On 7 sep, 00:13, "Ville M. Vainio" <[email protected]> wrote:
> On Sun, Sep 6, 2009 at 10:15 PM, Yannick Duchêne Hibou57
> Depending what you mean by link capability, backlink.py plugin might
> provide what you want.
>
> --
> Ville M. Vainiohttp://tinyurl.com/vainio
I was not only talking about it, while its true I had talk a lot about
it too.
As you point it, I think I should be clearer about what I was to mean.
Talking about browsable, I was not thinking about back-link like
you've introduced. And true, I guess this can be done in Leo with
Python (its just a long time I didn't, and will have to come back into
it now). I was nearer to talk about ergonomy and layout, which is an
important part of any environment... and language oriented
environment. Talking about the links of CodeBrowser, as was talking
about links inside the text, as opposed to child nodes beside in Leo.
In Leo, you have node, and some child nodes. Child nodes displays at
one side of the parent node.
In CodeBrowser, you got outline, thus child nodes (which are named “
folders ” in the CodeBrowser terminology), are inserted in the parent
node.
Another light on the difference, still meaning the same : with Leo,
child nodes are attached to the parent node, but not to a location in
the parent node. In CodeBrowser, child nodes (viewed via there
headings) are attached to a location of the parent node.
There is also a tree-view in CodeBrowser, like the one in Leo, but the
main layout is different in the sense the source more looks like a web
page with links inside (you got a somewhat similar thing in Leo, but
only with section references).
Important note : there is no tangling in CodeBrowser. If you want to
achieve literate programming with it, you have to use references : you
start to write somethings as normal code, with foldings and headings
(this is not syntactic driven folding, but markup driven folding,
although the markup is properly hidden while editing, and encoded in
comments, like Leo does). Then, you create a literate view creating
others folders containing headings which does no stand for folders
this times but for references to folders which are part of the code.
This is the exact opposite way as the you have with Leo. Leo starts
with literates and end-ups in code via references and tangling, while
CodeBrowser start with code and ends-up in explaining it via literates
and references. In Leo, the material is the literal and the product is
the code, with CodeBrowser, the material is the code, and the product
is the literate.Both use references to build the product from the
initial material.
To be honest as well, just like the back link you were talking about,
it should be possible to follow section references as if they were
CodeBrowser-like links in Leo too.
I've tried two different environments (GPS is not really an
environment, but mostly a set of tools, so I drop it at this point of
the discussion). There have some similar things, belong to different
approaches. That's why I was thinking back again about Leo with new
ideas (the one I've printed into my mind using CodeBrowser).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
