- Inkscape Devel - Inkscape Mailman

resize text boxes
by Wolf Drechsel 16 Jan '10

16 Jan '10

Hello friends, how can I resize text boxes without resizing the font ? - What I want is that the font size remains stable and the number of lines increases when I make a text box narrower. Thanks and greetings, Wolf

2 1

Node tool is ready
by Krzysztof Kosiński 15 Jan '10

15 Jan '10

Hello all Today I have implemented snapping of nodes, so the new node tool should be ready to go into trunk. As a reminder, here is the status table: http://wiki.inkscape.org/wiki/index.php/GSoC2009_Node_Tool_Rewrite There are still some minor issues with snapping: 1. Nodes do not snap to unselected segments of selected paths. 2. Nodes do not snap to selected shapes. They will be fixed once I refactor the event context / tool hierarchy, which I plan to do before this year's GSoC. Now I have a few remarks / questions about the behavior: 1. There is an RFE: https://bugs.launchpad.net/inkscape/+bug/321150 The proposed is like the new node tool's join action, but with a distance threshold. Implementing this should be easy, but I don't know how to present it in the UI. Ideas, anyone? 2. Releasing the mouse button causes the point to immediately snap, even if the snap delay has not expired. For me, this unexpected and very annoying: I have to turn off snapping to make a non-snapped movement. If this feature was removed, I could comfortably make both snapped and non-snapped movements with snapping enabled. Currently I disabled snapping on mouse button release. 3. When a point snaps to a path, it should remain snapped to it until the pointer wanders outside the snap distance. This would allow me to adjust the point's position on a path it snapped to, without waiting for the snap delay to expire every time. Same behavior for snapping to nodes, corenrs, etc. (the point remains snapped until I move the mouse pointer out of the snapping range). What do you think? 4. The method to switch to the transform handles to rotation mode is very non-obvious. Currently it is Shift+R. To be consistent with the selector, the method to switch to rotation mode should be to click on a selected node, but this might become annoying quickly - the old behavior is to select only the clicked node in this case. I think the second behavior is acceptable if it only works when transform handles are shown, and the handles can be toggled using a button on the controls bar (preferably the first one). Regards, Krzysztof.

7 40

We are good to go!
by Joshua A. Andler 15 Jan '10

15 Jan '10

Hey all, I made the first commit on LP after our trunk branch was established and it went smoothly. So, everyone, feel free to go to town! As a side thought, since 0.48 will be maintained for a bit while 0.49 is under development. What do people think about our use of LP and how we use Fix Released rather than Fix Committed... are people game to perhaps try using Fix Committed (and target them for 0.48 when doing so) for this cycle? If we properly use committed and mark where it will be available, we can then just script it to change to released when it really is (I think it will be nicer for users). Just a thought. Cheers, Josh

9 19

NEW: remove boost::optional warnings
by Krzysztof Kosiński 14 Jan '10

14 Jan '10

Hello I put in some extra code in configure.ac to turn off strict aliasing warnings when boost::optional emits a lot of them. It tries to compile a short snippet using boost::optional with -Werror=strict-aliasing, and if it fails, it adds -Wno-strict-aliasing to CXXFLAGS. It might be a bit unsafe, because we won't see aliasing warnings from things other than boost::optional, but on the other hand the legitimate warnings that can highlight real problems won't be crowded out by those spurious warnings we can't fix Relevant mail from the Boost mailing list. http://lists.boost.org/Archives/boost/2009/05/151577.php And the relevant quote. "Precisely... a char* is explcitely allowed to alias any object, so, for Boost.Optional at least, the warning is clearly spurious." Regards, Krzysztof

2 4

document properties dialog
by Alexandre Prokoudine 13 Jan '10

13 Jan '10

Hi, Are we going to leave document properties dialog as it is now or is it acknowledged that alignment of widgets in its newly added section (margins) needs work? Alexandre

3 3

pixelsnap
by Alexandre Prokoudine 13 Jan '10

13 Jan '10

Hi, http://code.google.com/p/pixelsnap/ "PixelSnap is an extension for Inkscape, an incredibly useful vector graphics app. It allows you to align rectangles & paths to pixel boundaries, to create sharp web & digital graphics." IMO, we need it shipped by default until we have a global solution (if ever) :) Alexandre

6 7

Fwd: [cairo] Spot colors (and CMYK)
by Felipe Sanches 12 Jan '10

12 Jan '10

we need to provide that for cairo developers ---------- Forwarded message ---------- From: Carl Worth <cworth@...573...> Date: Tue, Jan 12, 2010 at 6:16 PM Subject: Re: [cairo] Spot colors (and CMYK) To: ecir hana <ecir.hana@...400...>, cairo <cairo@...278...> On Sat, 26 Dec 2009 15:31:12 +0100, ecir hana <ecir.hana@...400...> wrote: > Hello, > I've seen some messages about adding spot colors (or named color, or > Separation and DeviceN in PDF specs terms) some time ago. Or perhaps > even adding CMYK as well. > Please, does anyone know if there has been any developments in that > direction? Is it perhaps planned to include spot colors in the future? > Or, is this not very central to the current development? >From time to time, the cairo community sees a message like yours where we clearly have users interested in these features. But we haven't had much in the way of concrete API proposals (nor implementations to go along with them!). And it seems that the current set of cairo maintainers do not have the expertise to come up with either of these on their own. So I think we're going to need some further input from *somebody* before we'll see concrete progress on this front. Do you know of anyone (perhaps yourself) that could provide some or all of the following: * Concrete use case to describe what is missing at the application<->cairo boundary. * A concrete API proposal to satisfy that use case, (and a minimal API that doesn't multiply existing cairo entry points exponentially). * An implementation of that API. I'm looking forward to further input here, since I'd love to be able to say that cairo has a good answer for people needing whatever is missing here. -Carl -- cairo mailing list cairo@...278... http://lists.cairographics.org/mailman/listinfo/cairo

2 1

Fwd: 2D animators using free software
by Felipe Sanches 12 Jan '10

12 Jan '10

anyone here is capable of doing simple 2d animations with free software and would like to help the Free Software Foundation? Please contact Holmes Wilson at holmes@...511... -Juca ---------- Forwarded message ---------- From: Felipe Sanches <juca@...2270...> Date: Tue, Jan 12, 2010 at 6:01 PM Subject: Re: 2D animators using free software To: Holmes Wilson <holmes@...511...> I can ask our geeks from the inkscape users mailing list. On Tue, Jan 12, 2010 at 4:44 PM, Holmes Wilson <holmes@...511...> wrote: > Hey Felipe, > > FSF is looking for some animators who could do some simple but professional > 2D motion graphics for a film (mostly interviews) about software patents, > using free software. Know anybody? > > -Holmes >

1 0

Inkscape 0.48 status and proposed release plan
by Joshua A. Andler 12 Jan '10

12 Jan '10

Hey All! Are there any larger features people are planning on still for this cycle that aren't well known? I know of the following still outstanding: *Krzysztof's new Node Tool *Soren's DBUS work (provided Ted is able to do his magic on it) *JonCruz's Adaptive UI work I assume all kinds of smaller, less intrusive things are still on their way. However, I just want to make sure we keep track of the big things to keep this cycle tight and under control. Proposed release plan: Mid-February for Chill Beginning of March Frost (Bug Hunt begins) End of March for Feature Freeze End of April for Hard Freeze Sometime in May for Branch & Release I am planning on maintaining branches to patch in bug fixes for point releases this time. So we most likely will not do a bug hunt goal of 500 this time if things don't break badly (perhaps 300 if we're in decent shape, which makes the proposed plan feasible). Cheers, Josh

4 3

Objects ("patterns") along path - pathscatter extension
by Hans Meine 11 Jan '10

11 Jan '10

Hi, background: I want to model some room with rows of chairs, not necessarily along straight lines however. Furthermore, I want to be able to access each chair from python, in order to change appearance depending on status in a reservation system. Thus, I have been looking into an "create objects along path" functionality, and found the pathscatter ("Generate from Path/Pattern along Path") extension, plus some "path effect" which I could not get to work and did not find any documentation on. I also had a lot of problems with the pathscatter extension, which I would like to discuss with you and possibly provide fixes for at least some of them. (I am an experienced programmer, in particular with python, but not very familiar with inkscapes code or even GUI yet.) First, my impression was that the extension is slow (I think there's a lot of potential for improvements, since it looks like a straightforward but not very efficient python implementation) and not very well integrated into the GUI, which is probably a typical problem with scripted extensions (I have experience with Gimp's script-fu stuff). For instance: 1. The menu has no accelerators, which makes it inconvenient to start without using the mouse. 2. It has an apply and a close button, but the apply button does not close the dialog, although the only sensible (actually: possible) action after it is close, since it modifies the selection, and the dialog is modal. 3. The dialog is modal, but does not check whether its preconditions (two objects selected) are fulfilled, so you end up making settings, getting an error message on "apply", need to close, fix the selection, and re-open it again (suffering from 1 again). 4. Also, there does not seem to be any good documentation or even help within the program (for instance: icons, tooltips or "whats this" texts, ...); the best information I found was the python comments at the top of pathscatter.py, which should probably be at least put up on some wiki page. Speaking of preconditions, it took me more than an hour to understand how to use the extension, simply because I tried it only with a rectangle as pattern. The results were incredibly... wrong. That's because the extension seems to work only with paths (that is - circles seem to work) - this could surely be improved either by a) allowing rectangles, which should be possible at least in the "snake" mode, or by b) automatically converting other objects into paths. Actually, my plan would be to implement both a+b, since I then realized that with just b) (which is probably the easiest to implement) I have yet another problem: in the "repeated" mode, I am still getting only a single path as result, which contains several path components. For my use case, I really need separate objects, in order to be able to differently style the chairs. I have some basic coding questions, which I will put into a separate posting. -- Ciao, / / .o. /--/ ..o / / ANS ooo

6 10