On Mar 14, 8:57 am, "Edward K. Ream" <[email protected]> wrote:
> The conclusion (always provisional) is that @shadow is not well suited
> to collaboration, and that @thin should be the basis of any work
> shared via bzr. We could then consider some "magic" that would
> eliminate sentinels for Leo *insiders*, but the payoff isn't all that
> big. My own sense is that sentinels are, *by far*, the simplest thing
> that could possibly work for Leo insiders.
I'd like to say one more thing about #...@leo-db sentinels. Recall that
these sentinels would allow Leo insiders to eliminate sentinels from
@thin files.
This might seems like something that should be done, but I have my
doubts. It requires both bzr magic and something like zodb magic. It
creates a connection that could be broken between the db and the
actual file. It may be rare for that connection actually to be
broken, but lots of information will be lost when it is broken.
Most importantly, changes to external file create an @shadow-like
situation. It no longer becomes trivial to update the outline based
on changes to the external file. This looks like a show-stopper to
me. At the very least it introduces significant complexity into the
heart of the @thin read logic.
For all these reasons, the "magic" we discussed yesterday looks more
and more like heroism. And for what? For code review, we can just
change @thin to @shadow...
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
-~----------~----~----~----~------~----~------~--~---
