April 2012 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Circular Arrangement
by Valerie 07 May '12

07 May '12

Nice proposal! I just find the use of arrows for "bounding box" confusing. For me, arrows refer to a Direction, so my first impression is that you're choosing the direction for a transformation, except that doesn't make sense here. There's a really nice existing blueprint for anchor points here: https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors For the sake of the future interface consistency, I'm wondering if that arrow-less grid shouldn't be used instead, though maybe in a bigger version. A mouse-over will pop up descriptions like "Use objects' lower-left bound." Another question is... how does this feature handle it if you want all the objects to Just touch the guide edge, but you don't rotate the objects? Basically, for an object on the upper-right, the lower-left bound should be used, while for an object on the lower-left, the upper-right bound should be used (which isn't quite an accurate way of putting it either, since the object doesn't necessarily touch the circle that way). See what I mean? Something like "Objects to touch circle's inner edge" (or just "Touch inner edge") and "Objects to touch circle's outer edge." Then again, if anybody needs that, they could submit it as a feature proposal later. I really look forward to the feature, rotational arrangements are a pain to do right now (I can never remember how to use that tiling interface). So thanks in advance!

3 4

affine/transform question
by mathog 03 May '12

03 May '12

In the emf print virtual methods the current transform is pulled out with: Geom::Affine tf = m_tr_stack.top(); Is the stack supposed to hold the final transform, or just the stack of partial transforms? For instance, for this bug: https://bugs.launchpad.net/inkscape/+bug/965594 the text SVG has a set of nested transforms, and the top only returns the inner one. The problem can be worked around by ungrouping everything, which seems to replace the serial transformations with a single one for each object. Otherwise it seems the proper action is to multiply down the transform stack to find the final complete transform operation. It looks like the stack is "fed" by the ::bind method, but that just moves the question out a bit, as that method has a call argument which is itself a transform. (Unfortunately "bind" is a common string in this code, so grep was not very helpful in locating whatever it is that calls the [virtual] ::bind method.) Thank you, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

5 8

javick2
by Ivano Arrighetta 30 Apr '12

30 Apr '12

signal processing and JAVICK in theory - draft 2 -https://docs.google.com/document/d/19EP2CgK6_EqsZ_nU6YSHcWsmC8ciFs7y1WWmTQw8J2c/edit Inviato da iPhone

1 0

Possible bug: ruler meters leaving trails
by Joachim 30 Apr '12

30 Apr '12

Hello all, Have found a possible bug. When using Inkscape on my Sony Vaio VGN-NS11Z traces are left by the ruler indicators on the edges of my 'design screen'. Running Debian Squeeze here. See attachment for a screenshot. Regards, Joachim de Koning - Metasync.info

2 1

javick
by Ivano Arrighetta 30 Apr '12

30 Apr '12

Someone pointed me to videojack, it's almost the same thing Inviato da iPhone

1 0

javick
by Ivano Arrighetta 30 Apr '12

30 Apr '12

sorry, i posted a wrong url. right one: https://docs.google.com/document/d/1Lut6Y6Xe-4ScR9G4Fg6EorTuSp0JKuTP6QRRzrk… Inviato da iPhone

1 0

javick
by Ivano Arrighetta 29 Apr '12

29 Apr '12

please see: https://docs.google.com/document/d/1Lut6Y6Xe-4ScR9G4Fg6EorTuSp0JKuTP6QRRzrk… and comment here Inviato da iPhone

1 0

Trunk PPA
by Josh Andler 28 Apr '12

28 Apr '12

Hey All, I just wanted to let people know that I've included the Quantal (Ubuntu 12.10) series in the PPA builds, so they should start showing up soon. Cheers, Josh

1 0

Re: [Inkscape-devel] New dynamics interface proposal
by Valerie 28 Apr '12

28 Apr '12

> http://www.tomlechner.com/randompics/finishing.png Ni... whoa, transparency on dark background is hard to read. xD But it's okay once you've downloaded the image. So anyway, it does look nice! I did end up thinking about what Josh said about what's "something you'd find in Inkscape and what you don't", and about implementation issues though. I'm wondering if it isn't too hard to code those visual elements (maybe it's not though, I can't tell). The part I totally agree with is the gradient and the "extrude" view for dynamics. A few thoughts on the rest: 1. Color dynamics In fact, the existing tiling mechanism is quite far from the ideal solution. Right now: To have color dynamics, you have to: - Start with unset fill and stroke colors - All objects in group must have and end up with the same color properties - You can only define a start value and %changes (though by defining a start and end value instead, it should be possible to have those then converted into %values) Ideally: - You can start with any fill and stroke - You can have objects of different color/opacity/blur properties - You can define multiple stops, just like a gradient Basically, for color/opacity/blur dynamics, your proposed interface works well if there's only a start node and an end node. For the user to be able to add intermediate nodes, the code for the color dynamics mechanism needs to be changed. This does not prevent us from defining the ideal end interface from the start, I just mean I'll have to note this in the wiki later, so I'm telling you first. Also, on the group color change, the following feature basically would help a lot (just like "cut operation on groups" is necessary for the "fuse tile" mode): Group colour/color changes, brightness, contrast, HSV, more: https://bugs.launchpad.net/inkscape/+bug/171181 Instead of starting with an object with no fill or stroke, you could start with anything you want, even groups of objects with different colors etc. Inkscape would modify the hue of the whole group like when you use the hue slider in Gimp for example. 2. Jitters There are two things that worry me a bit about the jitters presentation: - Interface clutter: I like the wub-wubs, but it may get messy with more than 2 or 3 of them. Maybe a single static round wub-wub could be displayed around the node if there's - any- jitter (just to warn you that it's there). The user can them see which ones are available by bringing up the whole thing. - Ease of programming. There aren't that many GUI features in Inkscape, and I don't know how how easy it would be to create a widget like the one you're proposing. Maybe clicking on nodes could instead just pop up a more usual dialogue with different jitter options and sliders: X-Jitters [x] Position : |----|--| [ 80 ]% [ ] Width : ||------| [ 10 ]% [x] Opacity : |------|| [ 90 ]% [ ] Hue : |---|---| [ 50 ]% (logarithmic sliders could be nice...) I wonder if trace properties could also be stuffed somewhere... Since there is a "preview" button in the wiki proposal, the user can just toggle it on then off and tweak values until he's happy. Though... the preview feature itself is something that needs some work...

1 0

Re: [Inkscape-devel] New dynamics interface proposal
by Valerie 28 Apr '12

28 Apr '12

Thanks for uploading the file Veronika! http://wiki.inkscape.org/wiki/index.php/Tiling_tool I've edited the wiki page some more: - Added a table of UI design status, so feel free to add your own input of what seems OK already and what isn't - Added description for radial tiling - Added description for line tiling - Re-added proposal for symmetrical dynamics around base tile, but also noting that the current tiling mechanism does not support it - Added current discussion on on-canvas Dynamics. Also added a proposal: "preview mode for dynamics" (click a checkbox next to wherever the toolbar item for dynamics is located). Inkscape will render a preview of the dynamics by applying it to the frame's different tiles, also adding blur, color, opacity. You cannot edit transformations or jitters in this mode. Uncheck to return to "edit" mode. I've also finally added a blueprint link: https://blueprints.launchpad.net/inkscape/+spec/tiling-tool Although work still needs to be done, especially concerning on- canvas dynamics, I doubt on-canvas dynamics editing will be implemented anytime soon, first because Inkscape is currently more focused on clean-up, second because the tiling tool itself isn't likely that high priority, third because even then, many other features need to be coded first before reaching that particular feature... By the way, am I the only one for whom the text tool now crashes every time I try to start a new text box? (I can copy existing text boxes and change the content though) inkscape: /usr/include/boost/optional/optional.hpp:641: boost::optional<T>::pointer_type boost::optional<T>::operator->() [with T = Geom::Rect, boost::optional<T>::pointer_type = Geom::Rect*]: Assertion `this->is_initialized()' failed. (kind of annoying while making the mock-ups)

3 3