March 2008 - Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] skeletal-stroke offset parameters
by bulia byak 09 Mar '08

09 Mar '08

On Sun, Mar 9, 2008 at 10:16 AM, jf barraud <jf.barraud@...400...> wrote: > Thks. The label has to be changed (it's not good anyway), yes. Not sure if I > should also change the code to really use %. > Do we have a common practice with this respect (expressing proportional > quantities as % or ratio) ? This is similar to stroking a path, and in that area things are normally in units of stroke width (such as miter limit or marker size). So I think you just need to change the label. > Argh! Writing this I realize there should maybe be only one check box (the > same as the one for the one for the y scale factor) (?!) > This would simplify the UI, at a low freedom cost (?). In the opposite > direction, there could be one check box for each parameter (space, > normal/tangential offset...). Yes, I think it makes sense to have just one checkbox for "all sizes and intervals in units of length". Even better is to have a regular unit selector there, where you'll have all the absolute units as well as % (and in that case, the spinboxes will have to use % and not units of width, but that is not so important after all). > Another remark is that we should decide what level of details we want in the > UI: > for instance there are at least 3 ways of stretching things to precisely fit > the skeleton length: > you can stretch > -pattern+space > -space only, keeping pattern width fixed > -pattern only, keeping spaces fixed For that, in the "Pattern copies" list, we can have these options: - Single - Single, stretched to fit - Repeated - Repeated, stretched to fit - Repeated, spaced to fit I think this will take care of most practical needs. -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org

1 0

skeletal-stroke offset parameters
by jf barraud 09 Mar '08

09 Mar '08

Hi all, I just added the offset parameters in lpe-skeletal-stroke again. They can otpionaly be expressed in proportion of pattern size. Thank you for testing and commenting (is this the behaviour we want to have?). Dunno if there is the faintest chance to have this in some 0.46.x...(?) If it stabilize fast enough, I think it would be nice since it greatly emproves the usability of the effect... Bye, jf.

2 1

Inkscape development on Windows with Dev-C++
by g mak 08 Mar '08

08 Mar '08

Hi, I am not sure if this would help, it has been a long time since I've done any development, especially on the Windows platform. However, I have invested a little time to attempt to get Inkscape to work with Dev-C++, and would like to see if anyone else is interested to share the experience. Thanks to JonY's help, I can get Inkscape to build with the buildtool (btool), so I used build.xml in the inkscape home directory as a reference to setup Dev-C++. Here is what I have done: - install Dev-C++ in c:\Dev-Cpp - I downloaded devcpp-4.9.9.2_nomingw_setup.exe from http://www.bloodshed.net/devcpp.html - install Inkscape in c:\inks1, and the support library c:\devlibs, I had the 0.45 plus the SVN as instructed by JonY - Note: Please keep in mind that the above locations are relative if you would like to use my Dev-C++ Configuration File and Project File. - Depends on how you install MinGw and GCC, you may wanted to add c:\mingw\bin in your PATH environment variable so Dev-C++ can get to GCC, may be in the future c:\devlibs can include GCC as well, I can only find gdb there only, we will leave it for the pros for those decision. - Create a folder "inkwin32" under c:\Dev-Cpp, and download this attached file "inkwin32_devcpp". It is the Dev-Cpp Configuration File. - Start Dev-C++, select "Tools]Files & Directories]", check "Use this alternate configuration file" and enter "C:\Dev-Cpp\inkwin32\inkwin32_devcpp". - Re-start Dev-C++, it will read in the configuration, which set up: - "Tools]Compiler Options]Compiler]" - the "compile" and "link" target from buildtool - "Tools]Compiler Options]Directories]" - the C++ include libraries. This I needed to check out again, some may be duplicated with the compiler option. I am not sure. - Download the attached project file "inkwin32.dev" to c:\Dev-Cpp. It is not complete, but has references all the source files in ~/src, ~/src/dialogs and ~src/ui. This is a easy to read text file, may be buildtool can create it in the future, if Dev-Cpp is the way to go. I stopped where I am so I can check out the compilation and see if this can be progress any further. - To compile, simply F9 ("Execute]Compile]"). I have marked the following files not to be included with the compile, (inkscape, inkview, interface, sp-fediffuselighting, sp-fespecularlighting, sp-filter, verbs, dialogs/filedialog-win32 (excluded in buildtool as well), dialogs/fill-style, dialogs/layer-panel), they caused the problem with magick with errors such as: - 'MagickExport' does not name a type - 'ClassType' does not name a type - 'Quantum' does not name a type which I cannot google meaning resolution. Anyone interested in going forward?

1 0

gdb problem on Win
by Mihaela 08 Mar '08

08 Mar '08

1 0

Inkscape 0.46pre3
by Ted Gould 08 Mar '08

08 Mar '08

Hello Inkscapers, We've put out another pre-release of Inkscape. As we're getting very close to releasing 0.46 on platforms other than Windows testing is critical. On Windows, there are some release blocking bugs that could use developer attention. If you're a Windows developer please come help. If not, but you know one, time to buy him/her their favorite pizza and beer then tie them to a chair :) [1] --- All bugs should be submitted to --- http://bugs.launchpad.net/inkscape/ --- Release --- https://sourceforge.net/project/showfiles.php?group_id=93438&package_id=991… --- MD5Sums --- 0daed93fbf24da295499d844b54be621 inkscape-0.45+0.46pre3.tar.bz2 d486eb8b02641b90cb7750afd8477efc inkscape-0.45+0.46pre3.tar.bz2.sig 39a5d9451120cf953a811d6dde92adfe inkscape-0.45+0.46pre3.tar.gz 635ed77f488d2bf18b2c2be19cf900bc inkscape-0.45+0.46pre3.tar.gz.sig 427584d96ef0f07d5b78c74e96414a6b inkscape-0.45+0.46pre3.zip 190ca9ee4f96e180ce851bcb7bdd99f1 inkscape-0.45+0.46pre3.zip.sig Thank you everyone for continuing to use and help out with Inkscape. --Ted [1] Neither Ted nor the Inkscape project encourage violence towards Windows developers. They're all future Linux developers ;)

5 5

0.46.x stable branch practices for bugs and patches
by Bryce Harrington 07 Mar '08

07 Mar '08

With 0.46.0 nearly finished, bug fixes for our release should be targeted to 0.46.1. For 0.46.x we want just critical bugs: crashes, data loss, security vulnerabilities, severe regression, failure to build, etc. To mark an acceptable bug as needing fixed in a Stable Release, please 'milestone' it to 0.46.1 (or 0.46.2, ...) To mark a patch for an acceptable bug as needing integrated into the Stable Release: 1. Attach the patch to the bug report. 2. Confirm that the fix is in the main development trunk. 3. 'Nominate it for release' in launchpad for 0.46.x 4. Include this information: * Justification why its release-critical * Steps to reproduce * Explanation of the patch * Discussion of regression potential (Translation updates only need to follow steps 1-3) This makes it easier both for us to review patches, and for distro packagers to cherrypick and backport them. A more detailed version of this is at: http://wiki.inkscape.org/wiki/index.php/StableBranchUpdates Thanks, Bryce

1 0

Inkscape 0.46-final plans (March 10th)
by Bryce Harrington 07 Mar '08

07 Mar '08

ScislaC and I are quite pleased with how -pre3 has shaped up, and are making the last call for 0.46.0 bug fixes, translations, etc. We will tag 0.46.0 at UTC 04:00 Mar 11 2008. I've incorporated all patches sent to me or nominated for 0.46.x. If you have something I've missed, please get it to me this weekend. There are 7 milestoned bugs left: 3 are translations, 3 are windows-specific, and 1 has a patch that just needs a quick test. The translation patches I trust will be squared away in the coming days. Bug 189432 has a fix committed to trunk for upside down text with PDF, that just needs checked and I can commit the patch. For any remaining translation work, please arrange to get it incorporated in the release branch by March 10th. For the 3 windows bugs, progress has been slow on these. The consensus from the lengthy "0.46 release debate" thread is to tag 0.46.0 for Linux so we can get the release into Ubuntu and Fedora (which have a drop-dead date of March 13th for getting new Inkscape incorporated), but hold off on PR two weeks to give the extra time for Windows developers, because we would prefer to have full platform support for maximum PR effectiveness. If the Windows bugs are not sufficiently resolved by March 24th, we'll proceed with 0.46.0 being a non-Windows release, and hope they can be addressed in time for 0.46.1. Bryce

1 0

LGM 3 Presentation call — Heya!!!
by Louis Desjardins 07 Mar '08

07 Mar '08

Heya! Time to get yourself on the wiki for your presentations at LGM 3... it's coming! May 8-9-10-11 yes! 4 days! in Wroclaw, Poland, just 5-hour train ride from Berlin. http://create.freedesktop.org/wiki/index.php/Conference Please, don't be shy! Louis p.s. let us know you'll be there too. The Create List is our preferred one for talking most LGM stuff. Or get on IRC at freenode #lgm — Cheers!!!

5 5

Re: [Inkscape-devel] [Fwd: Re: Extensions on win32]
by Aaron Spike 06 Mar '08

06 Mar '08

Ted Gould wrote: > -------- Forwarded Message -------- > From: Ted Gould <ted@...11...> > To: bulia byak <buliabyak@...400...>, Aaron Spike <aaron@...749...> > Cc: Inkscape Devel List <inkscape-devel(a)lists.sourceforge.net> > Subject: Re: [Inkscape-devel] Extensions on win32 > Date: Sun, 02 Mar 2008 21:00:16 -0800 > > On Sun, 2008-03-02 at 20:01 -0400, bulia byak wrote: >> On Sun, Mar 2, 2008 at 9:59 AM, <J.B.C.Engelen@...1578...> wrote: >>> Now there should be a somewhat cleaner/better fix, however these two effects are broken again. The effects run successfully, but the parameters are not passed correctly. >> In rev 17608, function plotter works but dimensions and add nodes do >> not. Ted, can you please look into whether this might be caused by >> your recent fixes? > > With "Add Nodes" I get: > > Traceback (most recent call last): > File > "/home/ted/Development/inkscape.work/install/share/inkscape/extensions/addnodes.py", line 91, in <module> > e.affect() > File > "/home/ted/Development/inkscape.work/install/share/inkscape/extensions/inkex.py", line 154, in affect > self.effect() > File > "/home/ted/Development/inkscape.work/install/share/inkscape/extensions/addnodes.py", line 81, in effect > splits = math.ceil(length/self.options.max) > ZeroDivisionError: float division The inx file would seem to indicate that a value of 0 for max is unallowed. Are these constraints no longer enforced? When you run add nodes do are you passing 0 for the parameter? <param name="max" type="float" min="0.1" max="10000.0" _gui-text="Maximum segment length (px)">10.0</param> > and with Dimensions I get: > > /home/ted/Development/inkscape.work/install/share/inkscape/extensions/dimension.py:60: TagNameWarning: Tag names must not contain ':', lxml 2.0 will enforce well-formed tag names as required by the XML specification. > marker.set('inkscape:stockid', name) > > Aaron, do you have any ideas on what these could be caused by? This is a real error in the script: marker.set('inkscape:stockid', name) should be: marker.set(inkex.addNS('stockid','inkscape'), name) Aaron

3 5

lpe-blueprint
by jf barraud 06 Mar '08

06 Mar '08

Hi all, I just added an lpe-blueprint<http://wiki.inkscape.org/wiki/index.php/Lpe-blueprint>on launchpad. The goal is to gather ideas/props about lpe futur generations. The first part is about stacking lpe's from the UI viewpoint. Individual effects specifications are also collected, including propositions of new effects... (notice that things are not supposed to be developped in a short term; in particular, handling full svg data as parameter or output might require a lot of work!...) Remarks, comments, additions are wellcome! jfb.

2 1