Re: WOPopupButton and DirectAction
Re: WOPopupButton and DirectAction
- Subject: Re: WOPopupButton and DirectAction
- From: Chuck Hill <email@hidden>
- Date: Mon, 28 Mar 2005 19:55:58 -0800
Oh never mind number one. Too much burrowing though log files today,
I'm starting to hallucinate.
On Mar 28, 2005, at 7:48 PM, Chuck Hill wrote:
As long as you are not nesting the forms, that is both a valid thing
to do and probably the easiest solution. Nested forms are not valid
HTML though there are likely some browsers that will try and make
sense of it. If that changes your UI too much, then there are some
other options to consider:
1. The image submit button can use its own URL. Have the form bound
to a direct action that just regenerates the calendar and all the
other buttons bound to their own direct action.
2. Use JavaScript to set an hidden form value which indicates the
action to be taken.
Chuck
On Mar 28, 2005, at 7:40 PM, Baiss Eric Magnusson wrote:
Restatement of the problem: creating a DirectAction app out of a
session based app by removing all the action bindings on the page.
I removed the <?curRegionName> binding of the WOPopupButton and added
the binding
name "regionPopupIndex";
because that's what comes thru, it's the index of the popup, not the
selection.
This works for me, in a limited sense, as I have the <list> in the
application, but I don't think it would work in most situations.
But I get the binding for <regionPopupIndex> even when the form's
action is triggered from the <Login> button.
So I need to know which widget is triggering the form's action, so
when I come from the Login button I will go to the Login page and
when I come from an <onChange> of the Region popup I will just
re-generate the calendar for that region, and there will be other
widgets which will trigger a form's actions.
I suppose I could put multiple form's on the page, does that seem
like a valid solution?
It helps to think about the HTML that you need generated. A lot of
the component action RR loop is not used in direct actions.
I think you should take off the ?curRegionName binding and add
name = "curRegionName";
Chuck
----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden