on 7/12/2000 7:58 AM, "Dan Diephouse" <[EMAIL PROTECTED]> wrote:
> As a turbine developer I have yearned for something to ease development
> further (Turbine already eases development tremendously..) AND to make
> everything look nice and pretty. ECS is alright and it lets me generate
> dynamic tables and HTML and all that good stuff...But I feel that is not
> enough. After seeing the link to Hammock (www.oop.com) it sparked some
> ideas.
Good, since Hammock isn't OSS, it won't be used around here anytime soon.
:-)
> Please keep in mind two things about myself while you read this
> :) 1 - I have not used WebMacro yet, that would probably solve lots of
> the complexitys of javascript and servlets.... 2 - I do not know
> javascript very well, or it's capabilities. Anyway, here are some
> scenarios...
Try out WM.
> 1) I have a drop down list. The has several options (ie: contacts)
> listed from about 200-300. These contacts (or options if we stick to
> the abstract) are their most recently used/most frequently used ones.
> Then there will also be an option in the list for Search. If the user
> clicks on search it should open up a new 400x400 window with a search
> form. Then the contact is passed back to original form and set. (is it
> possible to add an option to a drop down list dynamically? Otherwise it
> could be set in a hidden field) This same scenario could be played out
> with an Input box and search button also. Now how would one do this in
> a servlet?
>
> combo = new ComboBox(Array of options);
> action = new OpenAction(window);
> action.closeAction(combo.addOption(Search Results));
>
> Now this is truly horrible above. For some reason I can't flesh my idea
> out, but I 've only been thinking about this for an hour....I need some
> way to have the set the links for the second screen (the search results)
> so that it will exit and return the value to original screen. There are
> many problems I'm sure....
Start of with implementing it as regular pages. Then add in the javascript
to create a new window. This stuff isn't rocket science and really doesn't
have much to do with Turbine itself.
> 2) Form Validator: When a user clicks submit this checks to verify that
> all the fields are filled. There could be a FormValidator utility class
> and you could do:
>
> FormValidator.addCheck(InputBox1);
> FormValidator.addCheck(InputBox2);
> FormValidator.addCheck(SelectBox, Check that it isn't option #1);
> FormValidator.finalAction(goto page blah);
> Submit.onClick(FormValidator.Execute);
>
> This could be very useful. I have at least 20-30 places that this could
> be used.
Right, we already have this type of system with
ParameterParser.setProperties(). You can stick your bean object into there
to do the validation. There are also examples of the way that I'm doing in
in Scarab...
<http://scarab.tigris.org/source/browse/scarab/src/java/org/tigris/scarab/om
/project/Project.java?rev=1.4&content-type=text/x-cvsweb-markup>
look at the doPopulate() method.
> 3) Form Tabulator: When you have a spreadsheet of input fields it is
> nice to have Javascript automatically add them up for you....
>
> FormTab.add(field1, field2, MULTIPLY, dest);
> each input would be set to FormTab.execute() after it lost focus or
> something....
>
> SOOOO.....This whole system would need
This is beyond the scope of this list.
> A dynamic JavaScript Generator
huh? Simply use WM to do this.
> A new windowing framework (One that is swing-like)
gag. This has already proven to not work well. SPFC is a dead project.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
