third-party widgets (like jQueryUI) and Ember are two separate worlds. As i pointed out, one must handle the events and control the underlying data in an Ember Way. So, yes, nothing changes about Ember, but Ember cannot automatically know about the widget you are using and therefor not about its DOM manipulation(s).
Are you looking for some automation process on this?
For the sake of time i left out the “data binding” part in the jsbin example. Please see this blog post for one option on how to deal with it:
This applies to
sortable but will most likely be different from ‘widget’ to ‘widget’! The benefit of using a component would be, that you use it in other projects too, as well as share it with the community.
This is also the point, where one must be careful, _when_to update the model as change in the model layer triggers re-rendering! E.g. when you proxy the changes of the sortable on the
sort event you will get into trouble as this triggers the mentioned re-rendering and you will loose the currently sorted element. Also you want to always take a look on how your data looks rendered as DOM structure. This might influence the workings of your widget.
As you can see, there is not really a straight forward answer to all widget (let’s just take this for jQuery UI); so a jsbin with your approach on using jsTree would help to help.