Forums

In my work I am heavily using events and drag/drop. So far things are relatively simple during mockup and demo data dev work.

I will have a bunch of items on a page that can be dragged around and connected together in various manners

As I progress though I will be running into possible scenarios where I will have the following #'s on a page:

~50-100 click/mousedown element checks implemented via Delegate method using class selection
~10-15 mousedown element checks implemented via Delegate method using class selection
~30-75 drag/drop elements also including an almost equivalent number of available drop zones for each element.
{each element will have drag:start,drag:drag,drag:drop checks}

~5-10 timers triggering various background tasks and io requests

Main question is between work Y! team members have encountered internally or folks in community are they any performance implications people have encountered and reached some limits on a smooth UX?

Trying to use Delegate style event handling where possible instead of instatiating whole event objects. Right now my main concern is over proper methodology around the drop elements since I have a large number of permutations for possible drag/drop groups.

Thanks Dav,

I am playing around with a couple different methodologies I have been working on as I have been flushing out my own architecture. So far the first delegate stuff I have done seems to work great so I will try this new stuff out and let you know how it goes.

Ok Dav, moving things along, new delegate stuff is pretty sweet,

With regards to the 1st level children or all children being queried, still seem to get the behavior of just 1st level children. I see your comment "All nodes should be a child of this container", and this:

items = Y.one(self.get(CONT)).all(self.get(NODES));

Two other things I came across which I dont know are bugs are just part of the changes,

One is with regular DD, you are able to use this.get('node') inside an drag::* function to get the drag node object. It seems that has changed to this.get('currentNode');

Other one is the last piece of the puzzle I am tinkering with is Proxy. I am able to .plug it, no complaints/errors but no proxy behavior happens. I assume since its in an early state it hasnt been implemented or just something funky going on.., or I am just using it wrong:


var dragDelegate = new Y.DD.Delegate({
cont:'#'+compElemID,
nodes:'.available'}
).plug(Y.Plugin.DDProxy, {
borderStyle: false,
moveOnEnd: false
});