Hi All, I am about to start a new project using Leo, and am considering how I want to organize it with respect to other projects. I have used two different approaches, as follows:
1. Use a single Leo file and put all projects in it. Each project is rooted in a single root node, using @path to locate it in the filesystem. 2. Use a separate Leo file for each project. Each Leo file is located in the filesystem along with its project. There are pros and cons to each approach. The single-Leo-file approach offers the following: *Pros:* - Only one Leo file - nothing gets misplaced or forgotten - Global search through all my code history - giving a better chance of finding something to re-use - Bugfixes in cloned reused code propagate to all projects - no need to manually patch them in - I know that code is always to be found in this single Leo file - no need to go looking in the filesystem for something I remember doing "way back when" *Cons:* - Only one Leo file - becomes large and sluggish to load - Changes to cloned reused code propagate to all projects, even when I don't want it to - Changes to filesystem breaks @path - Something I did "way back when" can eventually fall out of my mental radar range, even if it is useful The two approaches are roughly equivalent, though I tend to favor the single-Leo-file method. I am wondering how others manage this. Thanks, Phil -- 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.
