The more I think about it, the more Kent's response:
"Dingdingding! That's the prizel."
to the question::
"Wouldn't it be great if we all could remember what we,
and others, have already done :-)"
points the way to some great new features of Leo. Maybe even a
unifying, simplifying framework:
1. Improving the quicksearch plugin: Adding cross-file capability and
more key bindings.
2. Improving bookmarks: Allowing {{expressions in urls}}.
Both can be generalized:
1. Perhaps *all* searches should (optionally) provide a quicksearch-
like list of matches. This suggests making quicksearch a part of
Leo's Find tab. Similarly, the find tab should have a "Search All"
checkbox.
2. Bookmarks might be the key of several long-requested features.
Suppose that following a bookmark might optionally *create a node* in
the *referencing* outline.
This gives us:
A. A kind of cross-file clone: the new node would have the same gnx as
the target.
Maybe we should call the created node a link (or target) node.
B. A kind of clone-without-cloned-descendents.
3. Suppose we define @search nodes, that perform *dynamic* searches in
various ways. Unlike static bookmarks, they will be updated as
needed. And suppose we integrate them with either quicksearch or
Leo's search Tab. And the results of the search could *be* bookmarks.
In short, links, searches and searchable attributes might give us the
prizel. Perhaps these will moot the need for any kind of central
repository or client-server architecture. If so, it is a big collapse
in design complexity.
Your comments, please.
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.
