Ciao!
Would anyone care to offer suggestions on the implementation of dynamic
lists of values (LOVs) to be presented on interactive web forms in a
mod_perl/Embperl framework? Their content is to be derived from an
underlying DBMS based on previously filled-in form information, or
perhaps based on a simple pattern entered by the user.
Again, mod_perl/Embperl are my weapons of choice for rendering the
various project pages, and I can/will use a fair share of javascript to
'activate' the UI, I imagine. There is to be NO java, server-side or
otherwise, so I'm looking to make the front-end presented to the user as
usable as I can with the client-side maybe a bit heavier than in a
normal app.
I suppose one could do it via a 'wizard' approach with multiple POST
requests, each with a little more information than the other and used to
drive the next form state. I don't know how usuable this will be
considering the multiple requests potentially needed to navigate through
the information on a form. Guess I'll be finding out, huh?
If you have any thoughts on the subject, I'm listening. Otherwise, I
will keep anyone who is interested apprised of my approach and
solution(s).
Always a pleasure to participate on this list.
Peace.
Would anyone care to offer suggestions on the implementation of dynamic
lists of values (LOVs) to be presented on interactive web forms in a
mod_perl/Embperl framework? Their content is to be derived from an
underlying DBMS based on previously filled-in form information, or
perhaps based on a simple pattern entered by the user.
Again, mod_perl/Embperl are my weapons of choice for rendering the
various project pages, and I can/will use a fair share of javascript to
'activate' the UI, I imagine. There is to be NO java, server-side or
otherwise, so I'm looking to make the front-end presented to the user as
usable as I can with the client-side maybe a bit heavier than in a
normal app.
I suppose one could do it via a 'wizard' approach with multiple POST
requests, each with a little more information than the other and used to
drive the next form state. I don't know how usuable this will be
considering the multiple requests potentially needed to navigate through
the information on a form. Guess I'll be finding out, huh?
If you have any thoughts on the subject, I'm listening. Otherwise, I
will keep anyone who is interested apprised of my approach and
solution(s).
Always a pleasure to participate on this list.
Peace.