are you using RJS templates?
using RJS you can update as much as you want on a page.
# action to call when element dropped into div2
def drag_item
# do your work here
render :update do |page|
page.replace_html "div2", :partial => ...
page.replace_html "div1", :partial => ...
end
end
On 4/3/06, da plutes <pluto1@gmail.com> wrote:>
> This is of course disallowed, which I discovered only after nearly
> completing my spanking new ajaxified UI. What is the motivation behind
> this, and what is the best workaround?
>
> This UI does a scriptaculous drag-and-drop of items from a first div
> (div1) over to a second div (div2), which triggers the contents of div2
> to be updated to reflect the drop. No prob, thus far. But then the
> contents of div1 must be re-sorted via controller (action1) based on
> what has been dropped into div2. THe re-sort of div1 must be done
> server-side. I currently update div2 via render :partial on the tail-end
> of the action (action2) that is triggered by the drop, and then re-sort
> div1 via a submit (form_remote_tag) to trigger action1 which does the
> sort and refreshes div1.
>
> It would be nice to be able to either update both div1 and div2 from one
> of the actions, or allow action2 to update div2 via render :partial and
> then redirect_to action1, but that is not allowed, so what is the best
> recourse to having to use a submit?
>
> Thanks - plutes
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060403/3753bddc/attachment.html