- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Mathematical Art for teenagers
by Valerie 19 Mar '12

19 Mar '12

Hi Veronica! Alright, now I understand why you were asking about the visual references for the tiling guides. I was approaching the issue from a "need as little prior knowledge as possible" approach, while you are interested in an educational approach. That could be solved simply enough. There could be an option to toggle indicators and markers on and off, and maybe show "neighbouring tiles." I'll try to add such options to the existing mock-up. :)

2 1

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

19 Mar '12

Thanks for the link! - The Frieze groups are definitely interesting! I'll add those to the current mock-ups once I have the time. They should help make border designs easier. - The Rosetta groups seem to be just Simple Rotations and Symmetry + Rotations though. Am I missing something? I'm not sure what you mean by rotation points, reflection lines etc. that can be moved though. They don't exist as separate points, they're just the borders and corners of the guides. A guide defines the shape of the base tile. You modify the guide itself, not points along the guide. (example: simple translation has a rectangle guide. You can easily change the dimensions of this rectangle, though it will stay a rectangle). Are you referring to my notion of guide points? Guide points are separate points that when added to one side of a guide, create counterparts on other relevant sides of the guide, so you know where you add lines in a way to create seamless transitions from one tile to the next. They're made so that a user would need 0 knowledge of wallpaper geometry when creating seamless tiles: they just need to connect to the guide points. I should have made a visual reference of guides and guide point behavior for each tiling type, but the truth is, I'm pretty confused about tiling behaviour myself. :S That's the whole reason I tried to come up with an interface that basically requires 0 prior knowledge. x) ------------------------------ Message: 6 Date: Sat, 17 Mar 2012 11:55:16 -0700 (PDT) From: veronika <vmi@...2827...> Subject: Re: [Inkscape-devel] New tiling interface proposal To: inkscape-devel(a)lists.sourceforge.net Message-ID: <1332010516483-4628619.post@...2730...> Content-Type: text/plain; charset=us-ascii You have covered the topic very well. Another example to look at is the Kali applet: http://www.scienceu.com/geometry/handson/kali/index.cgi?group=wt For Tiling along the Path you could support the seven Frieze groups and for Rotational tiling you could support the Rosette groups. In the guides for a given symmetry group, you could show the rotation points (along with their degree) as well as reflection lines, glide reflection lines and translation directions and lengths. I think you briefly describe these ideas in your document but since there is quite a lot going on here it may be useful to spell it out in detail for each symmetry group. The user should be able to move these guide lines and points as long as they stay within the constraints of the chosen symmetry group. Below is a picture of guides for symmetry p6m (colours just used for visibility but should conform to guidelines elsewhere): http://inkscape.13.n6.nabble.com/file/n4628619/wallpaper.png The book "The Symmetry of Things" by Conway, Burgiel and Goodman-Straus has some very nice visualizations for reference. -- View this message in context: http://inkscape.13.n6.nabble.com/New-tiling-interface-proposal-tp4570734p46… Sent from the Inkscape - Dev mailing list archive at Nabble.com. ------------------------------ Message: 7 Date: Sat, 17 Mar 2012 21:03:47 +0100 From: Stefan de Konink <stefan@...2063...> Subject: Re: [Inkscape-devel] Inkscape GIS To: brylie@...2823..., Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net> Message-ID: <4F64EE23.3050006@...2063...> Content-Type: text/plain; charset=UTF-8; format=flowed On 17-03-12 20:55, Brylie Oxley wrote: > Thank you for suggesting Mapnik Stefan! :-) Inkscape would be a suitable > GUI for a Mapnik based cartography solution. I do not think that > Inkscape and Mapnik are necessarily in opposition, do you? The major problem is, if you look at cartography to SVG is that data is not offered in layers you would actually use in regular print. The output of mapnik is actually a set of drawing commands. So your audience might require two approaches; - ability to get an arbitary piece of a map, and the ability to interactively edit the stylesheet, see output etc. Inkscape could help here because stylesheets contain a lot of SVG elements you want to edit along the map; the result of this operation is a stylesheet, and a set of icons. - the ability to get arbitrary data in layers and be your own renderer, stack layers, assign decimation, add colours etc. this would be closer to having a shapefile in a solution like Illustrator and modifying it. Opposed to mapnik this step requires the editor to do 'layer' operations theirselves. Stefan ------------------------------ ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ------------------------------ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel End of Inkscape-devel Digest, Vol 70, Issue 16 **********************************************

2 1

Problem using GDB on Windows
by veronika 18 Mar '12

18 Mar '12

Hi, I am new to Inkscape development and I am trying to use gdb on Windows. Using the latest source from trunk (via bazaar), I followed the instructions on the wiki, modified the build.xml and did a full re-build. I have no problem building the executable and launching the executable but when I try to debug it, I get an error immediately after the main window opens: warning: HEAP[inkscape.exe]: warning: HEAP: Free Heap block 1621e0d8 modified at 1621e258 after it was freed Program received signal SIGTRAP, Trace/breakpoint trap. 0x772504e5 in ntdll!TpWaitForAlpcCompletion () from C:\Windows\system32\ntdll.dll The backtrace appears at the end of this post. I have tried both the gdb executable that comes with devlibs and the one installed with mingw - both give the same result. I have been able to use gdb with Inkscape on Linux with no problem. Any suggestions? Has anyone else encountered this problem? Thank you for your help. Veronika [New Thread 3380.0x3a8] [New Thread 3380.0x10cc] [New Thread 3380.0x12a8] [New Thread 3380.0xa44] [New Thread 3380.0xf6c] [New Thread 3380.0x774] warning: HEAP[inkscape.exe]: warning: HEAP: Free Heap block 1621e0d8 modified at 1621e258 after it was freed Program received signal SIGTRAP, Trace/breakpoint trap. 0x772504e5 in ntdll!TpWaitForAlpcCompletion () from C:\Windows\system32\ntdll.dll (gdb) backtrace #0 0x772504e5 in ntdll!TpWaitForAlpcCompletion () from C:\Windows\system32\ntdll.dll #1 0x0028e8e8 in ?? () #2 0x7720a383 in ntdll!AlpcMaxAllowedMessageLength () from C:\Windows\system32\ntdll.dll #3 0x1621e0d8 in ?? () #4 0x771b35a7 in ntdll!RtlReleasePebLock () from C:\Windows\system32\ntdll.dll warning: (Internal error: pc 0x4a in read in psymtab, but not in symtab.) warning: (Internal error: pc 0x4a in read in psymtab, but not in symtab.) #5 0x0000004b in ?? () warning: (Internal error: pc 0x4a in read in psymtab, but not in symtab.) #6 0x771b3492 in ntdll!LdrLoadAlternateResourceModuleEx () from C:\Windows\system32\ntdll.dll #7 0x1621e330 in ?? () #8 0x7725169e in ntdll!RtlValidateHeap () from C:\Windows\system32\ntdll.dll #9 0x0e9e0000 in ?? () #10 0x7720ab9a in ntdll!AlpcMaxAllowedMessageLength () from C:\Windows\system32\ntdll.dll #11 0x0e9e0000 in ?? () #12 0x771b3492 in ntdll!LdrLoadAlternateResourceModuleEx () from C:\Windows\system32\ntdll.dll #13 0x1621e330 in ?? () #14 0x75b198cd in msvcrt!free () from C:\Windows\syswow64\msvcrt.dll #15 0x0e9e0000 in ?? () #16 0x6aa0178a in sigc::signal_base::~signal_base() () from c:\veronika\research\inkscape\src\trunk\inkscape\libsigc-2.0-0.dll #17 0x00429b92 in ~signal1 (this=0x1621df04, __in_chrg=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/signal.h:2736 #18 ~signal (this=0x1621df04, __in_chrg=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/signal.h:3641 #19 SPObject::sp_object_finalize (object=0x1621dec8) at src/sp-object.cpp:199 #20 0x63a46492 in g_object_unref () from c:\veronika\research\inkscape\src\trunk\inkscape\libgobject-2.0-0.dll #21 0x00429791 in sp_object_unref (object=0x1621dec8, owner=0x0) at src/sp-object.cpp:270 #22 0x0042a12f in SPObject::deleteObject (this=0x1621dec8, propagate=false, propagate_descendants=false) at src/sp-object.cpp:494 #23 0x00c11b93 in deleteObject (propagate=<optimized out>, this=<optimized out>) at src/sp-object.h:471 #24 MarkerComboBox::create_marker_image (this=0x1619c928, psize=22, mname=0x13493180 "Arrow1Lend", source=0x124b4e40, drawing=...) at src/widgets/stroke-marker-selector.cpp:345 #25 0x00c12238 in MarkerComboBox::add_markers (this=0x1619c928, marker_list=0x16114e00, source=0x124b4e40) at src/widgets/stroke-marker-selector.cpp:306 #26 0x00c126bb in MarkerComboBox::sp_marker_list_from_doc (this=0x1619c928, source=0x124b4e40) at src/widgets/stroke-marker-selector.cpp:263 #27 0x00c12bfe in MarkerComboBox::init_combo (this=0x1619c928) at src/widgets/stroke-marker-selector.cpp:126 #28 0x00c13883 in MarkerComboBox::MarkerComboBox (this=0x1619c928, id=0x1621e0d8 "K", __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at src/widgets/stroke-marker-selector.cpp:68 #29 0x00b2e69e in sp_stroke_style_line_widget_new () at src/widgets/stroke-style.cpp:471 #30 0x00739b28 in Inkscape::UI::Dialog::FillAndStroke::_layoutPageStrokeStyle (this=0x16150978) at src/ui/dialog/fill-and-stroke.cpp:123 #31 0x0073a30a in Inkscape::UI::Dialog::FillAndStroke::FillAndStroke (this=0x16150978, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at src/ui/dialog/fill-and-stroke.cpp:64 #32 0x00db4a10 in getInstance () at src/ui/dialog/fill-and-stroke.h:35 #33 Inkscape::UI::Dialog::PanelDialog<Inkscape::UI::Dialog::Behavior::DockBehavior>::create<Inkscape::UI::Dialog::FillAndStroke> () at src/ui/dialog/panel-dialog.h:186 #34 0x004fd024 in Inkscape::UI::Dialog::(anonymous namespace)::create<Inkscape::UI::Dialog::FillAndStroke, Inkscape::UI::Dialog::Behavior::DockBehavior> () at src/ui/dialog/dialog-manager.cpp:68 #35 0x004fdf65 in getDialog (name=3267, this=0x13207190) at src/ui/dialog/dialog-manager.cpp:236 #36 Inkscape::UI::Dialog::DialogManager::getDialog (this=0x13207190, name=3267) at src/ui/dialog/dialog-manager.cpp:224 #37 0x004fe106 in Inkscape::UI::Dialog::DialogManager::showDialog (this=0x1621e0d8, name=3267) at src/ui/dialog/dialog-manager.cpp:257 #38 0x00d6e4e7 in operator() (this=0x1326fe9c, _A_a1=<optimized out>, _A_a2=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/functors/ptr_fun.h:147 #39 operator()<SPAction*&, void*&> (this=0x1326fe98, _A_arg1=<optimized out>, _A_arg2=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:103 #40 operator()<SPAction*&> (this=0x1326fe94, _A_arg1=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/adaptors/bind.h:1122 #41 operator() (this=0x1326fe90) at c:/devlibs/include/sigc++-2.0/sigc++/adaptors/bind.h:1110 #42 sigc::internal::slot_call0<sigc::bind_functor<-1, sigc::bind_functor<-1, sigc::pointer_functor2<SPAction*, void*, void>, void*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, SPAction*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void>::call_it (rep=0x1326fe78) at c:/devlibs/include/sigc++-2.0/sigc++/functors/slot.h:103 #43 0x00470dc9 in emit (impl=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/signal.h:773 #44 emit (this=<optimized out>) at c:/devlibs/include/sigc++-2.0/sigc++/signal.h:2668 #45 sp_action_perform (action=0x13276560) at src/helper/action.cpp:164 #46 0x00539226 in SPDesktop::show_dialogs (this=0x124d4d20) at src/desktop.cpp:1845 #47 0x004374eb in sp_namedview_window_from_document (desktop=0x124d4d20) at src/sp-namedview.cpp:845 #48 0x0045b6da in sp_file_new (templ=...) at src/file.cpp:136 #49 0x0045ba2e in sp_file_new_default () at src/file.cpp:182 #50 0x00403b25 in sp_main_gui (argc=1, argv=0xeb3a908) at src/main.cpp:976 #51 0x00ef218f in main (argc=1, argv=0xeb3a908) at src/main.cpp:711 -- View this message in context: http://inkscape.13.n6.nabble.com/Problem-using-GDB-on-Windows-tp4628229p462… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

5 6

Problematic documentation changes in r10697
by Krzysztof Kosiński 18 Mar '12

18 Mar '12

Revision 10697 moved most of the documentation from .cpp to .h files. This means extensive recompilation whenever a documentation change is made, and therefore it discourages improving documentation for no obvious gain. If there was a desire to have all the docs in one file, they should have been moved to the .cpp file with the help of commands such as @class and @var. Unfortunately this revision mixes the pointless moves with useful fixes, so I can't simply revert it. Regards, Krzysztof

1 0

New tiling interface proposal
by Valerie 17 Mar '12

17 Mar '12

I redid the whole thing... again. http://wiki.inkscape.org/wiki/index.php/Tiling_tool This is the first among my proposals with a consistent behavior from start to finish (at least, I think so), and doesn't look like a badly-proportioned three-headed Frankenstein. A picture is worth a thousand words so.... this is the target behavior: http://wiki.inkscape.org/wiki/images/Tiling_interface_examples.png In fact, I now divide the tiling "tool" into 2 parts (then further divided the whole proposal into hopefully more manageable sub-parts): 1. A general tiling guide tool whose only interacting with the tiling process is to send it coordinates (the type that no-one wants to input manually). http://wiki.inkscape.org/wiki/images/Tiling_Guide_Toolbar.png 2. The tiling -process- is back in a dialogue. This is because no matter what I did, it wouldn't stuff into a toolbar, and having separate "tools" was becoming a bit ridiculous. However, all the things that need to be "on-canvas" (the guide, basically) is now on-canvas. The only numerical values you need to input manually are intuitive ones like the number of clones and maybe a start and finish angle. And values for dynamics, but I haven't figured out an on-canvas way to handle those as the same time as basic tile information... http://wiki.inkscape.org/wiki/images/Tiling_dialogue_proposal.png Also, this interface allows you to stack tilings, and could also integrate into whatever future Effects Stacking interface Inkscape comes up with. >From a single tile, you can define not only the interior tiles, but "edge" scenarios as well. The feature involved here is actually a simple cut, delete and join operation: Inkscape cuts the pattern along certain guides, deletes the parts that need deleting, and does a "Select all nodes" and "Join" operation. (of course, on this occasion, I discovered that Inkscape can't actually cut groups of objects yet, oh well) If you placed all the tile elements in a way to create seamless tiles (that's where Guide Points are supposed to help), then all the tiles will proceed to join up seamlessly, even with small variations (though not big ones). Hopefully this is a good start for others to come up with even better possibilities. Thoughts?

2 1

Inkscape GIS
by Brylie Oxley 17 Mar '12

17 Mar '12

Hello, My name is Brylie Oxley. I am a student at Sierra College in Nevada City, CA. I would like to apply for the GSoC program. I have been studying GIS at Sierra College, where the courses focus on proprietary tools. For libre GIS tools to be viable options, we need high quality cartographic tools. This is where I see Inkscape as an EXCELLENT candidate. With some effort and extension, Inkscape can be used as an integrated cartographic tool in a libre GIS workflow. The primary goal of the extension would be to enable Inkscape to receive/display information from one or more Libre Geospatial tools/data sources (such as QGIS, PostGIS, GeoServer, MapServer, OpenStreetMap, OpenLayers, and/or GRASS GIS.) Python would seem to be a good candidate language as there are already Python bindings in Inkscape, QGIS, and GRASS. The primary task of the extension would be to send/receive geodata, so most of the heavy lifting might be able to be done by existing modules (specifically GDAL/OGR.) http://grass.osgeo.org/wiki/GRASS_and_Python#Writing_Python_scripts_in_GRASS http://www.qgis.org/pyqgis-cookbook/ http://pypi.python.org/pypi/GDAL I feel that this is a very important step for the viability of libre geospatial and would appreciate any mentorship and feedback that this community can offer. Thank you very much for your time and consideration. --Brylie Oxley

2 1

EAN% barcode.
by john Culleton 17 Mar '12

17 Mar '12

My copy of 48.2 has the EAN5 barcode available. The latest version of the Tavmong Bah book does not list it. Is EAN5 part of the distro now? I remember adding it separately to 48.0. EAN5 is used for the price barcode on books, and is included with e.g., Scribus. -- 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

5 5

Google Summer of Code 2012
by Josh Andler 16 Mar '12

16 Mar '12

Hi All, I just wanted to shoot out a message to let people know that we've been accepted as a mentoring organization again this year. If you know any college or graduate school students who would qualify and be interested, please let them know, we would like to talk to them. :) Cheers, Josh

1 0

Bug tracker maintenance
by Josh Andler 16 Mar '12

16 Mar '12

Hey everyone, If you're a developer and have a chance sometime soon, please visit the bug tracker to view what bugs are assigned to you. If you feel a bug assigned to you is wrongly assigned or that it is unlikely that you will work on that bug, please unassign yourself. We don't want to discourage anyone from taking on a bug because someone else's name is on it. As long as my LP-fu isn't bad (forget the stats on the bug page, I did it not including bugs marked "fix committed") the bug tracker currently has 1,791 open bugs (wishlist not included), 748 are marked as new, 167 marked High, and it appears that bugs w/ patches is at 84. Those numbers aren't horrible, but I'm sure there are a number of bugs that can probably be closed at this point. If you don't code, but want to help the project, you can give us a hand by trying to help us reduce the number of "New" bugs mentioned above. Trying to reproduce bugs is always helpful if they're not confirmed or if it looks like it was last confirmed a couple years back (or on old versions). I'm not sure if the tracker is as open as it was, but hopefully you can modify the status and such without needing to be a team member. If so, please review http://wiki.inkscape.org/wiki/index.php/Bug_management to find out how we do things. Any Qs, as always, please don't hesitate to contact me. Cheers, Josh

2 1

Re: [Inkscape-devel] Meeting: build system on Windows
by Johan Engelen 15 Mar '12

15 Mar '12

On 9-3-2012 10:00, Jasper van de Gronde wrote: > On 08-03-12 21:52, Johan Engelen wrote: >> Hi all, >> I would like to have an IRC meeting about the build system on >> Windows. >> >> Although I like buildtool, it cannot do parallel builds, so I am happy >> to change (back) to something else. And unify it with Linux if >> possible... >> I am trying cmake now, but it does not link without errors yet. It is >> not very encouraging to see the cmake build process get stuck on some >> intermediate step for a long while, seemingly checking something to find >> out it does not need to rebuild it. "btool" does this much much >> quicker... >> >> In any case, I'd like to discuss the options. Who's in? > > Depends on when the meeting is, but I wouldn't mind participating. > > And here's an alternative option: use buildtool on Linux as well. > Seriously. Yes, buildtool has its deficiencies, and it is much less > flexible than *make, but it is /so/ much easier to use and maintain (the > build file itself I mean, not buildtool). I'm completely unaware of the > issues involved in getting it to work on Linux, so perhaps it's just not > very feasible. Or perhaps I'm unaware of some of the issues buildtool > has on Windows. But I would hate to see buildtool go and be replaced by > some other monster of a build system just because it couldn't do > parallel builds (which should in principle be fixable). This of course triggered me to see if I could hack buildtool to do parallel builds. It turns out to be extremely easy to do so! See rev. 11087 Rebuild buildtool with "-fopenmp" and then you should be able to use the "-j" (20 parallel threads) option or e.g. "-j 4" (4 threads). Needless to say this speeds up a clean build tremendously on i7 2600K: 7 minutes. It is somewhat buggy, but who cares You have to run btool once more without "-j" to get a build done. Someone should be able to fix that... Cheers! Johan

2 1