Re: [Dynapi-Dev] Redrawing widget with new data

[Richard E. <emb...@co...>]

Richard Bennett wrote:

> Hi,
>
> >Is there any tutorial code,
> > examples, or
> > existing sites
> Practically all the resources are mentioned in the FAQ:
> http://www.dynamic-core.net/core/files/faq.dynapi2.html
>
> You can work with loadpanels, to load content, passing values, without
> refreshing the page.

I looked at the code and tried the loadpanel example. It works fine with the
supplied
(simple) HTML pages but the loadpanel example has some rules as to what can
be loaded; for instance, having it load one of the other example pages - some
can be
loaded while others can not. I do not know if a good test for the loadpanel
is for it to
be able to load other dynapi example pages.

Anyway, I am just beginning and I was unclear in my request. As an example,
your
server has a database with your friends names as the key and the associated
data is
your friend's one or more email addresses, telephone numbers, etc. My dynapi
webpage
has a entry field for entering the friend's name and a list widget with will
contain the
associated data. Upon entering the friend's name (and clicking the submit
button),
a do-put request is sent to the server and the server returns a string that
contains a
the list of data ("home email:fr...@fo...|work email:Mr...@ba...|home
phone:
132-2343") which is parsed by the javascript and the list widget is updated
with the new
data. (I would return the data in XML if all browsers had a builtin XML
parser and the
javascript had access to it).

So is this possible (the requesting and receiving of data - not an html page)
and
does anyone have any example javascipt? thanks.

> >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?
> See above.

During the evolution of tcl tk, the tcl widget collection, it started with
base/leaf-node
widgets. Then multiple efforts started to create
meta-widgets/container-widgets.
These included layout objects or builting layout rules. Manipulating a
meta-widget
transparently manipulated its component widgets (moving, resize, attribute
setting, etc).
After a couple of the tcltk meta-widget frameworks were under creation, the
lessons
learned allowed for the creation of a single tcltk metawidget collection (it
might have
been that one collection just got more users and displaced all others). In
addition,
changes were made to the base widget set, the node widgets, allowing for
their use
in the metawigets (such as a method getParentWidget()).

Is such a container widget collection and layout engines being planned for
the dynapi widgets?

thanks

>
> Richard Bennett
>
> ma...@ri...
> www.richardinfo.com
> (Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
>