Welcome to yEd Q&A!
Here you can ask questions and receive answers from other members of the community and yEd developers. And you can tell us your most wanted feature requests.


Desktop shortcut directly to a node

0 votes

' '  The yEd Software License Agreement explicitly forbids the usage of yEd in any kind of automated process (see section 1, "License Conditions"), which covers most forms of commandline usage aside from simply starting yEd from commandline. So, no, you cannot and may not do so.  ' '

The answer - quoted from the related question - above seems to imply, that being able to open a specific graph file in yEd and automatically focusing on a specific node in the graph - directly from the command line - would be an acceptable use case. After all, this would in no way alter the state of the file itself, but is all about presentation, and makes possible no form of automation chain building without user interaction. Is this currently supported, or planned for the future?

To be a bit more specific, what I'm hoping to do is create an OS desktop shortcut that is capable of not only pointing to a specific complex graph file, but a particular node within that file. It seems like a highly useful usecase scenario for many purposes, not to mention what it would imply for yEd graphs interlinking between each other using the "go to URL" feature.

related to an answer for: Can I use yEd as a commandline-tool?
in Help by (170 points)

1 Answer

0 votes
Currently, the feature you suggested is neither supported nor planned.

Feel free to post a feature request for this.

That said, I am curious about how you would like to specify that one specific node you want yEd to focus on? Moreover, I am also curious about those use cases that might benefit from this feature.
by [yWorks] (160k points)
I imagine it would work something like this:

java -jar yed.jar mygraphfile.graphml --focus aNodeName (or other type of node identifier)

This would simply open mygraphfile.graphml in yEd and immediately home in on the node with "aNodeName" in (or as) the label, zooming if necessary for a clear view of the node.

As for use cases, as I pointed out, such a feature would allow different yEd graph files to link to each other on a node-by-node basis, simply by entering a command with the above syntax into the "URL" field, using an OS-native shortcut as a proxy, if necessary. This might be helpful when, for instance:

- A user is working with a complex graph-structured data set, but for reasons of convenience or performance would prefer to structure this data into several smaller files rather than pool everything into a single huge one. This feature would allow them to do so, while still allowing for arbitrary interconnectedness between different nodes in the involved files.
- A complex data set contains a finite number of different types of nodes. As above, putting everything into a single file might make things like layout and navigation, needlessly complicated. In this case, the user might instead consider using a separate file for each type of node, but would not be prevented from creating relationships between nodes of different types.
- The pattern might work best for complex graphs with a strongly componentized structure, with many clusters of tightly interconnected nodes with few edges interconnecting the clusters. Putting each cluster in a separate file and then interconnecting them via this or similar mechanism might dramatically help ease working with such data sets. It would also allow better version control of data sets that are built or edited by a collaborative effort, seeing as it would reduce the risk of edit conflicts arising, by separating the data into several smaller files.

For all intents and purposes, such a "URL" nodelink would serve just like any other kind of edge, except for its connecting to a node in a different file, which a purely technical distinction, not a logical structural one. I know of certain other graph or mind map editors that explicitly support such node interlinking between files. SimpleMind for Android comes to mind. yEd would already support the pattern, if only this kind of commandline call was possible.
Legal Disclosure | Privacy Policy