Improving any large code base is always possible. Here are the areas that seem most important to me right now.
1. Make it clear what classes, methods and functions are "official", that is, can be counted on always to exist. At present, many helper methods could be said to pollute various name spaces. Defining them more locally would be useful. Imo, documentation is *not* the answer. 2. Use @g.command to define all commands. As I review the code, this seems unlikely to be helpful. The various @cmd decorators quasi-magically define "self" to be the correct class. I rather doubt that removing these classes will be useful, or worth the effort. 3. Define the g.c property. This should be useful. It's really just a synonym for g.app.log.c, with appropriate guards. Alas, this doesn't make #2 above any easier to do. All comments welcome. The discussions this year have been useful. Some have introduced creative uncertainty or tension where I had been too complacent. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
