On Thu, Apr 16, 2009 at 9:57 AM, Edward K. Ream <edream...@gmail.com> wrote:
> > The present situation reminds me of my first impression of e's > dynaButtons. I didn't really understand them at first, but the phrase > "bring scripts to nodes" eventually lead to @button nodes and the > mod_scripting plugin. > > At present, I am floundering around with these ideas. But this is the > kind of floundering I live for. As I have said many times before, a > prerequisite for creativity is the ability to live with confusion and > uncertainty with calm excitement instead of fear. First, I'd like to thank all who have contributed so far to this thread. The comments have been useful and provocative. I think this discussion is doing well. I'd like to step back a bit from the details for a moment. It seems to me that if something "big" is going to come out of these ideas, then that "something" must have immediate, significant impacts on Leo and, perhaps, programming in general. We should not, imo, be looking for techniques; we should be looking for applications. For example, the result of e's dyna buttons was @button nodes (and the mod_scripting plugin). This was a big step forward; it immediately rendered obsolete the too-difficult-to-use find/change scripts. The good thing about big ideas is that they aren't necessarily tied to details. In the spirit of playing with ideas, suppose we had the following leo directives (or @cl kinds): @command creates a Leo command. *Not* the same thing as an @command node, but possibly related. @plugin creates a Leo plugin. @test creates a unit test. *Not* the same thing as an @test node, but possibly related. @view creates a view on a node, tree or element. @f creates an external file. Possibly equivalent to @shadow. @namespace creates a (named?) namespace. @module creates a named python module. @command, @plugin, @test, @namespace and @module hint at a ways of "composing" Leo from parts. Perhaps this new way would allow people to replace leo-editor with a collaborative doc... All this is pure speculation. I throw it out to encourage people to imagine new uses for @cl or @leo.directive. All comments are welcome. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
