add support for 'proxy' endpoint when dragging

[GoogleCodeExporter]

from this discussion on the groups:

https://groups.google.com/forum/?fromgroups#!topic/jsplumb/HtdSANpiDuk

It would be good to support the notion of a "proxy" endpoint, for jsPlumb to 
use when dragging a connection (new or existing).  At the moment, when you drag 
a connection from some endpoint, jsPlumb uses a clone of that endpoint.  If the 
endpoint is large this can make for an unappealing user experience.

of course there are other reasons why you might want to use this notion of a 
drag proxy.  i mention that one because it was the catalyst for opening this 
issue.

possible syntax :

jsPlumb.addEndpoint("el", {
  isSource:true,
  endpoint:["Dot",{radius:40}],
  paintStyle:{fillStyle:"blue"},
  proxy:{
    endpoint:["Dot",{radius:5}],
    paintStyle:{fillStyle:"red"}
  }
});

It would seem also to be a good idea to add the notion of a 'DragProxy' to the 
jsPlumb defaults while we're at it.

Original issue reported on code.google.com by simon.po...@gmail.com on 25 Apr 2012 at 3:27

[GoogleCodeExporter]

i actually don't think this is going to make it into 1.3.9. there doesn't seem 
to be an easy way to inject this behaviour into jQuery's draggable stuff.  

it is increasingly looking like jsPlumb should handle dragging of connections 
independently of any underlying library.

Original comment by simon.po...@gmail.com on 22 May 2012 at 1:55

• Removed labels: 1.3.9

[GoogleCodeExporter]

Original comment by simon.po...@gmail.com on 23 May 2012 at 10:06

• Changed state: New

[GoogleCodeExporter]

moved to github

https://github.com/sporritt/jsPlumb/issues/22

Original comment by simon.po...@gmail.com on 30 Apr 2013 at 11:32

[GoogleCodeExporter]

Issues have all moved to Github.  Google code is no longer in use for jsPlumb.

Original comment by simon.po...@gmail.com on 10 May 2013 at 11:37

• Changed state: WontFix