Mario, \define tv-freelinks() yes
But also a field or tag switch or viewTemplate trigger. As I mentioned previously freelinks power is as a research and discovery tool, if we had a quick way to turn discovered free links into real links or aliases, or be able "back list", or "white list" items we could freely turn *off* freelinks after the design and analysis before publishing. ie the overhead is only present in passing. Actually, There is an idea, take what is a discovered freelink and add it to a black list or white list entry, then use these lists to generate links and or alias's. Regards Tony Regards Tony On Thursday, April 23, 2020 at 4:57:30 AM UTC+10, PMario wrote: > > On Wednesday, April 22, 2020 at 7:15:30 PM UTC+2, springer wrote: >> >> Getting an alias field to play well with freelinks is THE DREAM! >> > > hmmm .. ok > > >> To be clear: something like uni-link helps one kind of use-scenario -- >> the one where a single author is generating tiddler content, and is aware, >> while typing, of where there's an alias available. >> > > That's a point > > >> My own case (perhaps like OP here, blarg H) is that I'm often pasting in >> text from elsewhere, and I just want all the resonances to other tiddler >> titles to self-recognize. >> > > A good point too. > > >> Jeremy's freelinks macro is GREAT for that! But simple things like >> capitalization and plurals get broken. And since I'm pasting in text from >> elsewhere (sometimes in a formal-citation context) it's really not >> appropriate for me to mangle the text itself. >> > > OK > > >> I'm in no position to rewrite any plugins (least of all now, given my >> day-job). But I would actually pay real money for this work. And I'm not >> rich. :) >> >> -E Springer >> > > Hi, > Sometimes it needs posts like this, to broaden someone's (my) view, where > it is too narrow-minded. ... > > But ... I still have a problem. It's the potential performance hit with > many 1000++ tiddlers > > As Jeremy pointed out in the freelinks plugin description, the mechanism > used is heavyweight, compared to the "normal" text parsing. Alias-linking > is also relatively heavyweight, compared to standard links. It's similar to > "backlink" handling. > > Both mechanisms use internal caching, to speed up lookups. But we still > have to rebuild this cache very often. This means we need to touch every > single standard-tiddler, to build the cache. > > So from my point of view, we need to make more tests with a huge amount of > tiddlers, tags and aliases. With and without the plugins enabled, to be > able to measure the "real impact". > > My second concern is, about the "false positive" links that can happen if > a tiddler is named "test" or "task" or "in" or "out" ... you name it. So I > personally would prefer a > > \define tv-freelinks() yes > > at the head of a tiddler, instead of globally enabling freelink handling. > ... This doesn't reduce the time to create the cache, but it would limit > the "false positive" links. > > Thinking ... ;) > > have fun! > mario > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5a123420-0343-40c4-9cee-5283dad495ec%40googlegroups.com.
