On Mon, Oct 17, 2011 at 7:41 AM, Kent Tenney <[email protected]> wrote:
> IMO it's a major breakthrough for Leo, and as a pattern for
> data retrieval in general.
Thanks for this. You have been the most insistent on improving and
generalizing Leo's design.
Recent revs to to the trunk complete, with perhaps one or two small
additions to come, a grand redesign of all of Leo's @command/@button
nodes:
- Significant @command nodes now appear in:
leoSettings.leo#@settings-->Common @command nodes
-->@commands-->@ignore
That is, they are define in as common global @command nodes, but they
are ignored. Move them to myLeoSettings.leo as needed.
- @buttons appear only local to specific files. See leoSettings.leo
for check buttons and LeoDocs.leo for various preview buttons.
In other words, the new org uses @command for global scripts and
@button for local scripts. This makes sense for two reasons. First,
we can't use @button for global scripts because that would overwhelm
the icon area. Second, using @button for local scripts draws
attention to scripts that only make sense in a local context. It's
very effect.
Edward
P.S. Except for the relatively minor tweaks, Leo already had
everything needed to support this scheme. In particular, Leo already
supported the distinction between local and global @command and
@button nodes.
P.P.S. Earlier today I correct an oversight: Leo now properly
supports @ignore nodes in @commands and @buttons nodes. This is very
useful: no need for @@button or @@command.
EKR
--
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.
