Since this thread has opened the discussion of leo UI design, I would like to add a few comments.
Each leo user will have very different needs, so to make the most people happy, flexibility is required. I would like to be able to switch between different views of the leo outline, its contents and external files with ease. The traditional view is fine for a general overview and quick editing, but is not an ideal use of screen real estate for serious edits involving many nodes and files. A tab view could be useful where each tab would be a 'dirty' node with easy hiding and viewing of the tree as a split view. Changing a node would add it to the dirty tab list. Changing of external files would add them to the external file list. Clicking a node in the tree view would add it as a dirty node tab. A side by side diff view would also be useful. This could be used when external files are changed, or in integrated use with a repository. This is not really needed since other tools cover this, but might be useful if it does not bloat leo in any way. A full screen view of the code, perhaps in a separate window would be very useful since I now am fully addicted to multiple desktops that allow quick switching between different windows. This could be done with dockable tabs from the tab view where the user could select a tab and create another window with its contents. The next suggestion is yet another echo of a recurring theme on this forum. It would be nice to have a view of the entire contents of an external file, or perhaps a subset of some of the nodes that are used to represent this external file. If the above suggestion is possible it opens up the possibility for a revolution in leo usage.... Since a large number of developers are addicted to one of the two big editors, they are in turn addicted to the UI features of these editors. One must admit that these two big editors are optimal for the task of editing many types of text. Since the scope and purpose of leo is beyond the pure editing of text, the usefulness of leo could be brought to a wider audience and the text editing capabilities within a leo environment could be expanded if one could open an expanded view of the text in an external editor via the open_with plugin or something smarter. Of course the ideal solution would be to open this expanded text view of the entire external file or subset of this file into a pure leo editing window that directly mirrors the editing capabilities of one of these editors, but this would take an large coding effort. It would be possible to make this goal a longer term leo plugin project to replace the open_with solution. I think this is enough for now and thanks for the hard work Edward. Cheers, David Schryer http://sysbio.ioc.ee On Apr 23, 12:04 pm, "Ville M. Vainio" <[email protected]> wrote: > On Wed, Apr 22, 2009 at 9:24 PM, Edward K. Ream <[email protected]> wrote: > > > As I just mentioned in another thread, Leo nodes could be a substitute > > for qt designer. This might allow people to design Leo's gui in an > > @settings tree(!) > > I think it's better to just use qt designer, as opposed to duplicating > the effort. It's really a rather good tool for this purpose. > > Sadly, the qt_main.ui has grown quite complex, so it's a bit > nontrivial to edit without breaking everything. > > -- > Ville M. Vainiohttp://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
