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
The plugin needs a way to visually show the user the model they're working with.
This could be implemented in one of two ways:
Generate the graph whenever the user edits the Umple model (Like in UmpleOnline, but somewhat taxing on resources)
Generate on compile or with the press of a "generate" button (more involved but less frequent)
The way I see it, the choice will most likely depend on whether or not the generation of the graphs will be done server-side (favoring automatic generation) or client-side (favoring manual generation, really needed for low-end setups). A third choice could be a setting that allows the user to pick and choose how they want it done (client vs server, and auto vs manual), but there is still the problem of what the plugin uses by default.
Generation frequency aside, the method of generation should also be determined, but that will most likely just borrow from UmpleOnline.
The text was updated successfully, but these errors were encountered:
UmpleOnline does most of the computation on the server side. An ajax call to the same API can be done. In Umpleonline it can be toggled between manual redraw and auto-redraw. Auto-redraw is done after 3s of no typing, but a check is done client side to ensure that the changes are not just spaces or comments ... in the latter case the diagram is unchanged. I suggest starting with manual redraw. And I suggest generating the graphviz class diagram and graphviz state diagram.
The plugin needs a way to visually show the user the model they're working with.
This could be implemented in one of two ways:
The way I see it, the choice will most likely depend on whether or not the generation of the graphs will be done server-side (favoring automatic generation) or client-side (favoring manual generation, really needed for low-end setups). A third choice could be a setting that allows the user to pick and choose how they want it done (client vs server, and auto vs manual), but there is still the problem of what the plugin uses by default.
Generation frequency aside, the method of generation should also be determined, but that will most likely just borrow from UmpleOnline.
The text was updated successfully, but these errors were encountered: