You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the ArtifactTree, using the Java ID of the nodes does not provide usefull information about the node. The Node Interface could define a mehthod "getTreeLabel", which by deafault (abstract base class) returns the Java ID, but the plugin could override. Probably the method just actually go in the ArtifactData so the plugins can provide custom implementations (plugins dont extend nodes).
The text was updated successfully, but these errors were encountered:
This probably also applies to the ArtifactGraph. Maybe a shorter version of the tree label ca be used for the graph (we want to avoid long names to reduce clutter). Perhaps for the ArtifactGraph, depends on the capabilites of the drawing tool, change the shape/border color?
(On a side note the ArtifactGraph needs a lagend)
It's a good idea for this method to be implemented in ArtifactData so that plugins can override the behaviour.
The name, however, should just be getLabel imo, since getTreeLabel would suggest the method is used in a GUI of which a plugin should not be aware of.
I will open a separate issue for an ArtifactGraph-Legend.
In the ArtifactTree, using the Java ID of the nodes does not provide usefull information about the node. The Node Interface could define a mehthod "getTreeLabel", which by deafault (abstract base class) returns the Java ID, but the plugin could override. Probably the method just actually go in the ArtifactData so the plugins can provide custom implementations (plugins dont extend nodes).
The text was updated successfully, but these errors were encountered: