- This topic has 4 replies, 3 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
Your Struts Flow Editor is incredible, however it could use some enhancements:
1. Being able to break the diagram into multiple diagrams would be
awesome. Or even better, nesting of diagrams would be awesome.2. I can’t get it to let move the end points on the associations between nodes. I switched to manual routing mode but that still won’t let me
pick the where the endpoint goes on a node.1. Being able to break the diagram into multiple diagrams would be
awesome. Or even better, nesting of diagrams would be awesome.What would be the meaning of breaking a diagram into multiple diagrams? Modules? Simply organizational? Multiple applications?
2. I can’t get it to let move the end points on the associations between nodes. I switched to manual routing mode but that still won’t let me
pick the where the endpoint goes on a node.Do you mean the snap-to points on the nodes where the links connect to, or do you mean moving a link from A to B instead to A to C?
@support-rkalla wrote:
1. Being able to break the diagram into multiple diagrams would be
awesome. Or even better, nesting of diagrams would be awesome.What would be the meaning of breaking a diagram into multiple diagrams? Modules? Simply organizational? Multiple applications?
Simply organizational is quite a valid reason. Just think on being able to make a small page flow diagram for each use case for the documentation…
Regards,
Robert
Robert,
I agree that could be helpful… can you describe the type of functionality you would like…. kind of a “focus” feature, where you could highlight a subset of the nodes and links and hit “focus” and it would hide all all nodes and links and let you work on just that subgraph? Or would you want this separation user defineable/persistent? i.e., select 4 or 5 nodes, click say “Make Group” and name it “User Login” or somethign like that?Hmmm this could be a good idea…
I guess it should simply be something like the following:
You should be able to create and delete layout diagrams (except the primary layout file which cannot be deleted, and contains all the nodes in struts-config, meaning you cannot take away nodes from the primary layout).
You should probably assign some name to the file so that the files can be distinguished from each other.
You should be able to (e.g.) dragging nodes from the outline into a new flow diagram, the same way as you do it with dragging classes from the tree to a class diagram in Rational Rose, also deleting classes manually from the diagram (only from the diagram!).
It should have the same layout features as the full flow, so arbitrarily moving around nodes, routing connections on arbitrary pathes. The storage format should not even be very different from the current one, a new file with the layout data alone would be able to store everything, I guess.
Whenever you make changes to one layout file which is reflected in a change to the struts-config.xml itself, you should make the user confirm this (except for making them in the struts-config.xml editor), and the change should be reflected in all other diagrams, if appropriate, so that all files are consistent. If for any reason you are not able to do all changes necessary for an operation (for instance some files are read-only and cannot be obtained with write permission from the source control), it is to be undone.
Also some notation should be invented for modules (different struts-configs) on the flow view. E.g. when a forward points to or comes from, or an input comes from (is that possible?) another struts-config module, the other module should be displayed on the flow view with an other icon type (package icon, for instance). That way some subsystem diagram can also be put together.
Of course this is just braindump, feel free to make modifications to this…
Regards,
Robert
