![](https://secure.gravatar.com/avatar/bb65b6b3a109d97cf9f8d6c014ede042.jpg?s=120&d=mm&r=g)
By the way, Alan has produced a collection of stock gradients, that we're going to try to package as part of openclipart (as opposed to bulking up the Inkscape tarball.) These will get installed to a directory somewhere in the /usr/share/. Is it possible to inform Inkscape of the location and identity of these gradients?
Yes but not in a short term. The plan is:
- switch marker menus to a new table-like widget that is updated on the fly and more responsive
- add the same widget and the ability to use stock items to patterns, gradients, symbols etc.
I spent some time testing it and playing with it. It works very well when compared with the usual RPM issues of finding/downloading various dependencies. I think it will help us a lot, especially given the new dependencies we've introduced recently, since it takes care of that for the user fairly seemlessly.
Good, then could you please publish a short version of my plea for help with Pango testing on the site, adding a link to the daily autopackage.
An issue is that we can publish a beta release for testing, get lots of testing input, but meanwhile developers will be adding bug fixes or even new code to the release branch. Ideally, betatesters would update frequently and re-test, but realistically I think we'll get at most one or two cycles of testing out of people.
Branching out a separate beta branch before the release is something we'll definitely need to do for 1.0, but for 0.39 it's perhaps more trouble than it's worth. It only makes sense for really long testing periods.
But what I think we can and should do is to allow several days of testing of a final release candidate with TOTAL freeze on CVS, and requiring a certain nunder of people to OK it before it is released.
_________________________________________________________________ STOP MORE SPAM with the MSN Premium and get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...