On Thu, Feb 26, 2009 at 12:41 PM, Kent Tenney <[email protected]> wrote:
> > As I understand it, sentinels are required to support a certain set of > features, > features which are unique to Leo - clones, <<sections>> ... Not exactly. They are needed to do anything other than @auto: they allow the user to put structure of any kind in @thin and @file files. Without sentinels, external files would truly *be* "derived" files: there would be no way to update a .leo outlines from an external file: all "primary" data would perforce be in the .leo file. True, clones, section references and directives are supported by sentinels, but the main thing is that sentinels *create* permanent structure residing in external files, not .leo files. To put it another way, the challenge is to put structure in the .leo file, while putting content in the external files. This seems impossible, in general. The closest general solution seems to be @shadow. Eliminating public sentinels would seem to require @shadow. I'm uncomfortable with that, but maybe it's just discomfort. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
