- Inkscape Devel - Inkscape Mailman

Python bindings
by pradeep.pyro 09 Feb '14

09 Feb '14

Hi, Which version of the lib2geom Python bindings is recommended for use: Boost-Python or Cython? I can build both versions on Windows, but I cannot use them. Here is the error that I receive when I import either of the modules: >>> import cy2geom Traceback (most recent call last): File "<stdin>", line 1, in <module> File "cy2geom.pyx", line 5, in init cy2geom (C:\Users\xxx\Desktop\lib2geom\build\src\2geom\cython-bindings\cy2geom.cxx:1094) ImportError: DLL load failed: The specified procedure could not be found. I followed the exact build and install procedure found in the README.win32 document. Appreciate any help on this, thanks. Best regards, - Pradeep -- View this message in context: http://inkscape.13.x6.nabble.com/Python-bindings-tp4969424.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

5 5

std::string with char*
by Tavmjong Bah 07 Feb '14

07 Feb '14

Hi, It is good we are slowly moving to using std::string... but mixing it with char* can be tricky. In particular, I've seen several bugs recently when char* is a null pointer. You cannot initialize a std::string with a null pointer. You will get at run time: terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid I don't know what "best practice" is but this seems to work: std::string my_string = c_string ? c_string : ""; You can also not compare a std::string to a null pointer. Tav

3 2

Inkscape Trademark Policy
by Bryce Harrington 05 Feb '14

05 Feb '14

Hi all, One of the Inkscape Board's actions in 2013 was to establish a trademark policy for the Inkscape name and logo. With the Software Freedom Conservancy's help we've completed the registration and documented under the About menu item on the website: http://inkscape.org/en/about/trademark-policy/ The motivation for doing this was due to questions that kept cropping up from people wanting to use it for legitimate purposes (e.g. using our unmodified logo on merchandise), and from people noticing our trademark used illegitimately (e.g. selling unrelated software using our name or logo). We wanted a policy that would provide clear guidance for all these uses, that would be liberally permissive for non-commercial and FOSS-friendly commercial uses, while prohibiting obviously fraudulent uses. Along with this, I've added a FAQ entry (below) with a brief summary. Bryce == FAQ: How are the Inkscape name and logo protected? == The Inkscape name is trademarked under U.S. Trademark Law, and held and administered by the Software Freedom Conservancy. Our policy is available on the website, and describes the conditions under which you can use our name and logo. We've aimed to make our requirements reasonable and friendly: We want to avoid things like other groups claiming to be or represent us when they don't, or to distribute our software in ways that aren't consistent with our license. The logo is similarly trademarked and covered by our trademark policy. We're cool with people creating derivative works that help promote Inkscape or make it fit in with a given user interface style, but we don't want to see it abused by companies that might incorporate it into their own logos. For merchandising, you are welcomed to use our unmodified logo; for anything else, please contact the Inkscape Board for permission.

2 1

Re: [Inkscape-devel] Making inkscape usable in valgrind grumble
by mathog 05 Feb '14

05 Feb '14

On 03-Feb-2014 20:01, Krzysztof Kosiński wrote: > In the long term, I think the consensus is that we should move away > from garbage collection and towards explicit memory management with > smart pointers. In the short term, I'm afraid there is little we can > do about this. The initial pieces of the puzzle are already in place > with the C++ification work on the SP tree. Apparently the current GC does not call destructors when it automatically removes memory. Inkscape has code in gc-finalized to tack a destructor onto an entry, but it isn't easy to see how often it is employed (grep shows "Finalized" in only a handful of source of files), and gc-finalized.h lists several caveats, which say that there are lots of situations where it might never act even if invoked. > GC is mainly used in code related to XML and undo handling. Removing > GC there requires modifying every piece of code that creates or > deletes XML nodes - at least 277 places according to grep. Speaking of that section, is there some debugger trick for keeping track of the objects that that code creates and deletes? I've been trying to follow it in gdb but since the memory pointers move around from run to run, and just running gdb seems to change what inkscape does (probably because mouse events are caught in strange ways, or windows overlap), it is really tedious. I ask because my text decoration mods blow up in style.cpp in sp_style_paint_server_ref_modified() when a certain simple object is selected on the drawing surface and then copied - but not if it is cloned. That object is just this: <text style="font-size:40px;fill:none;stroke:url(#MyPattern);stroke-width:5;" y="40"><tspan>A<tspan style="text-decoration:underline">B</tspan></tspan></text> The copy (==^C) triggers an insane amount of activity which passes in and out of style.cpp, where signals are attached and detached, apparently to/from the same objects much of the time, until eventually it drops into the function mentioned above with a PaintServer server that no longer matches the ones in style->stroke and style->text_decoration_stroke (which match each other), which triggers the crash. (After having previously been in that same function maybe a dozen times without issue.) It is my impression that there is vastly more activity for this simple copy then there is in just reading in that section of the file in the first place. (It definitely calls sp_style_write_string() at least 2 times for each of the styles in the section being copied, probably because execution control is through the setting and resetting of modified flags, rather than by doing a single "atomic" 1:1 copy.) Conversely, this object: <text style="font-size:40px;fill:url(#MyPattern);stroke:none" y="40"><tspan>A<tspan style="text-decoration:underline">B</tspan></tspan></text> copies without issue. It too triggers a lot of activity, including redundant sp_style_write_string() calls, but somehow it avoids whatever pitfall the first one falls into. As far as I can tell the implementations for style->text_decoration_fill and style->text_decoration_stroke are symmetrical, so why one crashes, and the other doesn't is pretty mysterious at present. It has something to do with the paintServer href, since there are no problems with text_decoration_stroke when it does not use a pattern or a gradient. Tracing execution in this region is no fun since much of it is driven by signals that trigger calls to stored references to functions. I can watch it creating patterns, objects, and styles, but figuring out which is which solely from their pointers, which change from run to run, is not a lot of fun. Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

1 0

New to Inkscape
by gagan 04 Feb '14

04 Feb '14

Hey all, I am a new user here at Inkscape and don't know what to do. I want to contribute to this projects as a developer; can anyone help me out where to start. Thanks in advance -- Thanks Gaganjyot http://codeify.wordpress.com "Jai Sai Naath"

3 2

LGM 2014 Leipzig
by Tavmjong Bah 04 Feb '14

04 Feb '14

Hi, If the Inkscape board were to offer some financial support to attend LGM (April 2-5 in Leipzig, Germany)[1] who would be interested in attending the meeting? There will be people from Gimp, FontForge, Scribus, etc. as well as a number of SVG Working Group members there. At the moment, I am the only one I know from Inkscape (besides Alexandre Prokoudine and Sirko Kempter, both LGM organizers) who is signed up to attend. Tav [1] http://libregraphicsmeeting.org/2014/

1 0

Future plans for XML namespaces in Inkscape and SVG 2
by Jarek Foksa 03 Feb '14

03 Feb '14

Are there any plans for Inkscape to move away from XML namespaces when SVG 2, HTML 5 and Web Components will become widely supported and XML namespaces will get deprecated? If this is the case, I think it would be great opportunity to clean up the current namespace mess. Ideally, I would like to see all vendors of SVG editors to agree on a common “editor” namespace that would be implemented with HTML 5 data- attributes and custom elements. My proposal: 1. Drop “dc:", "cc:" and "rdf:" namespaces and remove any elements and attributes using them as this is just useless noise. 2. Drop "xlink:" namespace prefix (as defined by the SVG 2 spec). 3. Convert all elements in “inkscape:" and "sodipodi:" namespace to custom elements with "editor-" prefix (as defined by Web Components spec) 4. Convert all attributes in “inkscape:” and "sodipodi:" namespace to data- attributes (as defined by HTML 5 spec). For example following SVG 1.1 document generated by current stable version of Inkscape: <svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" version="1.0" width="1000" height="2000" viewBox="0 0 1000 2000"> <sodipodi:namedview pagecolor="#ffffff" bordercolor="#666666" borderopacity="1" objecttolerance="10" gridtolerance="10" guidetolerance="10" inkscape:pageopacity="0" inkscape:pageshadow="2" inkscape:window-width="1366" inkscape:window-height="689" id="namedview1530" showgrid="false" inkscape:zoom="0.57" inkscape:cx="542.23281" inkscape:cy="1495.4813" inkscape:window-x="0" inkscape:window-y="27" inkscape:window-maximized="1" inkscape:current-layer="svg2"/> <image sodipodi:absref="/image.png" xlink:href="image.png" width="950" height="632"/> <path inkscape:connector-curvature="0" d="M 60,10 L -40,-45"/> </svg> ... could become this in future when saved as SVG 2 document: <graphics width="1000" height="2000" viewbox="0 0 1000 2000"> <defs> <editor-namedview pagecolor="#ffffff" bordercolor="#666666" borderopacity="1" objecttolerance="10" gridtolerance="10" guidetolerance="10" pageopacity="0" pageshadow="2" windowwidth="1366" windowheight="689" id="namedview1530" showgrid="false" zoom="0.57" cx="542.23281" cy="1495.4813" windowx="0" windowy="27" windowmaximized="1" currentlayer="svg2"> </editor-namedview> </defs> <image data-editor-absref="/image.png" href="image.png" width="950" height="632"/> <path data-editor-connector-curvature="0" d="M 60,10 L -40,-45"/> </graphics> Some related documents: - Custom elements: http://w3c.github.io/webcomponents/spec/custom/ - Proposal for improving SVG DOM: http://dev.w3.org/SVG/proposals/improving-svg-dom/ - Data attributes: http://www.whatwg.org/specs/web-apps/current-work/#embedding-custom-non-vis… Do you think this has any chance to get adopted by Inkscape? If not, do you have any alternative plan to improve the way how Inkscape stores non-standard data in SVG documents in the upcoming post-XML future?

5 8

wiki account
by Masanori Kanazu 03 Feb '14

03 Feb '14

Hi, I would like to contribute to the translation of Inkscape wiki into Japanese. I already finished translating these two articles. http://wiki.inkscape.org/wiki/index.php/Inkscape_for_Adobe_Illustrator_users http://wiki.inkscape.org/wiki/index.php/AdobeToolMap Could you please create a wiki account with username "mkanazu" for me? regards, Masanori Kanazu

2 1

Future plans for XML namespaces in Inkscape and SVG 2
by Jelle Mulder 03 Feb '14

03 Feb '14

Hi all, If anything I think the namespaces et al should be optional by using export switches. That would allow every user to create his own specified exports. Currently the is the Inkscape SVG file and plain SVG and optimised SVG, but I think it would be way more useful if there were just two kinds of SVG files. Inkscape native and export, the latter of which could be optimised with switches. If you'd then have a list of templates for optimisation (with a description on what it is used for)that would set these switches for the users, it would facilitate the user to find the right flavor of SVG. Currently you'll have to handcode a lot to create the right flavor and using such export facilities would simplify the process. In any case removing the XML namespaces doesn't feel like a good option as long as many people are using legacy software to get their SVG to parse right. Blink of all parsers imho is NOT the default to go with when it comes to parsing SVG and there are more things done with SVG than just produce content for the Android platform. SVG 2 seems still very much in flux and I would suggest not doing anything drastic until the recommendation level is reached, regardless of what a juggernaut like Google is doing. I guess they're flexible enough when it comes to exploiting standards for their own benefit as do all the others to try and push things their way, but that is basically what standards are for. To force the monopolists to adhere to standards. Not the other way around. Google in that respect can have a look at what happened to MS the past decade. And it may very well be the opening that MS would like to see if Google would divert. There are several products Google tried and dropped as well, without a blink. Please stick to the standard with tenacity. Any decent developer can handle the bloat. Oh,.. and... Happy Chinese New Year! Jelle Mulder

1 0

Waf build system, second try
by Krzysztof Kosiński 01 Feb '14

01 Feb '14

Hello everyone, I conducted an experiment in building Inkscape with Waf, redoing the work I did a long time ago with a newer version (1.7.15) and using more of its features. A correct build of Inkscape, with internal libraries built separately, "inklib" built as a shared library, Bazaar revision fetching and .po file compilation, requires less than 250 lines of Python script (!!!). I read on some mailing lists that Debian refused to package some software using Waf, because Debian considers shipping the "Waf binary" to be incompatible with the DFSG. I circumvented this problem by adding the Waf source distribution to the tree, which is a little bigger, but DFSG-compliant and works exactly the same. The code will be up shortly at lp:~tweenk/inkscape/waf-build, if anyone wants to check it out. Regards, Krzysztof

10 28