Comments on: Open Source Flex Project: flexwires

By: RA

RA — Wed, 29 Sep 2010 09:27:24 +0000

Thanks a ton for the quick turnaround. I’ll look at this example. Hopefully should also solve the problem of wires remaining on the screen when i change the viewstack. Thanks again!

By: Josh Tynjala

Josh Tynjala — Wed, 29 Sep 2010 07:38:49 +0000

RA, by default, there's a display object on the PopUpManager where all the wires appear. In flexwires, there's a class called WireSurface. Create one of these somewhere under your WireJacks. Then, pass it to the wireManager property of each of the WireJacks. All the wires should then appear on the WireSurface instead of on the PopUpManager. The IntroductionToJacks example in flexwires uses WireSurfaces because wires must disappear when the Accordion page changes. That might be a good place to start.

By: RA

RA — Wed, 29 Sep 2010 06:07:26 +0000

Hey Josh, Thanks a lot for this project! I’m doing a basic diagramming application as a college project and would like to have multiple connections from an output jack. You had mentioned that we need to add a wire surface to accomplish this. I went through the source but could not understand what you implied. Also JB, have you worked this out?

By: udana

udana — Sat, 18 Sep 2010 16:46:29 +0000

am developing an application to drow ER diagrams and conver those ER diagrams to Object relational database schema is there any flex class to draw an ER diagram or any kind of diagrams ?? udanajeewantha@gmail.com

By: Josh Tynjala

Josh Tynjala — Tue, 06 Jul 2010 01:30:44 +0000

As an FYI for anyone reading the comments, the issues described above, regarding Adobe AIR, are now fixed. You can download version 1.1.0 or newer over at GitHub.

By: Josh Tynjala

Josh Tynjala — Wed, 11 Nov 2009 21:35:07 +0000

JB, an output should be able to connect to several different inputs by default. However, you should ensure that the wires are placed on a WireSurface under the jacks (instead of the default surface that gets placed on the PopUpManager) so that wires appear below the jacks and don’t block additional connections.

A chain should be possible too. However, you probably don’t want to use InputWireJack and OutputWireJack. I wouldn’t know for sure without testing, but you might be able to use their base class, WireJack, without any modifications. It doesn’t have default restrictions on how it can be connected to specific types of jacks.

There is no forum or mailing list set up for flexwires. You can post a comment here, or use my contact form, if you prefer. Either way, I’ll be notified by email.

By: JB

JB — Wed, 11 Nov 2009 21:22:27 +0000

First and foremost, great work and thanks for the generosity to release this code open source. We are planning to use it as a base for a node-link chaining to create data-based 3d visualization scenes. We have a few questions…for example, most of the demos show an InputJack or an Output Jack. Wondering what the best approach is for a situation where a node is to serve as both (e.g. a logic chain) and in cases where an output may go to several nodes. Is there a forum to pose such questions?

Thanks

By: Josh Tynjala

Josh Tynjala — Mon, 16 Mar 2009 00:14:02 +0000

I've also added a new clickToDrag static property to the WireJack class. This allows an alternate drag interaction where you click on one jack (including releasing the mouse button), and then the wire will follow the mouse until you click again. If the target of the second click is another jack, then the connection is made. Otherwise, the wire disappears when you click anywhere just as if you released the mouse button during a normal drag. Personally, I found that it felt a little more natural for my finger to do two simple clicks to connect a pair of jacks rather than mouseDown->drag->mouseUp. That said, not everyone may agree, so the standard drag behavior is still the default.

WireJack.clickToDrag = true;

As you can see above, it's easy to setup. Since it is a static property, you can just drop that directly in an MXML Script block (no function needed).

By: Josh Tynjala

Josh Tynjala — Sun, 15 Mar 2009 22:34:42 +0000

I’ve committed some changes to the repository on Google Code that fix the runtime error when trying to use flexwires in AIR. However, it appears that the AIR version of the framework has an IDragManager implementation that behaves very, very differently in several ways than the default implementation. While the error no longer happens, the drag image appears to be removed from the display list almost immediately after being created. Not sure why.

By: oak

oak — Sun, 28 Dec 2008 02:17:34 +0000

I tried Nick’s AIR hack but with no luck. Has any progress been made on an AIR patch?