March 2012 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] New tiling interface proposal
by Valerie 29 Mar '12

29 Mar '12

> The unclump option is already in the align and distribute dialog. So... should I add it or not? > This might give some problems when used with the fuse cut method > (with or without borders). In principle the user can obviously create a > design based on a rectangular tile, but this might not be the most natural. You mean edge scenarios right? It shouldn't be a problem for inner tiles, since you can just duplicate the pattern to fill the missing part, and Inkscape will still cut it more or less correctly. How about this? You can skew, but if you mess with the handles, the tile snaps to 90 degrees angle again. It becomes skewed again if you go back to P1 or P2. (I don't envy the person who wants to try to program the tiles...) > This reasoning is partly correct, and I agree that this would definitely not > be a "must". On the other hand, I think that some changes might be quite > logical, so at some point it might be nice to have the option. Hmm... I'll leave it in the design as a "really low priority feature", and we can just wait and see if anybody actually requests the feature one day. > Partially. One of the things that would make interpolation work really > well with tiled clones is that they are conceptually laid out in a grid True. Leaving dynamics out made the design conception much easier, but I realized that having to go back and add dynamics separately would be annoying in the end. Here's what I propose: http://postimage.org/image/4235075wd/ The solution is that little dot thing in the corner of each frame. Initially I was worried that it'd get in the way, but then I realized that until rendering is done, those frames are empty anyway. They're also invisible outside of the render mode. Each dot offers a visual representation of opacity, blur and HLS. Mouse-over gives exact values. Double-click to define exact values. At this point I hope the programing folks can answer a few questions about interpolation: 1. It is possible to define interpolation over both rows And columns using just a start tile and a reference tile (example: a base tile at the upper-left and a reference tile and the bottom-right). The current tiling dialogue forces you to define changes for both Rows and Columns. Though, in that scenario, maybe Inkscape just divides the values over Rows and Columns (I still need to make sure though that users don't need to choose two reference tiles besides the base tile). 2. Could each render tile in fact be considered more or less like an independent tile? Like, should we have the option to allows the user to break a tile apart and drag it around independently? (internally, Inkscape would still keep track of their row and column value, so users could still use some mechanism to select a whole row for example)

3 3

Re: [Inkscape-devel] Circular Arrangement
by Valerie 29 Mar '12

29 Mar '12

> You're right, the arrows are indeed a little bit confusing. As an > alternative I could use the iconless buttons like in the blueprint. As > an alternative I could put icons that somewhat resemble a bounding box. > Example: http://www.pasteall.org/pic/show.php?id=28549 Personally I really like your alternative icons! I wonder if the others agree? Don't worry about those other possible features I mentioned, they're just questions I happened to have on my mind. I wasn't trying to imply that you actually had to code them. Good luck with the project!

4 5

tracing bitmap images using bucket tool
by francesco fantoni 29 Mar '12

29 Mar '12

hi everyone, I used to selectively trace bitmap images using bucket tool, and I think it is a great feature and a wonderful trick in my workflow. Now I've compiled a fresh source from bzr, and tracing bitmaps this way seems not working anymore, I get only a message of non-closed surface or something similar. has this feature been removed on purpose, or am I somehow facing a bug? best to all, francesco

2 1

Re: [Inkscape-devel] Google Summer of Code 2012
by Yevgeny Lezhnin 29 Mar '12

29 Mar '12

Josh Andler писал 28.03.2012 02:44: > One thing to take into account when coming up with a proposal is if > you have many other plans for the summer. Are there other work or > travel plans that will be time consuming? Chances are that GSoC will > be much more time consuming than you may be expecting (especially if > you have not participated before). > > Cheers, >Josh I have a programming job in my university, but it should not take too much time in summer (0-5 hours per day), I'm not participated to gsoc before. I'm only participated to co.de-in 2010

2 1

Re: [Inkscape-devel] New tiling interface proposal
by Valerie 28 Mar '12

28 Mar '12

You guys are killing me. D: Hopefully this... 7th iteration or so is the lucky one (at least approach-wise)? It still needs a lot of work, but the Youtube video and the extra comment on guides were eye-openers, so thanks for that! Alright, here's the deal: so far the design has either concentrated on dialogue, or on the "base tile", and such. This new design changes the approach (again): this new tiling tool proposal is centered directly on a render frame (with one tile serving as "base" tile). http://postimage.org/image/vinwmlp6d/ http://postimage.org/image/81v4l35p3/ Now as you can see, it should be somehow possible to fit the Dynamics onto the top-level as well. Unfortunately, I'm not as smart as the guy who made that Youtube video, so right now I can't think of a fancy approach to handle it all. The basic idea is that for some dynamics at least, (namely involving position, angle, skew, size and maybe opacity and blur), it should be possible to define them on-canvas through some trick involving the distribution or interpolation of the various frames. Suggestions please?

3 2

Libraries for 0.49
by john Culleton 28 Mar '12

28 Mar '12

Are the library requirements for compiling 0.49 the same as for 0.48.2? I have just gone through the agony of adding all the Inkscape libraries needed for compiling/running 48.2 on Slackware Linux. -- John Culleton Free list of books for self-publishers: http://wexfordpress.net/shortlist.html Police Procedural and Expose: "Death Wore Black" "Create Book Covers with Scribus" http://www.booklocker.com/books/4055.html

3 3

Re: [Inkscape-devel] New tiling interface proposal
by Valerie 28 Mar '12

28 Mar '12

And another iteration: http://wiki.inkscape.org/wiki/index.php/Tiling_tool Is it me, or is the mail-archive not showing all mails in a timely manner? It took two days for one of mine to show up. Anyway, to answer a few questions: > Changing the selected wallpaper group is something the user will do a few > times and there are a fixed, small number of choices. Yes it would be very > nice to show the user that many of the groups are similar and to make the > user aware of the differences. However, I think there may be other ways to > do this and they may even be more clear. Yes, that's why there's a drop-down there. If you want to choose a tiling type immediately, then you use the drop-down. Also, the tile type can only be changed in tile edit mode. Users probably won't spend a lot of time in that mode. > In contrast, changing the size, orientation, in some cases angle of the base > tile with respect to the group being tiled is something the user will need > fine control over. The tiles behave like objects, so you can transform them with the F1 transform tool, and you can snap them to other guides. For radial and line tiling guides, you can also input numerical values in tile edit mode. I'm not sure what to do with the wallpaper tile though, since there are so many different shapes. A possibility is to define the coordinate of the first center of rotation + the length of 2 sides (only one is used if all sides are equal length). Now to answer Jasper: > 1. Inkscape's current tiling approach doesn't actually generate the > tilings it says it does. It /can/, but by default it doesn't (you need > to tweak the parameters to make sure the tiling actually matches the > chosen tiling group). Ah yes, I noticed the hard way that P2 tilings behaved weirdly... (i.e. I was trying to understand what it does by actually trying to render it) > Forget about tiles. Seriously. The problem with focusing on the > actual base tile are two-fold. First of all, if you define the base tile > together with what rotation centers/reflection axes are on its edges and > at what positions, then it is often non-obvious what the actual base > tile is. But the base tile is still the most intuitive guidelines one has for wallpaper tilings... Also, you need to know where the edges are to create seamless tiles. Or do you mean that the extra stuff gets in the way? The handles etc. aren't visible outside tile edit mode. Since the default tile is a simple P1 tile, and you need to bother double-clicking the tile to enter the tile edit mode and change what it does, I think we can assume that the user won't be too surprised if the output is no longer a simple P1. > Even worse, take a p2 tiling and put a 180-degree rotation > center on its "translational" edges (I'm referring to the diagram drawn > by veronika(?)), what you end up with is another p2 tiling with a > different base tile... Huh? It's still the same tile, just flipped. That's how wallpaper tilings work. > Another reason is that users might want to put guide points somewhere > else than on a tile boundary. So I think it is more important to focus on > the transformations involved, rather than on the base tile, and I think > this can even help to make things make MORE sense. I'm not sure what interface you're proposing. I know nothing about tilings, and the only thing I care about for tiling is that when I click the "apply" button, I get a pretty result (and a seamless output would qualify for the "pretty" factor). The specific transformations don't actually matter at all to users like me. :S

3 2

freehand tool in Python for comparison to Inkscape tool?
by lloyd konneker 27 Mar '12

27 Mar '12

This *might* be of interest to some. I am not familiar with the Inkscape freehand tool. I wrote a freehand drawing tool using Qt, PySide, Python. See https://github.com/bootchk/freehandTool Uses algorithms from potrace. Its readable, understandable, easy to prototype, and FOSS.

1 0

Re: [Inkscape-devel] New tiling interface proposal
by Valerie 26 Mar '12

26 Mar '12

Alright, I haven't made a full diagram of guide transformations using handles, but looking at the different tiling types, I am now convinced at least that it is at least possible. So, with that in mind, I bring you YATTIP (Yet Another Tiling Tool Interface Proposal): http://postimage.org/image/nhwdn9x29/ http://postimage.org/image/m1lvj06sn/ By popular (?) demand, this is now a tool again! (with a possible extra dialogue for extra options). The "handles" approach actually resolves a number of things. In fact, when choosing a guide, you now simple start with the following defaults: - P1 for wallpaper - Simple-rotation and scaling for radial tiling - Simple translation for line tiling (but all Frieze types are available) Double-clicking a "tile" changes the toolbar into the tile edit mode. Using either the handle or a drop-down in the toolbar, you can then change the tiling type. Since for wallpapers, most people will be using P1 anyway, this approach should be satisfactory. Other features I had proposed are still there: - Guide points and other guide types - Excluding parts of a tile's exterior and fusing all the tiles - Tile stacking should be still possible from a dialogue Any major comments before I completely redo the wiki content again?

2 1

Some clipboard functions
by Romain de Bossoreille 24 Mar '12

24 Mar '12

Hi, A 200% code question, thanks to the one (or two, or three... !) who will give me an answer! I'm looking very closely to the clipboard implementation to follow understanding its behaviour (cf. http://wiki.inkscape.org/wiki/index.php/Clipboard), an amazing work have been done but I've a question (in src/ui/clipboard.cpp): Inkscape::XML::Node *ClipboardManagerImpl::_copyNode(Inkscape::XML::Node *node, Inkscape::XML::Document *target_doc, Inkscape::XML::Node *parent) void ClipboardManagerImpl::_pasteDocument(SPDesktop *desktop, SPDocument *clipdoc, bool in_place) void ClipboardManagerImpl::_pasteDefs(SPDesktop *desktop, SPDocument *clipdoc) SPCSSAttr *ClipboardManagerImpl::_parseColor(const Glib::ustring &text) On my understanding, those functions should not be implemented in the Clipboard class because 1) they are not using any functions dedicated to the Clipboard and so 2) they are codes that could be needed for other puposes than clipboard (and I wonder whether some are duplicated elsewhere in the project). If my opinion/understanding is confirmed, implementing them in a more global namespace should be a better way to avoid dupplicated functions (now or in the future) and provide better code hierarchy ('util' functions?). Or at least setting them as static to show they are not dedicated only to the clipboard management. Does any "Inkscape developper expert" have an opinion on it? -- *Romain de Bossoreille*

2 2