On Sat, Nov 1, 2008 at 5:02 AM, schryer <[EMAIL PROTECTED]> wrote: > The configuration is indeed the most troublesome aspect of Leo. Now > that qt is well on its way to being usable, I can imagine a nice > graphical front end (automatically generated) that would allow users > to choose and test their keyboard bindings, add, remove and test the > plugins, adjust the qt layout and display options (spacings borders, > colours, fonts ect..), and various other options related to leo's > commands like find options.
Heh. At one point Leo did have the "typical" gui-based front end for various settings. I removed it after it had been a stable part of Leo for about a year. I am not going to put it back. Leo has a huge number of options because Leo's environment is richer than flat editors, and also because adding a new option can be done in a matter of seconds without asking for anyone's permission. This is not possible with a "pretty" front end. Furthermore, leoSettings.leo allows you, the user, to arrange settings using clones, an especially valuable feature that can't be done with any reasonable amount of work if a gui interface is used. > With regards to gui design, I suspect with the move to qt it may be > easy to make the layout of Leo quite flexible and dynamic. Yes, it will happen. > Specifically, it would be nice to separate out the various components > of the leo interface into different windows for use with multiple > desktops, or quick switching to save screen real estate. I suppose a separate find panel might be possible, but this idea does not thrill me. Leo's tabbed log pane can do a lot. Of course, you can always open multiple .leo files and put them in various places. > On another topic, it would be nice to display files in multiple > ways: For instance, it is often convenient to work with your > routines separated into different nodes, but sometimes it is helpful > to view and edit the entire derived file (with line numbers). This is a frequently requested feature. It will happen. > To > facilitate this I can imagine a special type of flattened clone that > displays the contents of the external file (derived file) exactly as > it would appear in another editor. The asymmetry in the clone can be > circumvented by turning the (or one of the) flattened clone(s) back > into its original form if the last nodal clone is deleted. I wouldn't used the term 'clone' in this regard, but yes, something like this is going to happen. In fact, there are various plugins that presently do various parts of this. > > Related to this idea is the facility to print out sections of code > with the various display options available in many editors. Leo has > the chance to really shine in this area as we can view the code in > many many ways, but currently I find myself using other editors to > print out sections of my external files. Perhaps the new qt front end > will facilitate the interface to a nice printing dialog. Tk did not have adequate support for print. I hope qt is better. If so, simple scripts should suffice to print outlines in whatever format you like. Also, Leo has good enough integration with other editors, including Open Office, that using such editors to print stuff shouldn't be too odious. One way to summarize our dialog is that Leo has indeed become a huge beast. One must study Leo's documentation carefully to understand what it can do. Or ask on this forum :-) Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
