On Sun, 2007-12-30 at 18:31 +0000, Emmanuele Bassi wrote: > On Sun, 2007-12-30 at 09:42 +0100, Murray Cumming wrote: > > > > it's also a matter of what kind of UIs Clutter targets: on the iPhone or > > > on small embedded devices I have yet to see a tree-like widget like a > > > full GtkTreeView showing a GtkTreeStore, for instance; the GtkListStore > > > is far more common. > > > > > > ClutterModel is targeted at tables/lists. if in the future there's some > > > need for trees, a ClutterModelTree can be added as well. > > > > Maybe ClutterListModel would be a better name then. > > it implies a false dichotomy: there is no "TreeModel" of sorts.
The name "ClutterModel" does not suggest anything about a tree. If I understand you, it's for lists of things, so it just seems obvious to have the word "list" in the name. Not all models are lists. > at the > moment, the only Model provided by Clutter is ClutterModel. if we're > going to add a new model abstraction class to Clutter before we reach > 1.0 then we could even rename ClutterModel to ClutterModelList or > ClutterListModel. > > as of now, there's no need to do it. > > > I imagined that this > > was some kind of model of the whole stage+actors. > > Clutter has no need for a global MVC architecture (mostly because we do > not allow multiple views of the same scenegraph); a ClutterModel could > be used to build a scene, though. in a way, a ClutterScript buffer could > also be seen as a model. > > > And I doubt that > > you'll never want some other type of data-structure model. > > as I said, at this moment and for the foreseeable future, we don't see > the need for another type of data-structure model to be added in Clutter > core; if another comes up, we can still add it without even requiring > API breaks. -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com -- To unsubscribe send a mail to [EMAIL PROTECTED]
