On Wed, Apr 5, 2017 at 8:48 AM, Phil <[email protected]> wrote: 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 is a third approach, used in leo-editor itself. Use a separate .leo file for parts of the project: LeoDocs.leo, leoPyRef.leo, scripts.leo, unittest.leo, etc.
That said, I typically use a separate .leo file for a project. It's rare you need more than one .leo file, but there will be no big problems if you do. 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.
