On Tue, Jul 8, 2008 at 7:29 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote: > > > On Tue, Jul 8, 2008 at 6:17 AM, Kent Tenney <[EMAIL PROTECTED]> wrote: > >> I'm missing something ... who would be the audience for the shadow files? >> My impression has been that they are private to Leo. > > The audience is anyone who wants to share files without sentinels.
This is probably a semantic issue. I understand that the .leo tree holds files _with_ sentinels, which Leo uses to build the outline. To me this means that if those who want to share files without sentinels are not interested in shadow files, only in public. Maybe a useful analogy is that the shadow files are for 'styling', they determine the presentation of the data held in the public files. > > True, shadow files are private. That is, they exist only in the Leo-shadow > folder and they would typically not be part of the repository. But the > *public* files, the files without sentinels, could be shared in a > repository. The point is that Leo can update the private files from changes > made to public files, so that changes to the repository will "magically" > cause changes to the Leo outline. > > Perhaps an example will make this clearer. Suppose, as is indeed the case, > that I would like to study the pypy project. > http://codespeak.net/pypy/dist/pypy/doc/home.html > > This is a major project, with lots of files. Clearly, I don't want to try > to convince the pypy folk to change all their files. Here is what I am > likely to do: > > 1. First, I'll create @auto for all the files of the pypy project in which > I have an interest. An already-existing script will help me do this. See > test.leo: > > Startup-->Scripts-->create-at-auto-nodes > > 2. Next, I'll convert @auto nodes to @shadow nodes (details a bit fuzzy, > but let's ignore them for now). When I save the outline, the original files > get written as before. In addition, the private files containing Leo > sentinels will be saved to the private Leo-shadow directory. > > 3. When I reopen the Leo file, the outline structure will come from the > private files. However, if any of the *public* files have changed (by the > pypy folk), those changes will be incorporated into the Leo outline, and > when I save the Leo outline again the changes will be written back to the > private files. > > Thus, I can use Leo to read and write pypy files, but the pypy folk will > never see Leo sentinels in "their" files. I can use the pypy repository and > the pypy people will not know that I am using Leo. > > Edward > > P.S. In the usage case just described we would *not* want to add headline > comments to the public files because that would be change the pypy sources > too much. > > 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 -~----------~----~----~----~------~----~------~--~---
