Hey: Thanks for considering this.
My intended use for this was as follows: I have a huge outline with many mixed things, and I use them all, because all are somewhat related. So part of my work in Leo is to find one, then find the related ones for fixing that one, updating that one, then go to the next one. The problem is (most of the time), while finding the related ones, I will find some extra thing that requires edition. If I add that new extra thing as a new bookmark, the list of bookmarks will be soon too long, so currently I have no other option than forgetting about that and coming to that later. But If I could nest that as a bookmark of a new bookmark, forget about it now, and go fix that later, that would be sweet. Also, this allows you to do much more complex work with nodes, since, you can be working with difficultly related nodes, then go to lunch, and when you are back you have them bookmarked in a "logical" order which allows you to quickly gain back the train of thought and keep editing right away. If you dont have this, the only option is to keep cloning, or remembering where was each related node to the issue. And some times, cloning is not the way to go, because: - Some problems are not solvave in one session - Most of the times, I work in several different problems at once. - So, If you keep cloning everything around, there would be no way back to the original state when you finish fixing the 4-7 different problems you have been working in the last few days. But with nested bookmarks, you could quickly nest the concept you just forged out of a new pack of nodes-relations, then work on that for a few days, then delete the bookmark when done. And the good thign is you would be able to work in several different complex concept at the same time, since no massive cloning invovled, and switching from one another is just picking another of your "main bookmarks". So the solution of nested bookmarks would be dynamic enough to allow us to do this, but again quick enough to add it without much problem to revert back (cloning or chapters). That is why I would base the gui doing some thing similar to: - By default, all main bookmarks load (only children of the bookmarks node). When you want to work with nested ones, you (eg) shift+control+click it. You will be working with that node as main, and its children will be shown. - When a bookmark has children, it is denoted by ending with (+), so the user knows it. - You can have a "(-)" button on the left, which travels up to parent of current position, which can be stored through the gnx. This, although simple GUI, would allow an incredible dynamism on node edition, since you would be able to group them as concepts and navigate through them very quickly. Again, perhaphs this is only my view of things and this wouldnt be as useful for everyone, so just sharing the idea in case you find it useful too =) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
