On Dec 7, 2007 3:53 PM, Murray Cumming <[EMAIL PROTECTED]> wrote: > For Openismus, I have started a tutorial to cover Clutter and to mention > a little about other libraries such as clutter-gtk and clutter-cairo and > maybe clutter-gst. I should have it finished in a week or so, and I'll > then keep it up to date with the API changes.
Hi, I finally managed to have a quick look through it and have some comments and questions I found lacking: Tutorial says 'Each Clutter application contains at least one ClutterStage' . IIRC currently clutter supports only one stage at a time. Then again, I haven't used clutter-gtk, which might lift that limitation. Worth mentioning I think. Events: There's clutter_set_motion_events_enabled(TRUE); and clutter_actor_set_reactive (rect, TRUE); kind of hidden in the code. It would be a good idea to mention those in the text as well. Would be good to explain ClutterActor::captured-event as well, with a simple illustration of event propagation. (There was one good one I saw about DOM events, but can't find it right now.) Timelines: Before starting with details of timelines etc. it would be good to have a quick overview of timelines, effects, alphas and behaviours in same paragraph. How is memory management for timelines meant to be done, i.e. when is it safe to unref a timeline? (Just had a situation where I wanted to make a fire and forget timeline and timeline_new(); start(); unref(); didn't actually complete the timeline.) Implementing actors: which functions are expected to be chained to parent? Before or after your own code? Contributing: comments to gtkmm-list, really? :-) Overall looks quite good, although the complete code examples, while very valuable to get runnable examples, make it harder to see at glance the relevant information from the boilerplate. (noisenoisenoisenoise clutter_behavior_path_new() noisenoisenoisenoise) Adding emphasis for code that is relevant to the current chapter, using bold or extracting snippets into the text, would help guide the reader. -- Tommi Komulainen [EMAIL PROTECTED] -- To unsubscribe send a mail to [EMAIL PROTECTED]
