Re: [Dynapi-Help] 3x api and text boxes - semi solved

[Leif W <war...@us...>]

It sounds like a cool application of the DynAPI.  Would you consider
releasing a very simplified, generalized version for example purposes or a
demo, for the DynAPI examples pages?  I think it would be a good addition.

In any case, best of luck, and if someone else who reads this thread has
some more input on the topic than I've given, please share it.

Leif

----- Original Message ----- 
From: <ml...@id...>
To: <dyn...@li...>
Sent: Thursday, September 04, 2003 4:24 PM
Subject: Re: [Dynapi-Help] 3x api and text boxes - semi solved


>
>
> My app is an editor for a complex dataset.
>
> Basically it presents a list box of choices, on selection of choices,
> a set of listboxes and user inputs pop into existance to the right,
> for the various sub choices that are available given that selection
>
> Since the available options are driven by the choices the user makes,
> the select and text boxes come and go as the user interacts with the
> system.
>
> This is driven out of an xml file which defines the choice space.
> The forms are never submitted as such, instead the data is read out
> and the main display is updated. That display gets submitted back to
> the host.
>
> I will have to make the application modal.
>
>
> > ----- Original Message ----- 
> > From: <ml...@id...>
> > To: <dyn...@li...>
> > Sent: Thursday, September 04, 2003 3:16 PM
> > Subject: Re: [Dynapi-Help] 3x api and text boxes - semi solved
> >
> >
> > >
> > > I did some more checking.
> > >
> > > 1) all of the text boxes had the same element name
> > > 2) using getElm() on the HTMLTextBox, returned the same object [as by
> > >    '=='] on all of the textbox's with the same name.
> > >
> > > 3) changing the names to be relatively unique, solved the problem.
> > >
> > > My list boxes just happened to have different element names.
> > >
> > > --
> > >
> > > I think this is a problem, because it becomes hard to make 'widgets'
> > > that can be replicated on the page, if the element names have to be
> > > unique.
> >
> > I think this is the same for most browsers and HTML in general.  How is
a
> > browser supposed to distinguish one element from another if they all
have
> > the same name?  It can't.  When the form is submitted to a server, how
is
> > the server side supposed to know about mutiple values assigned to the
same
> > name?  It can't.  Generally speaking, but you can do it in Perl -
sometimes.
> > Likewise with the DynAPI, if all DynLayers had the same name, then the
API
> > wouldn't work.  That's why the API automagically assigns unique names to
> > each DynLayer.  Something like this would have to be implemented if you
want
> > to have automatic generation of unique names for form elements, or just
keep
> > track of them manually in the code.  It's difficult to understand the
> > problem without an example, though.
> >
> > Leif
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Dynapi-Help mailing list
> > Dyn...@li...
> > https://lists.sourceforge.net/lists/listinfo/dynapi-help
> >
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help
>
>