Multiple Scopes

[GoogleCodeExporter]

It would be useful to somehow set multiple scopes so that an end point may 
connect to different "kinds" of things.
Or to set the endpoint "type" and configure an array of accepted endpoint types 
to connect with.

Original issue reported on code.google.com by cimt...@gmail.com on 24 Feb 2011 at 8:00

[GoogleCodeExporter]

'scope' is type, really..i just chose that term in the first place because it 
started out as jQuery only and that's what they use in their drag and drop.

would supporting an array of strings for the value of 'scope' get you what you 
need?

Original comment by simon.po...@gmail.com on 24 Feb 2011 at 9:21

[GoogleCodeExporter]

changed to enhancement.

Original comment by simon.po...@gmail.com on 24 Feb 2011 at 10:30

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Yes i think changing it into an array would allow for a wider range of usages, 
specially if combining the possibility of having this array set in the drop and 
drag configuration (which would provide the possibility of having 2 different 
arrays)
Thanks

Original comment by cimt...@gmail.com on 25 Feb 2011 at 2:48

[GoogleCodeExporter]

i'll update every place that uses 'scope' to support arrays of strings, keeping 
the existing support for string for backwards compatibility.  targeting 1.2.6.

Original comment by simon.po...@gmail.com on 26 Feb 2011 at 3:03

• Added labels: 1.2.6

[GoogleCodeExporter]

Original comment by simon.po...@gmail.com on 26 Feb 2011 at 3:04

• Added labels: Milestone-1.2.6

[GoogleCodeExporter]

after refreshing myself on how jsPlumb does the scoping stuff, it has occurred 
to me that this is not actually very easy to achieve, at least not for jQuery, 
because jsPlumb piggy backs on jQuery's scope concept for drag and drop, which 
is limited to a single scope.  the MooTools and YUI scope implementations in 
jsPlumb are both a little hand-rolled and could probably be made to support 
this reasonably easily.  

Original comment by simon.po...@gmail.com on 7 Mar 2011 at 5:07

[GoogleCodeExporter]

descoping this for 1.2.6.

Original comment by simon.po...@gmail.com on 13 May 2011 at 2:17

• Removed labels: Milestone-1.2.6

[GoogleCodeExporter]

i don't think i'll get to this for quite some time.

Original comment by simon.po...@gmail.com on 2 Jun 2011 at 4:10

• Added labels: Milestone-Sometime-In-The-Future
• Removed labels: 1.2.6

[GoogleCodeExporter]

Original comment by simon.po...@gmail.com on 5 Jun 2011 at 10:00

• Added labels: SometimeInTheFuture
• Removed labels: Milestone-Sometime-In-The-Future

[GoogleCodeExporter]

I need Multiple Scopes too.

Original comment by post2...@gmail.com on 17 Jun 2011 at 11:11

[GoogleCodeExporter]

I'm also looking for this functionality.

Original comment by lhfied...@gmail.com on 13 Feb 2012 at 7:16

[GoogleCodeExporter]

the problem still is that jsPlumb piggy-backs jQuery's scope stuff, which does 
not support multiple scopes.  So i'm not likely to get this in to a release 
anytime soon.

Original comment by simon.po...@gmail.com on 14 Feb 2012 at 5:09

[GoogleCodeExporter]

I'm trying to think of ways around this. Basically I'm trying to allow
target endpoints to accept multiple types of source endpoints.

For example, let's say I've got a target endpoint that can handle strings
and integers.  And I have 1 source of type string, and another source of
type integer.

My approach I'm thinking of right now is to put everything in 1 scope, and
then do a check in beforeDrop and abort if the target can't handle the
source type.  But obviously the user won't know they can or can't make the
connection until they try.

Original comment by lhfied...@gmail.com on 15 Feb 2012 at 5:57

[GoogleCodeExporter]

i'd really like to be able to fix this because i see this use case as something 
that would probably be quite common.  your beforeDrop solution would obviously 
work but it's misleading for users and so ultimately not a very cool experience 
for them i guess.

let me take a look in the jQuery source and see what i can see.

Original comment by simon.po...@gmail.com on 15 Feb 2012 at 9:49

[GoogleCodeExporter]

so, there's nothing i can do to influence jquery's scope stuff from outside.

if jsPlumb is to support this then it will have to do it itself. this is not 
entirely unappealing, as it will mean a unified codebase across the three 
library versions, and it also mean i could support another request i had today: 
the ability to prevent endpoints that are full from showing up as if the user 
could drop on them (achieved through the dragActive class).

so i am going to try to do this. for 1.3.9.

Original comment by simon.po...@gmail.com on 31 Mar 2012 at 6:23

[GoogleCodeExporter]

Original comment by simon.po...@gmail.com on 31 Mar 2012 at 6:24

• Added labels: 1.3.9
• Removed labels: SometimeInTheFuture

[GoogleCodeExporter]

Original comment by simon.po...@gmail.com on 23 May 2012 at 11:43

• Removed labels: 1.3.9

[GoogleCodeExporter]

It's been well over a year since I initially suggested the multiple scopes.. 
and it seems this thread (and the project) have evolved quite a bit since last 
I took a look at it. I initially mentioned the multiple scopes because in a 
project we are using WireIt, which provides this functionality, and wanted to 
try doing a similar thing in jsplumb. Recently I've had some spare time and 
wanted to attempt this again.
Regarding multiple scopes I found this post that might be useful 
http://stackoverflow.com/questions/11066497/jquery-ui-drag-droppable-with-multip
le-scopes
I am going to attempt to add this in a local demo i'm doing and see how it 
works out, as it seems (at least according to the docs) that it still hasn't 
been fully tackled :)

Original comment by cimt...@gmail.com on 19 Jul 2012 at 2:34

[GoogleCodeExporter]

Ignore my previous post. After a while of digging around in the code, I think 
that it's possible to simulate what I was looking for using the beforeDrop 
callback.

Original comment by cimt...@gmail.com on 19 Jul 2012 at 5:28

[GoogleCodeExporter]

thanks for the update. this is still one of those things i might do, but it's 
interesting to note that a similar effect can be achieved with beforeDrop.

Original comment by simon.po...@gmail.com on 24 Jul 2012 at 10:54

[GoogleCodeExporter]

moved to github

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

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

[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