- Inkscape Devel - Inkscape Mailman

10 Mar '08

Just my two cents worth on the release being held back by Windows; I think that, regardless of your position on Windows as an operating system, or Windows users, that putting out a release that is crippled would be downright humiliating to the *whole* Inkscape project. Let's ask, what is pushing us so hard to get the next release out? In a lot of these projects there is an impetus based on saving face, which is about bringing new features to fruition. IMHO, the saving face needs to be done by being a little patient, or at the very least not releasing 0.46 for Windows until it is pretty right. Again, what is the aim? Is it purely to further the name of Inkscape, or is there at least some desire to further SVG as a viable option is a largely proprietary world? I have heard that said a number of times, and used as a reason to include or reject features. This project is meant to be about a good SVG editor, and the rest is a nice by-product. Again, a good reason to hold off just a little. Let us also ask, if Linux users are so technically superior, aren't they already using the release candidate, which offers pretty much what the release will? Surely even the nightlies are very stable by now if all the bugs are ironed out. If so, in at least one sense who cares if there's a release if the RC is working and those who want the release are already using it! Linux users are well and truly used to beta and release candidates, and in fact the pure only use the bleeding edge stuff and look down on those who don't. Or are we next going to start railing against Ubuntu users for their lack of technical expertise, and because they need a packaged version? Afterall, isn't Ubuntu trying to attract that Windows-like person? Lets please hold off just a little, at the very least on the Windows release. For many Linux users it makes no difference whether or not there's an official release, because the pre2 package is stable. For the Windows users, and the reputation of Inkscape, SVG, and even FOSS, it makes a huge difference. -- View this message in context: http://www.nabble.com/0.46-release-debate-tp15773115p15773115.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

22 49

Automake files
by Bob Jamison 10 Mar '08

10 Mar '08

Hi, I committed some more code tonight, including a new Makefile_insert in /src/bind. We played with this for hours trying to get the wrinkles out, and I -think- it works now. But if anyone has any problems, and they know how to work with automake, please look at /src/bind/Makefile_insert and where it is referenced by /src/Makefile.am. I think that the general rule is that every time a Makefile_insert is added, Makefile.am needs to be touched, or autogen run. Thanks. bob

1 0

Additions to build.xml
by Bob Jamison 10 Mar '08

10 Mar '08

Hi all. This is just a note to let users of buildtool that I added a few things to build.xml to enable the building of the JVM binding. I commented the 3 places that allow /src/bind to be built, so it shouldn't break your builds. However, the new <javac> tag and and <property environment=""/> tag might require you to compile buildtool.cpp again to avoid parse errors. Let me know if you have any problems. bob(ishmal)

3 8

Extended input and "keys"
by Jon A. Cruz 09 Mar '08

09 Mar '08

Hi, I'm trying to find out if anyone has successfully gotten the "keys" settings under the "Input Devices..." dialog to actually do anything. So far on Ubuntu 7.10 I've been unable to get them reacting with my Wacom. I'm very interested in anyone getting them to work, since I'm doing a replacement for that dialog and am almost ready to check in the first round. Thanks for any feedback.

1 0

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