Rev 4796 contains a long-overdue housecleaning.
As noted below, all unit tests pass locally, which imo is a strong
test that the reorg is benign. But there are no firm guarantees--
please report any problems immediately.
Running unit tests externally is a good indicator of the health of the
leoBridge module, as well as an independent check of some of Leo's
most important base classes. At present, about 80 tests fail when run
externally. I suspect there are only a few real problems to be
solved. I'll be working on them today.
Here is the checkin log::
QQQQQ
An important reorg: Removed the following unused methods from all Leo
classes::
bind c.bind also removed.
configure
cget
event_generate g.app.gui.event_generate does exist.
getWidth
indexIsVisible Also removed for leoEditCommands: scrollHelper and
measure.
mark_set
onChar Fortunately, never used anywhere
pack Used only in Tk code
scrollLines
set_width Removed do-nothing calls in Leo's core.
tag_add Removed do-nothing calls in qt colorizer.
tag_bind Removed do-nothing calls in qt colorizer.
tag_delete Removed do-nothing calls in qt colorizer.
tag_names
tag_ranges
tag_remove
update
update_idletasks
xyToPythonIndex
yview
All unit tests pass when executed locally from unitTest.leo.
Many tests fail when executed externally: make those tests pass will
be a double-check on this checkin, and will also make the leoBridge
much more functional.
QQQQQ
Edward
P.S. At present, ### marks disabled code. I'll be removing such code
once all tests pass when run externally.
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.
