Not as complex as it appears.
We need to spend enough time with the tools provided here, before we start feeling comfortable.
Most of the tools open in their respective popup browser window. The tools have many functionalities, and since these are web-based, unlike a typical desktop application, you can perform several operations parallely by opening different links in different browser windows/tabs.
Parallel operation - be careful!
Since we can launch different tools in different popup windows, we can do many tasks parallely. While the possibility of doing several things in parallel can increase productivity, it can also cause problems.
Two common problems that one faces are the risk of losing unsaved work, and overwriting a new version of the document with an older version. These problems mainly happen in a cluttered desktop with many browser windows/tabs opened up.
If we close a browser window that has newly edited unsaved content, we lose our recent editing work, and if we click on Save/Submit button on a browser window/tab that has an older version of the document that has already been updated in some other browser window/tab (which might not be open at this moment), we end up overwriting the document with old version.
To reduce such risks, we have incorporated auto-cleanup (by closing itself) of orphaned windows. Let us understand this auto-cleanup carefully.
Windows hierarchy and dependency.
0space tools icons are present on every open 0space content page. If one opens 0sEd from one of them, and opens 0sNotes from some other 0space window/tab, we have two instances of parent windows (with 0space content pages in them), and two instances of child windows (one for 0sEd, another for 0sNotes). If one closes one or both of the parent windows with 0space pages, or navigates away from the current page, the child-windows will become orphaned.
When a child windows finds that it is orphaned, it closes itself in 3 seconds (implicit navigating away of child-windows)! This means that the current work in the child-windows also are lost automatically, if a user navigates away from the current page.
Do not ignore system messages.
We have provided enough alerts for user when one tries to navigate away from a page. [It is important that we read the alert messages before clicking on OK.] The alert messages a user gets will also indicate if there is any implicit navigating away case. So one has enough chance to save the current work correctly.
With this as background, let us now start looking at some of the available workflows, and start experimenting.
