Re: Organizer nodes and leoGlobals.py

2014-07-11 Thread Edward K. Ream
On Thursday, July 10, 2014 9:21:37 AM UTC-5, Edward K. Ream wrote: I plan to leave the functions in leoGlobals.py just as they are, except for reorgs. Done at the latest rev. The new organization is an important improvement--it should be much easier to find functions. A new Miscellaneous

Re: Organizer nodes and leoGlobals.py

2014-07-11 Thread 'Terry Brown' via leo-editor
On Fri, 11 Jul 2014 09:23:12 -0700 (PDT) Edward K. Ream edream...@gmail.com wrote: On Thursday, July 10, 2014 9:21:37 AM UTC-5, Edward K. Ream wrote: I plan to leave the functions in leoGlobals.py just as they are, except for reorgs. Done at the latest rev. The new organization is an

Re: Organizer nodes and leoGlobals.py

2014-07-11 Thread Edward K. Ream
On Fri, Jul 11, 2014 at 11:41 AM, 'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote: I propose that we convert p.get_UNL, vc.find_absolute_unl_node and vc.find_position_for_relative_unl. What's the status of those methods? Unchanged, and in the same places. I am thinking of a

Organizer nodes and leoGlobals.py

2014-07-10 Thread Edward K. Ream
This follows up a recent discussion of organizer nodes. Kent made the remark that they might encourage overly-large classes (or modules). For several years I have considered breaking leoGlobals.py into several classes, say g.scan, g.path, g.ws, etc. Ironically, Kent's remark has had the