RE: [Widex] Proposed rewording for Framework draft

["Jin Yu" <[e-mail]>]

> Vlad writes:
> 
> >> The "explicit view" on the Widex Server is when the UI exported
> >> through Widex is of a desktop application, case in which a
> >> physical view is kept also on the Widex Server.
> 
> Jin responds:
> 
> > What's the difference between desktop app and non-desktop app? If
> > you are referring to web apps, then I don't see a difference here.
> > In both cases, the server would keep a virtual DOM / view (e.g.
> > HTML DOM for web app, XUL DOM for desktop app), and the physical
> > view is kept in the renderer.
> >
> > Or perhaps when you say desktop app, you are referring to
> > X11-based app. In that case, the roles are reversed. The server is
> > indeed keeping a physical view, whereas the client is keeping a
> > virtual view. To me, Widex is the reverse of X11, so I guess our
> > Widex server shouldn't be keeping physical view.
> 
> I believe that whether or not the Widex Server maintains an
> explicit in-memory XML DOM tree for the View is implementation
> dependent and shouldn't effect the Widex protocol. If this is
> just a question of wording, will the following work for you?
> 
>   In an implementation where the Widex Server maintains
>   an explicit XML DOM for the View, changes made by the
>   Widex Server to this View result in DOM events, e.g.
>   DOM Mutation events. The Widex Framework in the server
>   (as shown in Figure 1) can listen for these events to
>   generate the corresponding Widex messages. The Widex
>   Framework in the Renderer interprets these messages to
>   reflect the changes to its copy of the XML DOM for the
>   View. Note that the Widex messages are independent of
>   whether the Widex Server has an explicit or a virtual
>   View, that is, an in-memory XML DOM tree, as this is
>   an implementation dependent design choice.

I think I got it. I see there are three ways for the server to maintain the
view:

1. the server maintains an in-memory copy of the XML DOM representing the view
on the renderer side.

2. the server could use some more efficient data structure, e.g. a UI tree or
graph to represent the view on the renderer side.

3. the server could represent the view as a string or binary blob. That's the
case for HTML page-based applications today. But the drawback is the WO.Update
messages will always contain full page updates, not incremental updates.

Do you call #1 explicit view and #2 and #3 virtual view? For me, I'd call all
three cases virtual view, since the physical view (the rendering) is only at the
renderer side and the server only keeps the data model that represents the view.
So I'd refer to #1 as something like "explicit DOM" rather than "explicit view".

Regards,

Jin
________________________________________
Jin Yu
OpenXUP.org


_______________________________________________
Widex mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/widex