- Inkscape Devel - Inkscape Mailman

GDL broken under Wayland
by Tavmjong Bah 21 Dec '17

21 Dec '17

Hi, It appears that GDL (Gnome Docking Library) is broken under Wayland. >From what I've figured out, the problem is that Wayland doesn't have the concept of global windowing position which means that GDL doesn't know how to do drag-n-drop.[1] The blue "pseudo" window used to indicate where the window is while dragging does not change position. GDL doesn't seem to be under active development so I can't see this being fixed upstream soon. (There were a handful of commits last year, mostly for translation updates.) The code and our interface to it are rather complicated and it would probably take someone a considerable amount of time to fix it. It might be time to rethink how we handle docked and floating dialogs. Any ideas? Tav [1] https://blog.gtk.org/2016/07/15/future-of-relative-window-positioni ng/

2 1

Re: [Inkscape-devel] Embroidery extension
by Lex 18 Dec '17

18 Dec '17

Ah, I see. My machine (a Brother SE400) can't cut the thread and continue stitching. It's a pretty difficult limitation to work with. I try to avoid jumps whenever possible, and when I have to, I place jumps such that they're easy to trim by hand. On August 28, 2017 1:45:33 PM Michael Soegtrop <MSoegtrop@...3339...> wrote: > Dear Lex, > > yes, in case there is a large distance, the TSP solver makes a jump. My > machine can actually do jumps (knot the threads and cut them at both > ends), so my main goal is to optimize the number of jumps. > > What one should do is try to order the groups such that connections can > be hidden below other stitching, but this is complicated, especially > when you don't have the concept of an area (my stuff just works on open > paths). > > Best regards, > > Michael > > On 25.08.2017 21:05, Lex Neva wrote: >> Hi! Sorry for going dark there -- everyday life intrudes fairly often. >> >> Neato, and thanks for the explanation! It does indeed look like your >> stuff follows a similar method to inkscape-embroidery. A few minor >> differences: >> >> * The extension handles creating a "grating" of lines automatically and >> intersects them with the fill region using Shapely (a Python extension). >> >> * The fill pattern is handled automatically through the insertion of >> extra nodes as you mentioned. Currently there's only one pattern: a >> sort of stair-step/staggered pattern that is visually pleasing. I >> cribbed it off of a pattern I bought online that was made using a >> commercial embroidery design program. I'd love to understand how to >> code more complex patterns, but I haven't given much thought to it yet. >> >> * The extension used to have a TSP solver of its own, but it really >> didn't do a particularly good job. I started off trying to fix bugs and >> ultimately just ripped it out. Instead, I carefully order paths in >> Inkscape. The new Objects panel is key for this, and it's a hugely >> awesome addition to Inkscape! The only part I struggle with is that >> Inkscape doesn't want to let you reorder objects relative to each other >> if they don't intersect (or nearly intersect). >> >> Ultimately, the problem I brought up for discussion boils down to the >> same problem you're solving with the your TSP algorithm. *Question: >> *what does your code do if it needs to get from one section to another >> that is distant? Does it just jump-stitch? >> >> Here's a brief description of how to use EmbroiderModder2's >> libembroidery to convert between formats: >> https://github.com/lexelby/inkscape-embroidery#optional-conversion-program >> >> I'd suggest that your code simply output a CSV in the format >> libembroidery understands, and then you can make use of its knowledge of >> pretty much every manufacturer format to convert it to a format >> compatible with your machine. >> >> --Lex >> >> On 7/30/2017 11:47 AM, Michael Soegtrop wrote: >>> Dear Lex, >>> >>> I guess we are trying to solve the same problem, but differently. I >>> wanted to have more control than semi automated fillers provide, so I >>> added 3 LPEs, which are in Inkscape 0.92.2: >>> >>> 1.) A bool LPE to do intersections / unions, ... of areas, so that one >>> can construct the areas to stitch from drawing areas. >>> >>> 2.) A path / path group trimmer LPE, which restricts a set of paths to >>> an area (or oustide of an area. There are already two path interpolation >>> LPEs which allow to create sets of paths with fine control over local >>> direction and density. >>> >>> 3.) An LPE to convert a set of paths into stitches. This includes an >>> almost reasonable traveling salesman problem (TSP) variant solver for >>> ordering groups of stitches to minimize the traveling in between. It can >>> still be improved. It is a bit more complicated than standard TSP >>> solvers, because it looks into groups of parallel stitches which have 4 >>> possible ends. >>> >>> >>> My approach is as follows >>> >>> 1.) Make a drawing >>> >>> 2.) Use the bool op LPE to create (in a new layer) the areas to fill >>> with each color / stitch style. >>> >>> 3.) Create a set of path to control density and direction using path >>> interpolation LPEs. This allows a great deal of control, e.g. for hair. >>> I don't think any commercial tool allows this amount of control. >>> >>> 4.) Use the path trim/cut LPE to trim the paths created in 3.) to the >>> areas created in 2.) >>> >>> 5.) Use the embroidery stitch LPE to convert the paths to stitches. >>> >>> Sometimes I use the cut / trim filter also to create intermediate nodes >>> in paths to create special stitching patterns. These nodes are not >>> visible in normal drawing, but after stitching they are visible. >>> >>> Of cause for simple cases, it would help to extend it with a more >>> automated approach, which is what you appear to be working at. >>> >>> I am very interested in the import/export library you mentioned. >>> >>> It would be great to work together on this. >>> >>> Best regards, >>> >>> Michael >>> >> > > -- > =========================================== > = Dipl. Phys. Michael Sögtrop > = Datenerfassungs- und Informationssysteme > = Steuerungs- und Automatisierungstechnik > = > = Anzinger Str. 10c > = 85586 Poing > = > = Tel.: (08121) 972433 > = Fax.: (08121) 972434 > =========================================== >

6 8

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 139, Issue 24
by Lex Neva 18 Dec '17

18 Dec '17

> That's really impressive. > I wonder if an extension is capable of setting the keyboard shortcuts ? > If it was then you could add an embroidery extension to set and unset > the shortcuts you use. > That would help to enable the workflows simple for complex domain > specific extensions like this. Neat idea, but as far as I know, there's no good way for an extension to modify keyboard shortcuts. The only method I can think of would be to kill inkscape, modify the preferences file, and restart. That seems like a terrible user experience. > > Question: - if the ice is white - how do you specify a thread change ? > The extension processes objects in their stacking order, lowest to highest. If it sees a color change from one object to the next, it automatically inserts a thread change instruction in the output file.

1 0

Spin slider widget, redux.
by Tavmjong Bah 16 Dec '17

16 Dec '17

Hi all, I've taken into account all the feedback and have developed a little test program that shows of a number of solutions to replacing the Gimp Spin Scale widget. A gzipped tar file of the source code is attached so that you can try out the solutions (should be trivial to compile on Linux if you have the Gtk3 libraries). Not all of the solutions fully work as I didn't take the time to make them... but you should be able to get a feel for them. If you run in debug mode (see README) you can interactively add CSS. I've include an example CSS file you can paste into the debug window (ignore the colors, they were just for experimenting). I've also attached PNGs of the widgets with and without the extra CSS. The five solutions, from top to bottom, are: * Custom Gtk::Range widget couple with Gtk::Spinbutton: This is my current favorite. It works quite well, methinks. Use the 'Alt' key to get into fine adjustment mode. It was rather simple to implement. Could be refined further (add styling properties, rounded corners, etc.). * Gtk::Scrollbar coupled with Gtk::Spinbutton: Works rather well, but doesn't show as well the current value. Using a narrow "slider" prevents it from covering up the text (text not implemented yet). I didn't know it before, but if one clicks on the slider and doesn't move for a second or two it enters into a fine- adjustment mode. * Gkt::ProgressBar coupled with Gtk::Spinbutton: CSS can get this looking pretty good but some extra work has to be done as the ProgressBar doesn't have an "adjustment", the class that actually handles tracking a value. The Gtk::Spinbutton actually contains a ProgressBar but while one can style it via CSS one can't directly access it and it overlaps the numerical entry part of the SpinButton (this is how the Gimp widget works). * Subclassed Gtk::Spinbutton: This is essentially a modified version of the Gimp widget but it has some major flaws as one cannot access the underlying widgets (ProgressBar, Buttons). In this example, the built in ProgressBar is disabled and new code that simulates a narrower ProgressBar has been added. I could not fine a good way to calculate how much narrower the new bar needs to be to not overlap the numerical entry part. Also, when dragging the bar it is easy to highlight the numerical text. The code to do all this is pretty messy. * Gtk::Scale coupled with Gtk::Spinbutton: CSS can make this look reasonable. Reducing the size of the circle will prevent it from covering text (text not implemented yet). Gtk::Scale also has a fine-adjustment mode accessed the same was as for a scrollbar. Tav

6 17

Stickers are here! ... now what?
by C R 12 Dec '17

12 Dec '17

The stickers arrived today. They are of acceptable quality, but I think 300dpi is a little low quality for stickers this small. Also I think the cutting machine had some ink residue, because the border of stickers are a bit dirty on the cut. So, who wants/needs stickers? I have a request for a sheet of the coffee and sheet of the ice cream already. Did we have any solid plans for these yet? See attached for samples.

6 9

Re-Posting Graphics Tablets
by Martin Owens 09 Dec '17

09 Dec '17

Dear Devs, There's a new fund going towards the development/maintenance of tablet drivers for linux (outside of wacom). It was posted to Libre Graphics World: http://libregraphicsworld.org/blog/entry/digimend-project-revived Would it be ok to post to inkscape.org? Best Regards, Martin Owens

3 2

Branch for high DPI monitors needs testing.
by Tavmjong Bah 07 Dec '17

07 Dec '17

Hi, If you've got a high DPI screen, please test the High DPI canvas branch: https://gitlab.com/inkscape/inkscape/tree/hidpi_canvas https://gitlab.com/inkscape/inkscape/merge_requests/137 There are a couple of minor problems that I know about (see merge request). If no other ones are found, I'll merge the branch in the next week. Thanks, Tav

2 3

[MR159] Convert to curves, bollops, union, combines... dont worry is not path
by Jabier Arraiza 07 Dec '17

07 Dec '17

Hi all, I just add a branch[1] to merge that, by converting to paths previouly: Allow boolops operation in shapes and clones Allow convert to stroke in shapes and clones Allow convert to curves in shapes and clones Allow combine with shapes and clones I want to know if is correct merge it. The 4 operations are descructive by default, so I dont see any problem to convert to path and allow finish the operation wanted by the user. [1] https://gitlab.com/inkscape/inkscape/merge_requests/159 Thanks for take time trying to undertand me. Jabiertxo.

1 0

Spin slider widget: Opinions needed!
by Tavmjong Bah 06 Dec '17

06 Dec '17

Hi, I've been looking into replacing the Gimp Spin Slider widget (e.g Blur/Opacity in the Fill and Stroke dialog). The widget is licensed under GPLv3 and is the only reason Inkscape as a whole is licensed under GPLv3 rather GPLv2.. The board sometime ago agree that being a GPLv2 program was desirable (I don't remember the exact reasoning). A normal Gtk Spin Slider (aka Gtk::SpinButton) has an option to show the "progress" of slider, that is the percentage (defined in some arbitrary way) between a minimum and maximum value. This in Gtk 2 is shown as a solid blue bar with width proportional to the value that covers the widget from top to bottom. In Gtk 3 the solid blue bar is replaced by a thin blue bar at the bottom of the widget. As far as I can tell, the Gimp version of the slider makes three changes: 1. It allows for a label inside the widget. This is a nice space saving feature. The widget handles changing the label text from black to white as the progress bar moves across the label. 2. It allows for a non-uniform scale by adding a "gamma" factor. 3. It adds the ability to drag the progress bar to change the value. If one drags from the top (down arrow cursor) the change follows the cursor directly. If one drags along the bottom half (double headed cursor) the change is finer and relative to the current value. I've always found that dragging the progress bar to be a bit awkward. One problem is that one can not start the drag at the far right of the widget as that area is reserved for typing a value directly in. Also, the different functionality of starting the drag in the top of the widget vs. the bottom of the widget is confusing. Since I am rewriting this widget, I can adjust it to what people want: * Do you want the progress bar? * If so, should it be the full height of the widget (quite a bit more complicated)? * Do you want to be able to drag the bar? With one/two methods? * Any other changes? Thanks, Tav

7 13

Wiki access
by Moritz 'Morty' Strübe 03 Dec '17

03 Dec '17

Hey there, I want to see whether I can do some optimization with the extension interface. My first idea is to have a two pass approach. First see whether the plugin only changed node attributes, and only replace the whole tree when nodes were added/removed or reordered. If this works, it would at least make JessyInk usable on large files. If that works out, I think there are some other low hanging fruits that can be picked. Anyway, as I know that I often do drive-by wiki editing I'm requesting wiki access right away. :-) Cheers Morty

1 0