I've tried Qt, and I always revert back to Tk.  Qt just doesn't have
all the features I depend on--using it on a daily basis (e.g. moving
nodes).

On Aug 29, 4:38 am, VR <[email protected]> wrote:
> Hi Edward,
>
> I am a  mostly happy user of the Tk-based version of Leo.
>
> On 28 Aug., 15:43, "Edward K. Ream" <[email protected]> wrote:
>
> > 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.
>
> I do not follow this argument. - Using Tk/ Tkinter is one component
> that the user does not have to worry about, since it is automatically
> there. - I'm talking about Windows here, but I assume that when
> you talk about installer you talk about the Windows installer and
> not for example the debian package that Ville provides.
>
> > It also complicates Leo's core, but that's mostly my concern.
>
> Is independance from a particular GUI provider, still a requirement
> for Leo core ? - If yes, how do you plan to verify it ?
>
> > 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.
>
> I think it really should be analyzed/ decided in the context of the
> requirements for and the approach taken with the Installer:
>
> * How do you plan to go forward with any of the other components
>   that are required beside Python and the GUI (Qt or Tk) ?
>
>   * docutils
>   * sphinx
>   * aspell
>
> Personally I would favor a 'cautious' approach. - By that I mean,
> don't try to 'improve' everything in 4.8. - There is a 4.9, and even
> a 4.10 is possible before releasing the magical Leo 5 ;-)
>
> My 2 cents ...
>
> Kind regards,
>
> Viktor

-- 
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