Remove the sortable before the Ajax call, then reinitialize the
sortable after the content has loaded.
On May 28, 8:44 pm, jGalzic <[EMAIL PROTECTED]> wrote:
> I am using drag & drop with Sortable.create between 2 groups on a page
> but I'm running into a problem with the elements not dragging an
Haha, have you ever tried doing that puzzle? It does exactly what i
mentioned. It's fine horizontally but as soon as you order vertically
the other pieces, other than the one you're dragging move. Might have
to develop my own solution using the native drag and dropunless
anyones got any bright
On Mon, May 19, 2008 at 5:08 PM, elduderino
<[EMAIL PROTECTED]> wrote:
> I'm working with sortables. I've set constraint to be flase as i want
> my list to be sortable in both directions.
Is that code in your sortable.js file? I don't see the constraint
option being passed in. Try it like this:
Why not? There is a scripty demo that does something similar.
http://github.com/madrobby/scriptaculous/wikis/puzzle-demo
TAG
On May 20, 2008, at 2:15 PM, Diodeus wrote:
>
> I don't think Sortable was designed with floats and a grid in mind (at
> least not your application of it).
>
> On May
I don't think Sortable was designed with floats and a grid in mind (at
least not your application of it).
On May 19, 6:08 pm, elduderino <[EMAIL PROTECTED]> wrote:
> hi,
>
> This is kind of mainly a scriptacolous q so if ther is a more
> appropriate place to ask this question then let me know.
>
I think you would use Draggable's observers here:
function saveDraggableOrder(){
// your code here
}
var draggableObserver = {
element:null,
onStart:function(eventName, draggable, event){
},
onDrag:function(eventName, draggable, event){
But if I put it in just one and then reorder the list that does not have the
callback function the function is not called.
On 7/25/07, Diodeus <[EMAIL PROTECTED]> wrote:
>
>
> I would put it in just one, but have it call a function that collects
> and updates the information from both lists when i
I would put it in just one, but have it call a function that collects
and updates the information from both lists when it runs.
On Jul 25, 2:17 am, Kim <[EMAIL PROTECTED]> wrote:
> If you have two sortables that you can drag and drop to and you want
> to call an action that will save the new orde
Is your HTML object properly structured? As in are you using ?
Sortable will automatically try to collect tags by default to set
up as the draggable objects.
On Jul 2, 7:50 pm, Chippy <[EMAIL PROTECTED]> wrote:
> Sorry for all the replys..
> It occurs to me that all the bug reports and such t
Sorry for all the replys..
It occurs to me that all the bug reports and such that I saw were for
problems with second and third level, whereas I'm having trouble even
on the first level...
On Jul 2, 4:45 pm, Chippy <[EMAIL PROTECTED]> wrote:
> I did a bunch of searching and found that people have
I did a bunch of searching and found that people have been having
similar problems with the version I'm using (beta 3). I found two bug
reports on this topic (and related patches for both), but neither of
the patches work. I even found a comment on the wiki (http://
mir.aculo.us/2007/5/25/script
Sure did. Only options I have set: "tree: true, dropOnEmpty: true"
On Jul 2, 2:28 pm, dasboe <[EMAIL PROTECTED]> wrote:
> did you set dropOnEmpty for sortable options to true?
>
> http://wiki.script.aculo.us/scriptaculous/show/Sortable.create
--~--~-~--~~~---~--~---
did you set dropOnEmpty for sortable options to true?
http://wiki.script.aculo.us/scriptaculous/show/Sortable.create
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this
Frederic,
I too have encountered this problem. My solution to this was to set
overflow to 'visible'. Although you'll lose whatever behavior you wanted
when overflow was set to 'scroll' or 'auto'.
HTH,
George
On 3/29/07, Frédéric JECKER <[EMAIL PROTECTED]> wrote:
>
> Moin list,
>
> I'm playin
Yes, I can see why it is needed in the code, however it just surprised
me that it works if I use dragdrop.js from pre-1.6.x.
It is a serious limitation in large nested trees where you don't want to
have to know what the lowest 'branch' is before you begin. For example,
I have one extremely lar
Peter Robertson a écrit :
> If you create the sortable from most to least nested then it works (i.e.
You always need to do that when nesting draggables/sortables; this issue
has surfaced several times in this list.
This is fairly normal, as to implement d&d we need to convert a page
position in
Ahh.. I ran into this problem myself once but didn't have time to
pursue it, and in that case neither the tree option nor the recreate
sortables bubbling upwards option would work.. This is quite an
annoying limitation, maybe I'll try to fix it if I ever need sortables
really badly...
Colin
This is the only way, at least according to the Wiki. You can also make
one big sortable out of the whole thing, using the tree parameter to
make a nested list sortable en masse.
Walter
On Mar 27, 2007, at 7:31 PM, Peter Robertson wrote:
> If you create the sortable from most to least nested
It's not really a Prototype/Scriptaculous question.
IE has some CSS rendering problems. There are workarounds--setting
position:relative in the divs or their parents may fix it for you.
A quick Google search turned up these:
http://www.mail-archive.com/wsg@webstandardsgroup.org/msg26789.html
It sounds like you have a set of *draggables* (things that can be
dragged and dropped) not a set of droppables (places where draggables
may be dropped).
I would suggest using a sortable observer, to which you can attach a
callback to check whether the item dropped on your sortable is one of
True, but I don't have two sortables, I only have a set of droppables
and a sortable, and when I add a droppable to a sortable I actually
prompt the user for some input and then manually add an element to the
sortable and then re-create the sortable. This is why I need to be able
to figure out whe
IIRC, Sortable recognizes the options for Droppable, so 'accept' should
be enough (this is used to allow cross-dragging between sortables, for
instance).
Check this page for inspiration:
http://wiki.script.aculo.us/scriptaculous/page/print/SortableListsDemo
--
Christophe Porteneuve a.k.a. TD
Hi,
the results are correct, because Sortable.serialize does not retrun
the content of the sortable items, but the identifier part of your
ids. And this part is empty, because this is the part after the
underscore. Another problem is that your code is not valid HTML,
because the ids must be uniqu
23 matches
Mail list logo
