On Nov 11, 8:16 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> In short, Leo remains stable enough to use for routine development,
> and just a bit more works should make all unit tests pass.
All unit tests pass, both with and without the qt plugin enabled. The
code is at rev 1486 of the qt-gui branch.
Interestingly, the qt tree redraw is significantly slower than the
tkinter tree code; the qt unit tests take about 90 sec. longer than
the tk unit tests. So much for native widgets :-) Of course, a lot
of special-purpose work went into making leoTkinterTree.py fast, but
it does cast some doubt on the inherent superiority of C code...
I plan to merge qt branch into the trunk in the next day or so. The
changes to Leo's core are minor and benign, and I expect that all
future work can easily be done in qtGui.py.
Edward
P.S. There is a new version of Qt out. Supposedly it contains the
fixes required to use QScintilla with Leo's core. I haven't installed
the new version yet, so I don't know for sure.
EKR
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
