@Josh - The upstream developer sounded very positive about accepting some/all of our changes (https://bugzilla.gnome.org/show_bug.cgi?id=652248). I guess the focus-switching is the most critical issue... we can live without icons, and as per the preceding discussion, it should be possible just to use the existing API if we decide we want to. I have asked Johannes from gdl if he would be happy to add this feature and if he can estimate an ETA.
AV
On 13 June 2011 05:32, Jon Cruz <jon@...18...> wrote:
On Jun 12, 2011, at 7:21 PM, Josh Andler wrote:
2011/6/12 Jon Cruz <jon@...18...>
First and foremost I was pointing out that existing code already allows one to achieve the needed goal without adding any changes to the library. Pushing out changes to app code that require end users to wait for their distros to pick up new versions of libs (or, more often, to wait and then upgrade to a newer distro to get newer libs) is often a poor choice.
Often a poor choice? Yes. Sometimes for the betterment of the project? Yes. 0.49 or whatever version it will end up as is truly a game changer for us. New versioning scheme, it appears the cmake cross-platform building will take, cairo renderer, purging our internal copies of libcroco (of which Abhishek is now a maintainer) & libgdl... to me, this release will really be one of those "you're best off on the most up-to-date distros" releases. Will we require it? No. Will there possibly be known issues with older libraries. Yes. I'm making this as a general statement, not just in regards to any patches we may be waiting for gdl to accept.
That is true... however the main point in this specific case is that the functionality under discussion (icons) can be achieved without changing any API's and pushing things out to external libs. And combined with the fact that the one change being looked at introduces many problems, avoiding a lib API change can be good here.
EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel