On Sat, Jan 10, 2009 at 6:39 AM, Edward K. Ream <[email protected]> wrote: > > > On Wed, Dec 17, 2008 at 1:26 PM, Kent Tenney <[email protected]> wrote: >> >> I think this has been discussed before, but I don't remember the outcome. >> >> Would it be feasible/interesting for Leo have a directive which referenced >> nodes/trees in other Leo files? > > Now that I see that you meant something other than @url, I can say that I've > always been dubious of such approaches. The problem is that it spreads > responsibility for text to at least one-too-many places. > > My analogy is this. No organization would tolerate having two managers be > responsible for any particular piece of code. There must always be one > person with ultimate responsibility. One person in charge. Many other > teams might use that piece of code, but chaos would ensue if multiple teams > were changing the same bit of code simultaneously.
Right, and I think that's why the thread soon was about a db backend. The db would be responsible for the content, the Leo files would be 'views' of the content. The concurrency would be addressed according to db principles .. locking, transactions, commits ... A topic for way down the road, if ever, I expect. Thanks, Kent > > bzr doesn't invalidate the analogy. There is only one trunk. > > Similarly, having two or more .leo files "point to" a shared node invites > the same kind of chaos. > > That's the way I see things, at any rate. > > 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 -~----------~----~----~----~------~----~------~--~---
