Persistance of Views when moving between tabs

[kritinsai]

Views in OrientDB studio are reset every-time tabs are switched. For example, if i move from the functions to the browse tab and back to the functions tab the function display would be the first function in the list instead of the one i was working on. Similarly, The commands i type in browse tab disappear every-time i switch out of the tab.

This behavior is really annoying if the commands are long. It is also dangerous as, if the last function i was working on is not saved after it is created, it vanishes.

[wolf4ood]

@kritinsai

this is a mayor enhancement. Those are not tabs but menu. And when you switch you change context (route change). The page is like reloaded and the state of the previously page is lost. I will keep this open as enhancement but it will not be done soon.

[santo-it]

Hi,

From a usability point of view I agree this is important

I'd say that the "Browse" view is "partially" persistent, in the sense that if a command has been executed and has been added into the history, the "command" frame persists even after a menu change, because the history is reloaded. The query in the text area, however, is cleared when the menu is changed

The Graph Editor is not persistent

@maggiolo00 perhaps the work on this can be chunked and different chunks implemented at different times?

Some ideas / possible questions:

• In the "Browse" tab, is it possible to implement a history for the sql text area? (something additional to the execution history) and add an entry in the text-area history every time the query is executed or the menu is changed (if the text area is not empty). On page load (similar to what happens right now for the execution history) also the sql history would be read, and last entry (if not empty) loaded into the text area - at least until Studio is closed (so that next time Studio starts the text area is clean)
• for the "Functions Management" view I am wondering if perhaps a check can be done on menu change and, in case, alert users that their changes will be lost if not saved? this may be a possible workaround to not loose any change
• for the "Graph Editor", again, from a usability point of view, it would be very useful to have an sql history. I'd also keep a history of the last visualized graph (or, better, graph panels) - at least until Studio is closed - this would allow users to change menu and not loose their last graph, and, when starting Studio again start with a "clean" Graph Editor (to not compromise performances too much) . See also Issue #293, related to having multiple panels in the Graph Editor

Thanks,

[santo-it]

Hi,

Recently we made some improvements in 2.2. so that if a query has been executed in the graph editor, when you change tab and then go back to the graph editor the query and the graph are displayed again

The other improvements are still to be implemented

https://github.com/orientechnologies/orientdb/issues/4974 and https://github.com/orientechnologies/orientdb/issues/5808 appear as duplicate of this issue

Thanks for your patience,

[santo-it]

Linked with https://github.com/orientechnologies/orientdb/issues/5425