Thank you Tobias for giving me and other interested peers the
opportunity to elaborate a bit on this:
You understand me right, that there is even more potential in it, than
"only" replacing the internal wiki links by it. In TiddlyWiki, I
suggest, to extend the parser a bit, to allow embedded
GoogleTagCombinations, as e.g.
$GoogleSearchTerm1,Comment1 ....some text ...
$GoogleSearchTerm2,Comment2 .. etc,
for calling the above defined (and to be improved) function g that
call g("GoogleSearchTerm1",Comment1) ....some text ...
g("GoogleSearchTerm2",Comment2) ....etc.
These interspersed calls produce (in the TiddlyWiki view-mode) option
boxes, that can be (un-)checked by the users and used as a Google
query by clicking an additional command-link, that is added to the
line, where you have already: "edit","done", ... : This way the new
command line shows up as: "edit","done","search", ... For convenience,
"search" should only be shown, if there is at least one
GoogleSearchTerm defined.
Another good idea, you imply, is: that we should have a "dual use" for
the GoogleTagCombinations, similar to the following example, that is
handled in the Aboutus wiki: GoogleIcon.png TiddlyWiki.
With one marker you get at the same time, two links: one pointing to
Google and the other one, to an internal wiki link. Now think this
latter template tool generalized to arbitrary (Google-) Tag
Combinations and you see the power of this construct and how useful it
is for (collective) filtering (in communities).
Please have a look at <->[[2]] where interested developers and plug-in
programmers can deepen the dialogue on this special topic.
fridemar 05:04, 16 July 2008 (PDT