Yes and no. At issue is that when I implemented the behavior I didn't
provide the ability to specify all the available options of sortable:

https://github.com/anutron/more-behaviors/blob/master/Source/Drag/Behavior.Sortable.js#L42

But it's easy to add. Just add handle: api.getAs(String, 'handle') and
you're done. I can add this if you want to open an issue (so you'll get
notified when I do it) or you can send me a pull request.

On Thu, Oct 18, 2012 at 7:35 PM, Philip Thompson <philthath...@gmail.com>wrote:

> Next question. Is there a way to specify more than the Behavior.Sortable
> options? For example, I want to supply Sortables' handle option. I tried
>
> data-sortable-options="{'handle':'.selector'}"
>
> but that didn't give me what I wanted. I know I can create a custom
> behavior, but didn't want to reinvent the wheel.
>
> Thanks in advance,
> ~Philip
>
>
> On Thu, Oct 11, 2012 at 10:10 PM, Aaron Newton <anut...@gmail.com> wrote:
>
>> Behavior filters have no order dependency, which means that the "user"
>> can put them on the element in any order, for example:
>>
>> <form data-behavior="FormRequest FormValidator">
>>
>> In this example, the form request instance will be set up and then the
>> validator instance. But it could easily have been the other way around. As
>> such, the filters can't be written to expect any sort of order of
>> operations. This is where Filter Plugins come into play. Plugins DO get an
>> order of operation promise. That is, the filter they modify is ALWAYS
>> applied before they are. So when you need two things to work together, the
>> plugins are the glue.
>>
>>
>> On Thu, Oct 11, 2012 at 9:25 AM, Philip Thompson 
>> <philthath...@gmail.com>wrote:
>>
>>> Excellent! I figured there was a way, but hadn't found it yet. I
>>> definitely already thought about making a behavior for those, but wasn't
>>> sure how nicely they'd play together. I'll take a stab and see what I can
>>> come up with.
>>>
>>> Thanks,
>>> ~Philip
>>>
>>>
>>>
>>> On Wed, Oct 10, 2012 at 9:46 PM, Aaron Newton <anut...@gmail.com> wrote:
>>>
>>>> elementWithBehaviorSortable.getBehaviorResult('Behavior.Sortable')
>>>>
>>>>
>>>> http://dev.clientcide.com/Clientcide%203.1.0/viewdoc/lib/behavior/Docs/Behavior.md#Element:getBehaviorResult
>>>>
>>>> You might also consider a Behavior Plugin to bind the two behaviors
>>>> together.
>>>>
>>>>
>>>> On Wed, Oct 10, 2012 at 7:20 PM, Philip Thompson <
>>>> philthath...@gmail.com> wrote:
>>>>
>>>>> Hi. I am using Behavior.Sortable and it works as desired. I am also
>>>>> using Drag.Move to insert move and insert new list items into my Sortables
>>>>> lists. The new items attach to the list, but I am unable to attach the
>>>>> sortable events on that new list item because I do not have access to the
>>>>> Sortables instance. Is there a way to access the Sortables instance from 
>>>>> my
>>>>> drag's onDrop method?
>>>>>
>>>>> Thanks in advance,
>>>>> ~Philip
>>>>>
>>>>
>>>>
>>>
>>
>

Reply via email to