Yes, this is a common pattern. The slider has a number of events you can
handle. These can be specified as options when you call the .slider(options)
init. You supply a callback function as the value of the event-named
property and it's executed at the appropriate time. In your example
$("#mySlider").slider({
change: function(event, ui) {
// this is executed each time the value of the slider changes
// could include a .ajax call to send the new value to the server
}
});
For more, see
http://docs.jquery.com/UI/Slider/slider (click the options tab, go to the
bottom of the list for events)
- Richard
On Tue, Feb 3, 2009 at 9:45 PM, Mel T. <[email protected]> wrote:
>
> Hi,
>
> I am new to building JavaScript / AJAX applications. I am building a
> web app that has a page made up of a lot of controls such as jquery's
> slider.
>
> I do not want this page to have an "apply" button.
>
> Therefore, after sliding a slider for example, I would like to make an
> AJAX call that changes my model on the server side, without requiring
> that the user explicitely applies this action.
>
> Is building something like this a common pattern ?
>
> My guess is that yes, this is quite common, to the point where this
> question is obviously from a clueless newbie.
>
> --
> Mel T.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery UI" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jquery-ui?hl=en
-~----------~----~----~----~------~----~------~--~---
