From: Richard E. <emb...@co...> - 2001-02-07 22:33:15
|
We have a reasonably complex webapp written in Flash by contractors (no documentation). We let everyone go (no more $$) and I am now re-writing it with html and js. I happened upon Dynapi yesterday (my first day of looking around the web for dhtml info) and it looks like a good starting point (and close to a stable release). Now what I want is not to have to load a new page from the server each time the user changes options (makes selections, etc), rather I want the widget(s) that display the data simply to be updated and re-drawn. The user would make some new selection, the js would communicate with the server requesting new data, the js would receive the new data and update the appropriate widgets. Is there any tutorial code, examples, or existing sites using Dynapi that have this characteristic? and can I see the code. Next, if I have a multi-page webapp, do I have to reload from the server the Dynapi code for each page? Is there lazy-loading in the widgets so that if your new page requires only one new Dynapi javascipt file, then only it is requested from the server? If I create two meta-widgets (widgets made up of more than one base widget) how do such meta-widgets specify which base widgets the depend so that if there is a shared base widget, it only get requested from the server once? (An examle meta-widget might be a viewport and two scrollbars (x and y)). Thanks Richard Emberson Director of Engineering (and only programmer) Contact Networks emb...@co... |