Thodoris Greasidis

Related to #248

The items option should target direct child elements of the ui-sortable directive. The default value is '> *'. Likewise you should use a css selector that starts with '>', otherwise...

> Likewise you should use a css selector that starts with '>' I was meaning something like this: `items: "> .category:not(.not-sortable)"`

Didn't realized that this was enough for your use case. I'm glad you found a solution!

I don't think this will fix it. This branch is updated by ui-publisher after releasing each tag. I think that we should edit [publish.js bowerData field](https://github.com/angular-ui/ui-sortable/blob/master/publish.js#L38).

Sorry, no progress yet :disappointed: Merging v0.14.x into master is my first priority at the moment. At the moment you can use the above code hint.

Please don't create a hure diff. Try not moving methods until the initial refactor gets reviewed. Keep in mind that targeting the absolute min number of code lines can hurt...

Have seen the [connected lists canceling example](http://codepen.io/thgreasi/pen/IdvFc) in README? It uses some of the extra properties that UI-Sortable attaches to `ui.item.sortable` to prevent the second list to have more than...

I just added [Connected Lists Without Duplicates](http://codepen.io/thgreasi/pen/uKfyt) example to README and I think it is very close to your use case. I would like to add an extra property ot...

> That example requires using DOM attributes + jQuery in my controller That was a bit hacky back then. I think the [new example](http://codepen.io/thgreasi/pen/uKfyt) I composed does not require DOM...