I opened a Leo file with Tk yesterday as part of unit testing.  I was
shocked at how bad it looked.

Furthermore, I'm beginning to think of Tk as actively harmful, like
@root and like code-mode in the rst3 command.

Indeed, Tk complicates life considerably for newbies: it complicates
the installer, it complicates the installion docs, and it complicates
the initial prompt for a user id.

It also complicates Leo's core, but that's mostly my concern.
However, some of that bleeds out into the user experience.  In
particular, I *really* dislike  UiTypeException.  The very last thing
I want a newbie to see is a bunch of red tracebacks in the log pane
the first time they open Leo!

For all these reasons I think it is time to retire Tk.  To do this
will require porting the most important Tk plugins to Qt.  It will
also require drag and drop in the Leo's tree pane, something that at
present I have no idea how to do.  In any event, imo it would be best
to retire Tk completely.

Your comments, Amigos.

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