No answer to this topic. I search through the archives and I see
repeats of the same question by other posters, also without much
response. The issue sits in plain sight at the bottom of the relevant
page in the (broken) scriptaculous wiki with no answer for 2 years.
In my opinion scriptaculous' drag-n-drop functionality is *broken* if
it is only able to hit test the candidate target divs in the same
order as they were registered, without the ability to specify the
reverse order or to specify bubbling and/or capture options at the
time of registering.
Does everyone just skip scriptaculous' drag-n-drop if they're dealing
with nested droppables, and work directly in plain javascript/DOM
methods instead? Or use another library?
Prototype does not have its own drag-n-drop functions though it does
help out a lot in event registration in general. I don't want to have
to start over in JQuery or even Ext to get this working in my project.
I'm just surprised that with scriptaculous included in Rails (and also
in Pylons, the similar Python framework) no one has a fix for this in
common. The answers I've gotten on IRC are basically "screw
scriptaculous, get a different library, or learn to produce what you
want in plain javascript." I'm willing to do that, just don't want to
miss any obvious short cut.
On Mar 22, 7:02 pm, Eric Ongerth <[EMAIL PROTECTED]> wrote:
> I am having trouble with scriptaculous' drag & drop here. I have a div
> that's droppable, and two divs contained within that first div, each
> of which are also droppable. The containing (outer) div seems to grab
> all drops. Even though I defined the inner ones as "greedy" which is
> supposed to mean that draggables don't propagate through.
>
> I read elsewhere that when anesteddiv and its containing div are
> both droppable, the one that was made droppable *earliest* actually
> grabs any drop, regardless of the "greedy" option. Is this true? If
> so, that would seem to contradict the intent and purpose of that
> option.
>
> In my situation, I really need the inner div to receive anything
> dropped on it. I do not want the drop to propagate to the outer div.
> But I cannot make the inner div droppable before the outer one,
> because the inner div does not even exist until the user drops
> something on the outer div. Only after that happens is the inner div
> created and made droppable.
>
> So is there no way to make this inner div droppable in the way I wish
> with scriptaculous? I have read one or two people asking this same
> question, getting no reply (or just a suggestion to create theirdroppablesin
> reverse order) and apparently giving up.
>
> I thought the 'greedy' option would do what I'm trying to do, but
> apparently it does not. I even triedDroppables.remove('outer_div')
> after the inner div is made droppable, but that failed. The outer div
> remained droppable and continued to steal every drop that occurs over
> the inner div location.
>
> I would be grateful for any insight and help on this.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
