Erik introduced the Journal/datastore to this thread about modifying the approach Sugar has taken to WM in order to better support legacy applications, The Gimp being everyone's favorite example. I am simply suggesting that the WM is--while not the least of our problems--less of an issue than resolving incompatibilities between libraries (The Gimp pulls in all sorts of stuff and Inkscape tries to pull in incompatible libraries, such as an old version of poppler), incompatibilities with where we'd like applications to write data (The Gimp will stomp all over the filesystem), moving data to and from the Journal (how do I open an image I took with Record in The Gimp? or use a picture I edited with The Gimp in Memorize)? The fact that The Gimp uses lots of little auxiliary windows is easily dealt with in, for example, the X Activity. Making this seamless in Sugar seems, IMHO, a relatively low priority relative to these other inconsistencies.
-walter On Wed, Sep 24, 2008 at 4:26 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > On Wed, Sep 24, 2008 at 04:16:17PM -0400, Walter Bender wrote: >> >> We all agree that the datastore needs serious attention, although it >> doesn't directly impact the running of legacy activities. Rainbow is >> an issue. And moving data back and forth between Sugar and legacy apps >> is an issue. > > Please say more. > > Thanks, > > Michael > -- Walter Bender Sugar Labs http://www.sugarlabs.org _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel