Hi,
Sorry for my late response. I have been working on a translation draft
of an old work about cognition, education, and collective problem
solving trying to get this understandable for English speaking public.
If someone is curious:
http://holonica.net/home/Edumatica/articuloTesisMaestria-en.pdf/view
(but remember, it's only a draft)
More comments inline.
On Wed Oct 12 11:11:21 2011, Edward K. Ream wrote:
Imagine that you can put a leo file inside a Fossil repository and that you
can put all the derived or original files of "@files" nodes under that
repository also. Let's call it a ".leof" (for leo + fossil) extension and
imagine that every time you save the file of a new version of the leo file
or its @files nodes is versioned and saved inside that fossil repository. So
you have a single portable file that contains a "discourse" about changes in
time in the structure of your Leo files, outlines or its associated files in
the @file nodes
Yes. Clear enough.
and that can be coordinated, p2p fashion, with other
repositories like that or with just plain files in your hard disk or in
anyplace where you move that file and leo.
That's what fossil does, right?
Yes. Fossil describes itself as a "github in a box"[1]. The idea of
Fossil + Leo would be to enable features of Fossil for Leo even for the
files inside a project without depending on another VCS. Of course the
idea could be tested with Git or Mercurial or bazaar or anything else,
but none of them is as minimalistic as Fossil.
[1] http://fossil-scm.org/index.html/doc/trunk/www/fossil-v-git.wiki
The added size to Leo for
understanding that "discourse" is 700k in a portable C file. This would be
the way of dealing with the insufficiency of just "everything is a file" of
Unix, so this .leof file format adds kind of an Smalltalk's image
abstraction to storage in Leo and more intelligence in the way Leo works
with its own files history in time.
Very interesting. It does seem like a Smalltalk image.
By analogy with the undo discussion, my guess is that only a
node-oriented version of the "discourse" will have any chance of being
comprehensible in the Leo environment.
May be not. That's the awesome thing about Leo. You can put in a
Leonine way a lot of dissimilar discourses, in this case this could
work with VSC/SCM systems.
Thanks for the further clarification. I would imagine that this kind
of project would move ahead slowly, but who can say now what new
horizons it might bring?
Well, if I get enough Leo users in a more local context, may be I can
start to code to get this projects running. For the moment my
non-programmer ways of doing things with Leo are good enough for
myself, so yes it will be a slow project, but hopefully will bring
interesting things.
Cheers,
Offray
--
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.
