on 6/7/01 1:22 PM, "Peter Lynch" <[EMAIL PROTECTED]> wrote:
>
>
> Ok, maybe like this...
>
> <form action="Foo">
> <input type="hidden" name="action"
> value="/Foo/Foo.doFoo">
> <input type="submit" name="submitbutton"
> value="Submit Foo">
> </form>
>
> <form action="Foo">
> <input type="hidden" name="action"
> value="/Foo/Foo.doFooBar">
> <input type="submit" name="submitbutton"
> value="Submit Foo bar">
> </form>
>
> Or with javascript or query strings things get even
> easier. Am I missing something?
Yes. Sometimes having two separate <form> tags creates spaces in the UI
layout.
> All of this presumes there is only to be one action to
> be performed at a time. Are you saying you wanted to
> be able to perform two actions in the same class?
Not at all. Just within the same <form> tag.
> Not trying to be picky, just trying to understand the
> approach a little better.
Regardless, you have the ability to define your own ActionEvent class and do
things however you want. Just like the rest of Turbine, the implementation
there is just the default and can be easily overridden. That is part of the
power and coolness of Turbine. You are not locked into one way of doing
things.
-jon
--
"Open source is not available to commercial companies."
-Steve Balmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
