On Sun, May 18, 2008 at 2:19 PM, Kent Tenney <[EMAIL PROTECTED]> wrote:
> > I see Leo as a platform, I think the 'Next Big Thing" can be that > what is built with Leo... > > I picture a Leo file with documentation, a smart node which will open > a set of files on the filesystem, safely, without impinging on them. > Buttons and commands are tailored to the application, protocol, or service > this particular Leo file has been prepared for. This file does ONE thing > amazingly well. Another Leo file next to it is built to do one other thing > amazingly well. They each have different buttons, menus, commands, > @nosent nodes. Leo is used to create file-based toolchains / tutorials. > The ONE Leo file does exactly what it's author wants it to do and the > Leo file mirrors his understanding of a topic, collapsing much of the > complexity of configuration, dependencies, maintenance. An interesting vision. I like it. > > Required is: > > 1 brilliant hierarchy management > 2 brilliant Python integration > 3 brilliant non-intrusive path and file capability > 4 dead simple, cascading configuration > > 1 and 2 stand alone in available tools, 3 frustrates me, 4 seems like > it won't happen. I think 3 and 4 are on the list. Here's the to-do entry for 4. It's in a node called 'Solve Kent's @menu problem': QQQ http://sourceforge.net/forum/forum.php?thread_id=1858451&forum_id=10228 I'm interested in using @settings to create application specific mini-editors. I think there's great promise in @settings nodes which create an environment with buttons and menu choices to work with specific file types, or other niche applications. The menus and buttons will expose a set of capabilities, and unneeded capabilities will be hidden. However, if I create a @settings->@menus->@menu node in a file, open the file, then open another Leo file, the next file opens with the redefined menu. QQQ Is there something else that needs to be done? Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
