QQQ let me skip ahead to what might be called the "real" Aha, namely that we can imagine three (or is it four?) ways of using bzr.
0. Don't use bzr at all. There is no cooperation. 1. A fully Leonine environment, such as leo-editor. All committers to the repository use Leo. 2. A fully non-Leonine environment. At most one committer uses Leo. 3. A mixed Leonine environment. More than one, but not all, committers use Leo. QQQ As I see it, the primary task at present is to verify that @file! will work in all four environments. Until this is completely verified, all other issues, while exciting in their own right, could be called "premature optimizations". Clearly, cases 0 and 2 pose no problems. The bzr repository will use so-called "public" files, that is, files without Leo sentinels. Indeed, it would not be possible, looking at the bzr repository, to determine that anyone is using Leo. OTOH, for cases 1 and 3 it *will* be possible to infer that various people are using Leo. Some or all of the source files will contain Leo sentinels (or their equivalent, if Leo's sentinel cashing scheme is used). The real purpose of this thread is to ask the following picky questions: Question 1: Exactly what will the bzr repository contain? and Question 2: Exactly how will public and private files be put in sync? At present, I don't have a clear answer for either question. Yes, I know we have discussed these questions a bit, but I don't think we have really thought things through yet. BTW, I had a "little" Aha re cases 1 and 3, the two collaborative cases. It seems to me that we should focus on the *hard* case, case 3, rather than the easy case, case 1. Indeed, leo-editor may remain the only project for which case 1 applies. Rather than "cheating" by using case 1 for leo-editor, I think leo- editor should "eat its own dog food" and use the case 3 approach. That is, both the public and private files should be committed to the bzr repository for leo-editor. If leo-editor can't live with this approach, it would be foolish to expect anyone else to do so. The Aha is both a challenge and a simplification. It's a challenge because it forces us to confront the hard issues. It's a simplification because we no longer have to worry much about case 1. This is just the start of the verification process. But I thought I would emphasize the significant work that remains. 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 -~----------~----~----~----~------~----~------~--~---
