On Wed, Apr 15, 2009 at 3:57 PM, Alia K <[email protected]> wrote:
>
>
>
> Edward  wrote:
>> I don't understand this yet, but my intuition says this could be big.
>
> One way to think about this idea is that a functional directive is
> like a python decorator, which decorates a leo head or body instead of
> a function.
>
> You can then use these directives to do wonky things with your leo
> nodes, like create an '@pdf' directive to output the contents of its
> container (most likely a body) as a pdf
>
>> Indeed, at the most basic level, Leo is about nodes.  Yes, there is more
>> than that--for example, nodes have structure--but nodes are the essence of
>> Leo.
>
> It kinda fun hanging around that abstraction level for a while.
>
> I'd love it if we push this concept to create dynamic, or self-
> updating subtrees in leo... you could have a leo mashup (-:
>
>> Another name for nodes could be objects, or data.
>
>>
>> @button is so important because it lets nodes enhance (or work on) nodes.
>> Your idea might do the same.  In Leo's world, nothing could be more
>> fundamentally important.
>
> Some time ago there was a thread on the use of Sphinx with leo, so I
> tried to try my luck with this project, and it just struck me how
> natural it felt and how usable it all turned out to be.  I'd say that
> leo is by far the best editor for restructured text.
>
> The best part of the usability boost

Great phrase, and your research looks to seek another
usability boost, additional power at reduced overhead.

Vrooom.

 came from  creating a simple
> @button which wrote the restructured text, rendered the sphinx docs
> and opened the browser...
>
>
> AK
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to