I wonder if pyfilesystem is germane
http://code.google.com/p/pyfilesystem/

LeoFS could be on that list :-]

On Mon, Sep 9, 2013 at 9:20 AM, Jacob Peck <[email protected]> wrote:
> On 9/9/2013 10:06 AM, Edward K. Ream wrote:
>
> On Sun, Sep 1, 2013 at 11:17 AM, gatesphere <[email protected]> wrote:
>
>> I'm imagining a Leo-based operating system.
>
>
> Interesting idea ;-)  I myself enjoy big thoughts, even if they are only
> thought experiments.
>
> There are several hurdles to be overcome, at least:
>
> 1. If you are going to replace the file system, there must be a way to share
> data.  Leo doesn't make this task easy.  Yes, you can share external files,
> but then you are back to a file system.  Without external files, the only
> unit of sharing appears to be the .leo file, that is, the replacement for
> the entire file system! I've thought about such things for many years.  I
> don't see a way around the problem.
>
> Very true...  It's an ugly, sticky problem.
>
> Unless there are two filesystems, one Leo-based and one that provides an
> external view.  Or I could just go the traditional route of having an actual
> filesystem, and access it with .leo files (active_path perhaps?).
>
> 2. I'm not sure whether you intend to use Qt for Leo's gui.  I suspect not,
> since you are talking about using Leo's bridge.  In that case, you are going
> to be doing a lot of extra work.
>
> The leoBridge usage was going to be for init scripts.  I'm now thinking that
> I could simply have a master .leo file in /etc/systemConfig.leo, which would
> access all the init and config scripts in one place, without the need for
> bridging.  The Qt gui would be the default, root-level window that
> everything else (graphically) spawned from.
>
> 3. Reinventing tools such as web browsers and mail readers is the wrong
> direction.  There is an infinite amount of *new* work to be done. Redoing
> old work (the work of hundreds if not thousands of programmers) can not be
> the way.
>
> As mentioned in a different thread, a QX11Embed widget/plugin could do all
> the heavy lifting here - on X Windows systems (like most Linux distros), it
> can literally embed an entire application within a widget.  Install chromium
> or firefox and embed it in Leo.  Install thunderbird and embed it in Leo.
> Install midnight commander (for the filesystem users) and embed it in Leo.
> Done and done.  The plugin would be XWindows specific, but I don't see that
> being a major problem.  It wouldn't even involve changes to Leo's core, I
> don't think.
>
> In short, I encourage you to keep thinking interesting thoughts until you
> come up with an idea that can be done *quickly* (days or weeks, at most).
> This was the place I was stuck initially (after the Aha that webs are
> outlines in disguise) until I saw that I could use the MORE outliner as the
> prototype for Leo.  It was then a matter of hours before I knew I was on the
> right track.  @others was born in the first day of prototyping, and the
> programming style I used that first day has remained remarkably unchanged
> until the present.
>
> And what a boon @others is!  It's so hard for me to use other editors
> nowadays.  If I'm not in Leo, I'm in vi, because I can sort of fake
> outlining with it... by using comments and the find function.  It's not
> ideal, but it's what I've got.
>
> Edward
> --
>
> -->Jake
>
> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to