Nw application development

> Note that this is incremental change, and not 
> invasive at all 
> unless you decide to write a pure netWindows app (like Christian's).

... Yes,  I begin to notice that my approach is quite different from what I
understand the developers of NW themselves focus on...

There seem to be two different directions one can go with NW:

1) The page-centered approach of richt and diverse websites, which uses
mainly inline-constructors and loads pages into windows as needed. This
approach also support the idea of "degradable widgets" for browsers that
cannot display nw widgets correctly.

2) The data-centered approach, which loads the complete application and a
lot of the data at startup, and then works from there. This approach uses
mainly programmatic constructors and relies on structured, mostly uniform
data queried and sent by the server. In this setting, "degradability" is of
course impossible to achieve.

This is what I am trying to do... But the problem might be that I need to do
almost everything programmatically, from populating tables with data to
constructing forms. I don't know how well nw supports this approach at this
point. 

I know that I want to stick with this approach because I don't want to have
to load each bibliographic reference from the server when I want to do
something with it - I want to have them in memory on the browser, and only
have server interaction whenever something gets changed.... That's my idea
of a real web application - to avoid roundtrips at all costs.... ( Another
reason is that I really like javascript programming now as much as I begin
to dislike PHP-style).

Christian


_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org