Previously, there was some benefit to splitting leoGui.leo, leoPy.leo and leoPlugins.leo. The split reduced load times. But now Leo's caching makes loading .leo files very fast. That being so, there would be significant advantages to combining all of Leo's source files, maybe even scripts.leo, into a single file, call it leo.leo. This merge would eliminate switching between files, and more importantly, make searches automatically apply to all of Leo's sources.
It would be foolish, however, to merge either unitTest.leo or test.leo into leo.leo. We want these files to be separate so that loading them gives the latest code. Anyone have any objection to such a scheme? Edward P.S. leo.leo itself would be small, as leoPy.leo is at present, because all the data are held in external files. 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.
