On Mon, 2008-08-04 at 18:24 +0200, Dirk Meyer wrote: > So I propose that a kaa.candy.Widget HAS a clutter.Actor. I see the > following advantages: > > - Thread-safe because we do not modify a real clutter actor. One > single now_render function could be created to calculate stuff and > create the actors in the gobject mainloop > - Hide clutter API the user should no use > - Support layout
Yes, and this is basically how kaa.canvas worked. In fact, the actual underlying evas object creation was deferred, as was applying properties to the object. For evas, the deferring was done because you couldn't create evas objects without immediately tying them to a canvas, which worked against our earlier requirement of being able to move objects between canvases. You could do something similar here with candy, further abstracting and deferring object creation, which will let you more conveniently take care of all that in the clutter thread. I'm a bit surprised you didn't do it this way to begin with. I should have been paying attention to the candy check-ins, I would have said something. :) > I have no idea what the code does. It was copied from tidy. Maybe tidy > is already updated to 0.8 I found that code in toys/ but I didn't check tidy. It would be nice if that was updated to 0.8. My changes work fine for non-tiled textures, and it sounds like tiled textures didn't work right even with 0.6. > > -import clutter.cluttercairo > > +try: > > + import cluttercairo > > +except ImportError: > > + # 0.6 > > + import clutter.cluttercairo as cluttercairo > > There is clutter.__version__ Not really needed I think. Eventually we'll just remove that code anyway, once 0.6 is old enough. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
