Hi; On Wed, 2008-01-30 at 20:52 +0100, Murray Cumming wrote: > > > > Will definitely do so! Its not so much total inaccuracies in API usage > > etc its just I think it misses detail where its important and feels > > quite dry (e.g. no diagrams) / impractical (animation stuff is not > > totally clear) - just a rather thin extension of the API docs > > The API documentation is rather bare. Much of the stuff in the > documentation could indeed be in the API documentation.
Hmm, maybe convert and send patches for that then ? Also I assume you mean bare as in detail ? Coverage at least is very high. > > > with some > > not so exciting examples > > As the documentation states, the examples are meant to be very simple so > that the new concepts are obvious and not lost in a sea of code. Im dont mean make them complex with lots of code - just look a little more interesting. I mean most just use a grey rectangle - surely just any kind of image would be more interesting/appealing. > The > "full example" should indeed be much more exciting (it's crappy) and I > hope that someone with more clutter-foo will one day do that. One thought would be make the tutorial center around building a more full featured app like this one - i.e each chapter adds more functionality adding the chapters features - Clutter is ideal for this kind of thing imho. > > > and rather strange descriptions (2.5D for > > example, '2D surfaces in 3D space' is better imho). > > Changed. I picked "2.5D" up from somewhere or other and it seemed to be > the one that Clutter people liked and understood. It was new to me. Ok. I thought Id moaned about 2.5D before (means populus style perspective to me) :/. Sorry. > > > Anyway dont take > > that the wrong way - I know it is not easy to write docs. Am likely > > going to write a 'chapter' on animation so I can show you what I mean. > > > > > > and is not > > > > totally in sync with current trunk. > > > > > > It should be. The examples build against trunk (they aren't just > > > copy/pasted in). > > > > > > > >From a quick look, I dont think the events and actor docs (event capture > > phase, > > I updated the events documentation after the previous discussion on the > list. See, for instance, the "Clutter first allows the stage to handle > each event via the captured-event signal" text here: > http://www.openismus.com/misc/clutter_tutorial/docs/tutorial/html/ch04s04.html > > If something else has changed since then about events then I can't see > it in the ChangeLog. Ok I did not see updated. What I would say though is the event workings are prime for a diagram explaining how it works. > > > anchor point, order of transformations etc). > > What part of the API should I be looking at to mention the "anchor > point" concept, and where is an order of transformations to be > discovered? I don't think they are mentioned at all yet in the tutorial. > > > I think GTK widget > > has had its namespace changed. > > Thanks. Fixed. GtkClutter changed to GtkClutterEmbed. Cool. > (and doesn't work any more for me, unfortunately: > ) Not so cool, could you log a bug ? > > I regularly rebuild clutter and clutter-documentation, but I guess I > forgot to rebuild clutter-gtk. > > > Also no info on new features of upcoming > > 0.6 - JSON, Shaders etc. > > I'm waiting for someone with more clue than me to provide some kind of > example. The lack of these new features in the tutorial doesn't make the > tutorial bad though. Check toys/ and test/ . Neither should be that hard to figure out. > > Other missing stuff (already marked by TODO) is waiting for the > high-level library (with boxes, scroll window, etc) to be released so I > can take something reasonable sensible as inspiration. > Ok, but note we do not (hopefully) expect there to be just one high level specific looking library on top of Clutter but many :) Many thanks; == Matthew -- To unsubscribe send a mail to [EMAIL PROTECTED]
