Andreas Beck wrote:
>
> > * separation of UI and model domain
> > * centralized configuration of UI related stuff (look & feel)
>
> Do I get you right, that then Berlin has kind of "server side widgets" ?
>
> I.e. the widgets don't get created by the client, but rather by the server,
> and the client is only specifying geometry and such ? Cool.
Almost. Berlin's central element is the scene graph. It is composed out of
lightweight 'Graphic' nodes. These Graphics are very differently implemented,
depending on the precise job they are designed to fulfill. It's like LEGO.
You have a graphic which sets the current trafo, another which sets the current
texture, another which is a composite and thus lays out its children in a specific
way, yet another one intercepts and deals with events. You get the idea.
Out of these basic building blocks we create widgets. Widgets are nothing but
specific compositions out of these building blocks. You now have two choices:
Either you stick together the elementary blocks (remotely, from within the client),
or you ask an existing server side factory (also remotely, from within the client),
to do that for you. In both cases, the scene graph stays completely within the
server, even though you can access and manipulate it from within clients.
Fast operations such as traversals will completely stay inside the server, i.e.
the client never realizes that the scene graph is being redrawn, or an event is
delivered to an event handling node (a 'Controller').
Regards, Stefan
_______________________________________________________
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: [EMAIL PROTECTED]
_______________________________________________________
...ich hab' noch einen Koffer in Berlin...
