March 2014 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] GSOC 2014 - New patterns/paint servers UI
by Krzysztof Kosiński 18 Mar '14

18 Mar '14

2014-03-11 16:31 GMT+01:00 Tomasz Boczkowski <penginsbacon@...400...>: > Thank you for your comments. I have to change my design a bit. > > >> 4. What is the purpose of the "transform" button? The pattern >> transform is specified on the object, not on the pattern, and is >> already editable on the canvas. This looks like a mistake. > > I tried to fix the bug #210442 in my solution. The transform button can be > replaced > by scale/rotation entries. I think the transform should be editable in the Fill & Stroke dialog only. It should not appear in the Swatches/Paints dialog since the transform is an attribute of the object, not of the pattern. >> How would this "new object" be represented at the XML level? > > I thought about representing them as svg:g elements with inkscape:type = > "patternEdit" attribute. > It is similar to the way layers are represented. > >> 5. I think it would be more sensible to embed the pattern preview and >> chooser into the existing fill and stroke dialog. > >> The proposal looks sensible. If you don't have too much experience >> with the Inkscape codebase, I think you could limit the proposal to >> providing the pattern preview in the fill and stroke dialog > > I don't have much experience with Inkscape codebase yet. I can resign from > implementing pattern edition tool. > I have created a new mockup illustrating modified Fill and Stroke dialog > [1]. > Solution 1 consists in embedding the pattern browser inside combo-box popup. > Gtk+ seems to be flexible enough to allow such changes [2]. The main > advantage > of this solution is providing the pattern browser with more screen space to > display > pattern icons. Selection from a combo box is not very nice when you have lots of items, for instance selecting markers is a pain. I like solution #2 better. > I would implement the browser widget in a way that allows future handling > different > paint servers: solid colors/hatches/gradient. Implementing "paints" or new > "swatches" dialog > around it seems feasible. This somehow extends the named color swatches > blueprint [3]. > I can make it an optional goal. > > What do you think about this? This slightly reduced project looks very sensible to me. With some guidance I think you have pretty good chances of being accepted and succeeding. >> and converting a few things to C++ along the way. > > I see there is some C-like code left in sp-pattern.h/.cpp. What else could I > focus on in my project? There are several classes used in the fill and stroke dialog which you could convert to C++ or improve, for example SPColorSelector and its derived classes. They are C++ classes, but they are hidden as members inside GObjects, which is confusing to novices and leads to verbose code. You could convert them to proper C++ classes that derive from the relevant gtkmm widgets. > Regards > Tomasz > > [1] https://www.dropbox.com/s/kvgjvtowpm55m5h/new_patterns_ui_2.svg > [2] http://tirania.org/pictures/hwidgets/gtk-combo-tree.jpg, > http://tirania.org/blog/archive/2008/Jun-01.html > [3] https://blueprints.launchpad.net/inkscape/+spec/named-color-swatches > > PS > > Your message was sent directly to me, omitting the mailing list. Oops, my bad. Regards, Krzysztof

3 2

Extension: Merge Style
by Martin Owens 18 Mar '14

18 Mar '14

Hi devs, I've committed in r13161 an extension which will take the inline styles from the selected elements, find the common values and create a new css style in the existing or new style element at the top of the document. This replaces the inline styles with a class reference. <rect style="fill:red;"/> <rect style="fill:red;"/> <rect style="fill:yellow;"/> <rect style="fill:red;stroke:green;"/> Becomes: <style> .name_of_choice { fill:red; } </style> <rect class="foo"/> <rect class="foo"/> <rect style="fill:yellow;"/> <rect class="foo" style="stroke:green;"/> I've added this into the extensions menu under Stylesheets > Merge Styles into CSS. And I decided to push it into trunk instead of just keeping it on my hard drive because it might be useful to other users. But I'd also like to sound it out too. So any issues you think, I'd love to hear. This should make it easier to make web svg I think. Best Regards, Martin Owens

2 3

Re: [Inkscape-devel] Bug Hunt for 0.91
by Bryce Harrington 18 Mar '14

18 Mar '14

Current stats: Bug Hunt Goal: 500 points Current: 381 points Pts Bug Date Assignee Description ------------------------------------------------------------------------ 9 1280684 2/22 Alvin Penner changing doc units with viewbox defined 9 1278645 2/22 David Mathog Image handling corrupts EMF/WMF output 9 1171109 2/20 insaner crash on cut n paste, or alt+scroll.. 6 1258473 2/13 Alvin Penner trunk: ink2canvas for stroked objects fails 6 1250250 2/07 David Mathog WMF/EMF open misplaces drawing 9 168695 1/28 Martin Owens Crash when undoing while mouse button pressed 6 1272119 1/27 apenner Poor rendering after 2geom update 6 1268778 1/25 jazzynico Move cursor disappears 3 1266308 1/15 apenner bbox dotted lines not visible if overlapped 9 1256449 1/15 Tavmjong Bah Clipped groups lose clipping when exporting 6 1268778 1/15 JazzyNico Move cursor disappears 3 1239779 1/14 Martin Owens symbol preview no longer updates 6 1253110 1/12 Johan E. Wrong intersection on circles at 45° (rev >= 12594) 6 1251405 1/10 mathog btool hitting command line limit on XP/Mingw/Msys 9 1255791 1/10 Martin Owens crash drag deleting guides 9 1257417 1/09 Martin Owens crash removing ID from object 9 1230241 1/09 Martin Owens crash for text with empty font-family 9 1258815 1/08 Kris crash after using Edit nodes icon twice 3 1255764 1/08 Bryce on screen snap message says UNDEFINED 9 1192023 1/08 Martin Owens Use elements removed when grouping 9 168695 1/08 Martin Owens crash when undoing 6 1247324 1/06 Jabiertxof optimized transforms do not propagate 9 1265556 1/04 JazzyNico plain svg export broken for filter 3 1057494 1/04 JazzyNico text hidden with "Remove Manual Kerns" 6 1262146 1/04 apenner persistent offset when scaling object On Tue, Jan 28, 2014 at 09:13:11PM -0800, Bryce Harrington wrote: > Pts Bug Date Assignee Description > ------------------------------------------------------------------------ > 9 168695 1/28 Martin Owens Crash when undoing while mouse button pressed > 6 1272119 1/27 apenner Poor rendering after 2geom update > 6 1268778 1/25 jazzynico Move cursor disappears > > 3 1266308 1/15 apenner bbox dotted lines not visible if overlapped > 9 1256449 1/15 Tavmjong Bah Clipped groups lose clipping when exporting > 6 1268778 1/15 JazzyNico Move cursor disappears > 3 1239779 1/14 Martin Owens symbol preview no longer updates > 6 1253110 1/12 Johan E. Wrong intersection on circles at 45° (rev >= 12594) > 6 1251405 1/10 mathog btool hitting command line limit on XP/Mingw/Msys > > 9 1255791 1/10 Martin Owens crash drag deleting guides > 9 1257417 1/09 Martin Owens crash removing ID from object > 9 1230241 1/09 Martin Owens crash for text with empty font-family > 9 1258815 1/08 Kris crash after using Edit nodes icon twice > 3 1255764 1/08 Bryce on screen snap message says UNDEFINED > 9 1192023 1/08 Martin Owens Use elements removed when grouping > 9 168695 1/08 Martin Owens crash when undoing > 6 1247324 1/06 Jabiertxof optimized transforms do not propagate > > 9 1265556 1/04 JazzyNico plain svg export broken for filter > 3 1057494 1/04 JazzyNico text hidden with "Remove Manual Kerns" > 6 1262146 1/04 apenner persistent offset when scaling object > > Bryce > > > > Pts Bug Date Assignee Description > > ------------------------------------------------------------------------ > > 3 1266308 1/15 apenner bbox dotted lines not visible if overlapped > > 9 1256449 1/15 Tavmjong Bah Clipped groups lose clipping when exporting > > 6 1268778 1/15 JazzyNico Move cursor disappears > > 3 1239779 1/14 Martin Owens symbol preview no longer updates > > 6 1253110 1/12 Johan E. Wrong intersection on circles at 45° (rev >= 12594) > > 6 1251405 1/10 mathog btool hitting command line limit on XP/Mingw/Msys > > > > 9 1255791 1/10 Martin Owens crash drag deleting guides > > 9 1257417 1/09 Martin Owens crash removing ID from object > > 9 1230241 1/09 Martin Owens crash for text with empty font-family > > 9 1258815 1/08 Kris crash after using Edit nodes icon twice > > 3 1255764 1/08 Bryce on screen snap message says UNDEFINED > > 9 1192023 1/08 Martin Owens Use elements removed when grouping > > 9 168695 1/08 Martin Owens crash when undoing > > 6 1247324 1/06 Jabiertxof optimized transforms do not propagate > > > > 9 1265556 1/04 JazzyNico plain svg export broken for filter > > 3 1057494 1/04 JazzyNico text hidden with "Remove Manual Kerns" > > 6 1262146 1/04 apenner persistent offset when scaling object > > > > > > On Fri, Jan 10, 2014 at 01:11:57PM -0800, Bryce Harrington wrote: > > > Quite a busy week! Another 63 points worth of bugs squished: > > > > > > 9 1255791 2014-01-10 Martin Owens crash drag deleting guides > > > 9 1257417 2014-01-09 Martin Owens crash removing ID from object > > > 9 1230241 2014-01-09 Martin Owens crash for text with empty font-family > > > 9 1258815 2014-01-08 Kris crash after using Edit nodes icon twice > > > 3 1255764 2014-01-08 Bryce on screen snap message says UNDEFINED > > > 9 1192023 2014-01-08 Martin Owens Use elements removed when grouping > > > 9 168695 2014-01-08 Martin Owens crash when undoing > > > 6 1247324 2014-01-06 Jabiertxof optimized transforms do not propagate > > > > > > Inkscape's changelog for this past week shows a lot more awesome cleanup > > > work underway that doesn't show up on this list, including warnings > > > fixes and translation updates. > > > > > > Bryce > > > > > > > Today three more regression bugs were fixed: > > > > > > > > 9 1265556 2014-01-04 JazzyNico plain svg export broken for filter > > > > 3 1057494 2014-01-04 JazzyNico text hidden with "Remove Manual Kerns" > > > > 6 1262146 2014-01-04 apenner persistent offset when scaling object > > > > > > > > Bryce > > > > > > > > On Sun, Dec 29, 2013 at 04:15:54PM -0800, Bryce Harrington wrote: > > > > > Welcome to the first bug hunt for the 0.91 release. This hunt focuses > > > > > on regression bugs. > > > > > > > > > > Traditionally, we specify a point target for us to reach, and award us > > > > > points based on the severity of the bug: 3, 6, 9, or 12 points for low, > > > > > medium, high, and critical. This bug hunt's goal is 500 points worth of > > > > > bugs from the following list: > > > > > > > > > > http://tinyurl.com/bughunt91a > > > > > > > > > > You'll note a few dozen regressions were already fixed, so we'll count > > > > > that as a (207 point) headstart on the effort. Here's a couple more > > > > > links to list only the open or closed bugs: > > > > > > > > > > http://tinyurl.com/bughunt91a-open > > > > > http://tinyurl.com/bughunt91a-closed > > > > > > > > > > [I'll write a launchpadlib script to calculate the score from the latter > > > > > list, unless someone's ambitious and beats me to it!] > > > > > > > > > > We only give points for true bug fixes - not bugs simply closed due to > > > > > being dupes, invalid, works-for-me, or whatnot. Once the bug is fixed > > > > > in the mainline branch, set its status to Fix Committed, and it'll tally > > > > > as a fixed regression. > > > > > > > > > > Bug Hunt Goal: 500 points > > > > > Current: 207 points > > > > > > > > > > If you're not a developer, you can still help by seeing if you can > > > > > reproduce the bug yourself, and posting your findings. > > > > > > > > > > If you have an idea on how to fix the bug, but don't have the time to do > > > > > it yourself, then outlining your thoughts on the bug may help junior > > > > > developers pick it up and implement the changes. > > > > > > > > > > If you're an experienced developer, consider posting an invitation to an > > > > > IRC bug party for the time period you'll be working, if you're willing > > > > > to help pilot junior developers and sponsor their patches. > > > > > > > > > > I will be posting scoring updates a couple times a week until we're > > > > > done. > > > > > > > > > > Bryce > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > Rapidly troubleshoot problems before they affect your business. Most IT > > > > > organizations don't have a clear picture of how application performance > > > > > affects their revenue. With AppDynamics, you get 100% visibility into your > > > > > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > > > > _______________________________________________ > > > > > Inkscape-devel mailing list > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > ------------------------------------------------------------------------------ > > > > Rapidly troubleshoot problems before they affect your business. Most IT > > > > organizations don't have a clear picture of how application performance > > > > affects their revenue. With AppDynamics, you get 100% visibility into your > > > > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > > > > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > > > _______________________________________________ > > > > Inkscape-devel mailing list > > > > Inkscape-devel(a)lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > ------------------------------------------------------------------------------ > > > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > > > Learn Why More Businesses Are Choosing CenturyLink Cloud For > > > Critical Workloads, Development Environments & Everything In Between. > > > Get a Quote or Start a Free Trial Today. > > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > > > _______________________________________________ > > > Inkscape-devel mailing list > > > Inkscape-devel(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > ------------------------------------------------------------------------------ > > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > > Learn Why More Businesses Are Choosing CenturyLink Cloud For > > Critical Workloads, Development Environments & Everything In Between. > > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply import > a virtual appliance and go from zero to informed in seconds. > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 4

GSoC proposal
by Krzysztof Kosiński 16 Mar '14

16 Mar '14

Here is what I submitted to Melange, let me know if anything else is necessary: Inkscape requires several high level path manipulation routines to implement some of its effects: - Boolean operations on paths. - Stroke-to-path conversion: given a path and stroke parameters, compute the shape of the stroke and return it as a new path. - Path offset. These operations are both available directly to the user and used as a building block for more complex effects. The current implementation uses a grid-based algorithm which rounds all coordinates to a multiple of some arbitrary quantum. This has several shortcomings - most notably it does not preserve the dimensions of the operands (see [1]). To provide a robust foundation for further feature development, this project will implement robust Boolean and stroke-to-path operations. The API will look as follows: class Path { ... void stroke(Coord width); void stroke(Coord width, std::vector<Coord> dash_array, Coord dash_offset); Geom::OptRect strokedBounds(Coord width); Geom::OptRect strokedBounds(Coord width, std::vector<Coord> dash_array, Coord dash_offset); Path &operator|=(Path const &p); Path &operator&=(Path const &p); Path &operator^=(Path const &p); Path &operator-=(Path const &p); bool contains(Path const &p); }; Operator helpers will allow developers to write code such as: Path result = path_a & path_b; Boolean operations will be implemented by copying the algorithm used by CGAL [2]. If necessary, CGAL will be added as a dependency of 2Geom, but will be hidden from users of the library (CGAL headers will not be required to build programs using 2Geom). Stroking operations will be based on the existing curve offset code for single paths available in 2Geom's offset toy. The stroke will be computed as an union of the offsets of all curves and the resulting shape will be post-processed to add joins and caps. Once the new operations are available, the Inkscape codebase will be modified to make use of them, and the current implementation from the livarot library will be removed. Additionally, the following smaller work-items will be done in the preparatory phase: - 2Geom's Path class will be renamed to Subpath, and the PathVector class will be renamed to Path, to mirror SVG terminology. - Copy-on-write functionality will be moved from Subpath to Path. - Various helper methods will be added to Path to simplify existing code. - The SPCurve class will be removed. Schedule: - before June 10: complete the items from the preparatory list, bounding box computation for stroked paths, read CGAL code and determine if adding it as a dependency is required - June 10 - June 30: final exams at my university - after June 30: implementation of boolean operations, implementation of stroking [1] https://bugs.launchpad.net/inkscape/+bug/168158 [2] http://doc.cgal.org/latest/Boolean_set_operations_2/index.html Regards, Krzysztof

1 0

Style Editing
by Martin Owens 16 Mar '14

16 Mar '14

Hi devs, Sorry if this has been worked on before, none of my searches came up with anything. Mockup time: http://wiki.inkscape.org/wiki/index.php/Style_Editor A idea to non-invasively allow any existing css style to be changed. Screenshot for mockup taken from 0.48 Thoughts? suggestions? Martin,

1 0

Inkscape sponsorship for LGM attendees
by Bryce Harrington 15 Mar '14

15 Mar '14

Interested in meeting up with fellow Inkscapers? Thanks to generous donations to the project, we are able to provide funds to reimburse five developers up to $500 each for attendance at the Libre Graphics Meeting in Leipzig in April. Anyone in the AUTHORS file as of Feb 19th, 2014 is eligible to apply. To register, please email Tavmjong Bah, our coordinator for the event, by March 6th to get on the list. He'll let you know what position you are in the list. Then, register for the conference, enjoy your time, and save your receipts. Afterwards email copies of the receipts to Tav, who will forward them along to SFC for reimbursement. A maximum of $500 US each will be reimbursed to five attendees for travel, hotel room, and food. Note that the LGM meeting may also give partial reimbursements, so if your total costs exceed $500 they may be able to help. In addition, the board is sponsoring Tavmjong Bah to attend both LGM as a speaker and as our event coordinator, and the co-located SVG Working Group Meeting. Tav will be representing Inkscape's interests at the SVG meeting, and will be working with them on features including mesh gradients, hatched fills, and auto-flowed text. Thank you to everyone who has contributed to Inkscape in the past. Your funding has made these sponsorships possible. We've found these face-to-face meetings invaluable both for sharing ideas and as general inspiration for advancement of the project. Bryce

6 7

Careful with C-strings!
by Johan Engelen 14 Mar '14

14 Mar '14

Hi all, *Please take this to heart: be very careful when handling C-strings. And try hard to use std::string, even if it involves a bit of work / adding helper functions.* Another C-string induced memleak was added today. Actually, the change fixed one memleak, but replaces it with the same one. Fixed in r13101. How to go about things using std::string in this particular case, see for example: http://stackoverflow.com/questions/20446201/how-to-check-if-string-ends-wit… ciao, Johan

6 13

Optionally disable antialiasing - implement based on existing SVG 1.1 rendering properties?
by su_v 13 Mar '14

13 Mar '14

> revno: 13144 > fixes bug: https://launchpad.net/bugs/170356 > committer: Krzysztof Kosiński <tweenk.pl@...400...> > branch nick: trunk > timestamp: Thu 2014-03-13 05:45:38 +0100 > message: > Provide a toggle in the document properties to optionally turn off > antialiasing for display and export. > Fixes a nearly 10 year old bug #170356 Questions related to rev 13144 (just curious): a) Why not implement such a feature based on existing SVG 1.1 rendering instructions (instead of a custom inkscape attribute of <namedview>)? Ideally, the user could then optionally apply this to individual objects (which may trigger bug #170356 if the objects' edges are adjacent), to groups or layers, or to the document itself, and the same effect may even be supported in other SVG renderers? AFAIU to disable antialiasing globally, these attributes could be added to top-level <svg> element: shape-rendering="crispEdges" text-rendering="optimizeSpeed" I'm not sure whether this one too: image-rendering="optimizeSpeed" <http://www.w3.org/TR/SVG11/painting.html#RenderingProperties> <http://www.w3.org/TR/SVG11/painting.html#ShapeRenderingProperty> <http://www.w3.org/TR/SVG11/painting.html#TextRenderingProperty> <http://www.w3.org/TR/SVG11/painting.html#ImageRenderingProperty> The attributes are also in the SVG2 draft: <http://www.w3.org/TR/SVG2/painting.html#RenderingHints> If implemented based on these rendering attributes, the feature should (or rather: could) also allow to control the rendering of different types separately (i.e. disable for shapes only, or for text only, or both), and maybe other text rendering modes can be added in the future (e.g. aliased with hinting for 'optimizeLegibility'). Note that support for 'image-rendering="optimizeSpeed"' has already been implemented (currently settable on import, and in objects properties for bitmap images (linked, or embedded)). b) Alternatively (based on other user requests), if the implementation stays a custom inkscape feature only: what about splitting it into a display mode (for rendering on-canvas, in the 'View' menu), and a bitmap export option which can also be used on the command line (without having to first edit the document properties via GUI)? Regards, V P.S. Personally, I somewhat disagree with closing bug #170356 based on a solution which globally disables antialiasing (for all shapes and text in the current document) - that report originally tracked an issue with a very specific aspect of antialiasing (adjacent edges); the current solution seems more like a workaround to me (disable antialiasing just for everything, including text (which - especially at smaller sizes - tends to looks bad (AFAIU due to lack of hinting) and objects not affected by bug #170356 at all). With r13144, antialiasing btw returns if an object (or group) has a reduced object (aka global) opacity, or uses a filter effect, for clipped or masked objects and probably other special cases.

2 3

Font selection
by Martin Owens 13 Mar '14

13 Mar '14

Hi devs, I was just making some art and noticed I couldn't select any fonts in the latest ppa build. Is this a known problem? Martin,

3 2

Re: [Inkscape-devel] Help with bzr
by Krzysztof Kosiński 13 Mar '14

13 Mar '14

2014-03-11 1:54 GMT+01:00 Jabiertxo Arraiza Cenoz <jabier.arraiza@...2893...>: > Thanks Krzysztof for the quick reply. > >> It is not removing the pushes, it is just changing the revision >> numbers so that the other users' pushes are in subrevisions. > > I feel confortable by this way but think isn't the normal usage in > inkscape trunk > >> If you want to prevent changes in revision numbers, use this: >> >> bzr config -d lp:path/to/branch append_revisions_only=True >> >> However if you set this, you won't be able to merge other users' >> changes and then push. Use this instead: >> >> bzr checkout lp:path/to/branch working_dir <-- only the first time >> cd working_dir >> bzr update <-- after the first time >> bzr merge <path to your working tree> >> bzr commit >> >> Another option - you need the "rebase" or "rewrite" plugin: >> >> bzr pull >> bzr rebase >> bzr push >> > Think one of this ways is the best, but i have the extra problem to > update the branch from trunk. Maybe this need to be done direcly in the > launchpad branch instead merge from trunk localy and push. Is correct? If you have your own branch on which you collaborate with a few users, you can just use a checkout. Instead of saying "bzr branch lp:path/to/branch" at the start, say "bzr checkout lp:path/to/branch". Then everything you commit will appear on Launchpad immediately, and to update you can simply say "bzr update". You can also say "bzr bind :push" to convert an existing non-diverged branch into a checkout. Regards, Krzysztof

4 13