Re: AjaxSlider
Re: AjaxSlider
- Subject: Re: AjaxSlider
- From: Chuck Hill <email@hidden>
- Date: Wed, 15 Oct 2008 11:20:45 -0700
Hi David,
On Oct 15, 2008, at 6:09 AM, David Ress wrote:
I am working a WO application for the US Air Force, and finally have
been able to upgrade the server from 10.3 to 10.4. This opened up
the
opportunities to use Java 1.5 as well as adapting the Wonder
frameworks.
Lots of big and good changes there.
No kidding. The 5 databases within the WOApp I am responsible for is
both interesting
and frustrating.
Is there an example which shows the AjaxSlider sending its value
back to the
component available for study? Otherwise, any hints as to how I
can send
the value back to the component for further processing?
The AjaxGridNavBar does this. Here is an example set of bindings:
Does that help?
Not really. It confused me quite a bit, largely due to my lack of
javascript
experience and being completely new to Wonder. I guess I need to
start with the
basics, but pointers are always welcomed.
My first pointer: JavaScript can make your head hurt, no two ways
about it.
I should have mentioned that the AjaxSlider will be one of 4
controls in a
component - the other 3 (WOCheckBox x2 and a WOPopupButton) are
submitted with a
WOForm and I need the value of the AjaxSlider to be passed back when
the WOForm
is submitted. Having the AjaxSlider update the page is not what my
end user
is after in this case.
Is this even possible - submitting an AjaxSlider's value via a
WOForm? If so, is
there an example available for study.
It is not a form element so it can't be used like a form element. The
easy way would be to just let it update a local instance variable in
the page. When the form is submitted, the method it is submitted to
can copy the value from this instance variable to its final
destination. If the form is cancelled, no action is needed. The
other alternative is to use JavaScript to copy the value from the
slider into a hidden field (WOHiddenField) in the form whenever the
slider is moved. This hidden field will the get submitted like any
other form element.
In perusing the AjaxExamples.woa, it seems that Ajax allows local
updates in a
component whereas a WOForm forces an entire refresh. That will be
very useful in
the other sections of the WOApp I am developing.
It can provide a nicer user experience, but it almost always ends up
being more work. Sometimes just a little, sometimes a lot!
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
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