Eric:
I could comprehend the aspect of "dynamic" nature of a tiddler's
content so that 1-to-1 matching is hard. How about trying to match
the string ("clicked word") underneath the mouse clicking to the
tiddler's content. If the content of the Preview panel can be
acquired and a group of nearby words (or phrase) is used to match to
the tiddler's content. If a match is found, then the auto-scrolling
will occur or nothing happens otherwise.
A more user involved version would be: users highlight certain phrase
in the Preview (or even copy to the clipboard if necessary) and click
a short cut key (or button), then the phrase matching is conducted.
Users have the better knowledge about what is actually inside this
tiddler and may simplify this searching process.
Just a still learning newbie's idea. Thanks!
Duke
On Feb 13, 1:59 pm, Eric Shulman <[email protected]> wrote:
> > it is possible to click on the Previewed text and then the "edit box"
> > auto scroll to the matching line (and vice versa). If it can be done,
>
> While it may be relatively simple to know the x,y position of a mouse
> click, there can be multiple DOM elements that all overlap at any
> given x,y location, so it is somewhat more difficult to figure out
> which element the user actually thinks they are clicking upon.
>
> Unfortunately, even if a specific clicked-on element can be
> identified, finding "the matching line" in the tiddler soruce is
> really hard. Basically, the TW rendering engine, wikify(), is a one-
> way translator: it processes wiki syntax and macros and then renders
> one *or more* DOM elements into the current tiddler display. For
> example, if you've used <<tiddler>>, <<tabs>>, or <<slider>> to
> transclude content from another tiddler, the rendered output will have
> numerous DOM elements that aren't even defined in the current tiddler
> source. Thus, there isn't always an unambigous one-to-one
> correspondence between the rendered content and the current tiddler
> source content.
>
> There are also lots of plugin-defined custom macros that can generate
> multiple DOM elements that vary based on the macro's parameters. As a
> result, it's nearly impossible to determine a match between a given
> clicked-on element and some corresponding macro instance... and, even
> if it were possible, I expect that the code to do it would be
> ridiculously complicated.
>
> sorry.
>
> -e
> Eric Shulman
> TiddlyTools / ELS Design Studios
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" 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/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---
