Hey all, This is where 0.48 as a "release" begins! This email will be a little redundant for developers, but will let users know what the current plan is. The next stage (Frost) kicks into gear at the beginning of March in case you were wondering. For right now: *New feature development will focus on wrapping up. *We will identify "make check" issues (we need to make sure things are "friendly" for packaging). *We will run an About Screen contest on DeviantART (which I will announce within the next 24 hours and post all info to both lists). *Ensure that the Release Notes are at First Draft stage. This is primarily a developer task, however, if you are a user and follow development closely and have something to contribute in this area which we may have overlooked, such as fixed bugs, changes in functionality, etc. please contribute. *Update tutorials and other docs (we could use volunteers). Not joking, if you are an Inkscape user and have the misconception that the only way you can contribute is by code, you are missing out on one of the most important things for our users... documentation. If you have time to spare and some tips for others that you're willing to share, please let us know. --- boring developer junk --- I do want to request from developers... most "big" new stuff be committed by March 1st if possible (or shortly thereafter). JonCruz: The swatch previews for "auto" swatches are starting to worry me given that they have not been working for quite a while now (since 0.47 dev cycle). The same goes for the method of editing color (gradient editor rather than F&S dialog). If you will not have time to address these before Freeze, please expect that I will request the feature is disabled again for this release at that time... I will also request that in 0.49 that you not re-enable it until you are looking to actively work on it. Krzysztof: The new Node Tool is fantastic. I know you're actively working on it, but I do just want to make sure that you will be able to set aside a few hours here and there for bugfixing as there are still a number of bugs and features missing from previous releases. Arcadie/Michael: The Connector Tool really is not consistent with the behavior of other tools. If it is not likely to be sorted out by Freeze, I will request that at least the tool controls button for "add connection point" be disabled, as it is not user friendly at this point. Please know that I am not targeting people or criticizing their work. This is a schedule issue and our date of release was horribly far behind schedule for the past couple releases. We will just be sticking to release schedules much more strictly than we have previously, and if features aren't "bug-free"/complete enough to release on time... there's always next release! :) Besides, we're going to be in the trenches w/ 0.49 for a bit by what has been discussed so far. Cheers, Josh ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user

I gave up after having to find, download and build 12 dependent libraries on my RedHat Enterprise #4 box.

Diederik van Lierop wrote: > On Wed, 17 Feb 2010 09:10:20 -0500, "william.crocker@...2677..." > <william.crocker@...2677...> wrote: >> I gave up after having to find, download and build >> 12 dependent libraries on my RedHat Enterprise #4 box. > > Seriously, get yourself a windows machine ;-) Although the majority of the > devs are using Linux, for some reason nothing can beat the windows > environment when it comes to compiling easily. You'll only have to > download > the bundled set of libraries and off you go! > > More realistically, can't you use a recent fedora install, either parallel > boot or virtualized? I guess it's just a matter of Red Hat 4 being out of > date, and us devs using very recent libraries. You will only need this: > > sudo yum install ImageMagick-c++-devel ImageMagick-c++ ImageMagick-devel > ImageMagick glibmm24-devel libsigc++-devel gtkmm24-devel glibmm24 > libsigc++ > gtkmm24 intltool gc gc-devel lcms lcms-devel gsl gsl-devel libxml2-devel > libxslt-devel boost-devel popt-static poppler-devel inkscape > You're out of control. I rest my case. :-)

I see an attempt at documenting the libs required to build Inkscape here: http://wiki.inkscape.org/wiki/index.php/CompilingInkscape, but this can not be trusted. For example, the Solaris page talks about version 0.44 Maybe this *is* a documentation problem. The README file broaches the subject with references to the likes of Boehm-GC and gtkmm, but does not specify version numbers. I suggest the README file include the specific list of dependent libraries and their version numbers as recommended to build the associated version of Inkscape. If they were listed in bottom-up or top-down order; that would just be so much more helpful. There is little more frustrating than taking an hour to find download and build your tenth component just to have it complain about needing three more. When will it end.... Bill Utopia: A world where the inhabitants use operating systems which are less than five years old and the "file system" stops at the RJ45 connector on the back of the box.

> It might be a good idea to inquire (on irc or this list) as to how that > wiki page could be updated, and then update it once you find that the > solution works. It would certainly be beneficial to others as well. > > Oops. Now I have homework. I will forge ahead and see if I can build Inkscape here in the 19th century. If so, I will document the libraries which I used, their versions and the apparent build order. I can then publish that information, but it will have a finite life-time as with the information referenced above. The developers, as part of a significant release really need to tell the world how they did it; What libraries are required and what versions. That information should be in the release notes and Wikis should reference up to date release notes, not release notes referencing out of date Wikis as we have here. This will take some time as I have a low threshold of pain. Nobody is to hold their breath. Bill

> Oops. Now I have homework. > > I will forge ahead and see if I can build Inkscape > here in the 19th century. If so, I will document the libraries > which I used, their versions and the apparent build order. > I can then publish that information, but it will have a finite > life-time as with the information referenced above.

> I don't believe it, but I am looking at Inkscape 0.47 > running on my RedHat #4 machine. > > What would you like me to do with this information? http://wiki.inkscape.org/wiki/index.php/CompilingRHEL will most likely be the best place to put it. It is currently empty so feel free to form it to your will. You will also need to add a RHEL link to the http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape page.

More realistically, can't you use a recent fedora install, either parallel boot or virtualized? I guess it's just a matter of Red Hat 4 being out of date, ...

Hey all, This is where 0.48 as a "release" begins! This email will be a little redundant for developers, but will let users know what the current plan is. The next stage (Frost) kicks into gear at the beginning of March in case you were wondering. For right now: *New feature development will focus on wrapping up. *We will identify "make check" issues (we need to make sure things are "friendly" for packaging). *We will run an About Screen contest on DeviantART (which I will announce within the next 24 hours and post all info to both lists). *Ensure that the Release Notes are at First Draft stage. This is primarily a developer task, however, if you are a user and follow development closely and have something to contribute in this area which we may have overlooked, such as fixed bugs, changes in functionality, etc. please contribute. *Update tutorials and other docs (we could use volunteers). Not joking, if you are an Inkscape user and have the misconception that the only way you can contribute is by code, you are missing out on one of the most important things for our users... documentation. If you have time to spare and some tips for others that you're willing to share, please let us know.