On Aug 31, 8:27 am, "Edward K. Ream" <[email protected]> wrote:

> As I was thinking about this issue, it occurred to me that a
> significant improvement can be made in Leo's startup logic.  

Done in the trunk at rev 3301.  Here is the checkin log:

QQQQQ
Important improvements to the startup logic:

- Created g.app.guiArgName to hold gui requested in --gui option.
- Revised and corrected scanOptions.
- scanOptions and g.app.createDefaultGui now allow 'null' and 'curses'
gui.
- g.app.createDefaultGui takes more care to handle special cases.
- All g.app.createXGui methods do trial imports before calling gui-
creation plugins.
- run() now takes more care with gui, and ensures the gui has been
created *before* loading plugins.
- The dialog that gets the Leo ID calls g.app.createDefaultGui.
- The error messages for g.UiTypeException are much less intrusive.

All expected unit tests pass.
QQQQQ

I have run many hand tests with both tk and qt gui's
(deleting .leoID.txt, for example).  The new code is, I think, simpler
and more general than the old.  However, the possibility of new
problems exists.  Please report any such problems immediately.

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.

Reply via email to