Mario, Thanks for reviewing this as far as being a fully integrated solution. I think its complexity and performance issues you raise indicates this "integrated case" not be done.
I am confident a solution I have will not have "link rot". Personally the provision of links and transclusions that allow the title to be changed is an "edge case" in my view. I can see how in some particular circumstances it may be necessary yet there are workarounds. - My interest is academic, as I do not currently have a need for such a solution; and with respect to those who have asked for It, I suggest developing your tiddler naming skills and the way your tiddlers are organised will get you out of a lot of trouble. Perhaps using data tiddlers is a way for them to structure their data. - However for this edge case I already made a button that will set a unique ID on a "nominated" tiddler. I even avoid javascript by indicating with a red button it is not unique (occurs with cloning tiddlers) it is pressed again and a new unique number generated. Once the ID button is green it remains as an indicator but no longer changes the ID. This can also be done to a list of tiddlers to apply unique ID's in bulk. - Now with a subset of tiddlers that have a unique value in a field it will be simple to make a set of macros that allow the unique ID to be used to transclude, or link to the containing tiddler, and uniquei-id[IDn] can be used in filters. - That is the links or transclusion can be placed anywhere and are only used when rendering a tiddler containing such link or transclusion. I can satisfy the requirements, but have no need to, so if someone has a reasonable case demanding it, I hope they let me know and I will finish building it. Otherwise I will build it when, and if I need it. Best wishes Tony On Tuesday, July 24, 2018 at 7:36:02 PM UTC+10, PMario wrote: > > On Friday, June 8, 2018 at 6:06:06 AM UTC+2, TonyM wrote: >> >> Marion, >> > > -n > > >> Requirements to support unique-ID's >> >> As discussed elsewhere It would be great to get Uni-links help support >> Unique IDs for tiddlers. I believe it may be a quite simple modification. >> > > :) not really. ... I'm thinking about UUIDs since early TiddlySPACE > <https://web.archive.org/web/20161205112404/http://paperstack.tiddlyspace.com/#%5B%5BTiddlyWeb%20ID%20generator%5D%5D> > > days (2011). ... The main problem I'm facing over and over again, is to > create a "really" unique ID, that doesn't suffer "link-rot > <https://en.wikipedia.org/wiki/Link_rot>". It doesn't make sense to use > UUIDs, just because we can. ... > > > >> Current >> >> - Assuming a tiddler has a unique-id field is is currently only a >> matter of adding the unique ID to the aliases list. >> - Then this tiddler can always be referred to >> as [[20180601231113983|?]] regardless of any future name. >> - However this currently displays as a link 20180601231113983 >> >> <http://127.0.0.1:8088/Development/disposition.html#Test%20Tiddler%20with%20ID%20as%20alias%20New%20Name>, >> >> Ideally this would display the subtitle, caption and title before and >> instead of the alias. >> >> > Technically, this seems to be possible. The main problem is the caching > and lookup mechanism. ... It needs to be fast with many tiddlers. The alias > handling implements some low level functions to make alias "backlink" > handling fast(er). ... The UUID handling would need its own functions ... > So we will have 3 different caches: standard link-backlinks, > alias-backlinks and uuid-backlinks. > > So the whole mechanism starts to get slow(er), since all 3 of them have to > be kept up to date. ... Every single one of them needs to touch every > tiddler in the system. ... IMO the whole core caching mechanism would need > an update to do all the work in only 1 run, instead of 3 ... > > > Unique ID support >> >> - To assist and generalise perhaps there could be an alt-name field >> in tiddlers that one could populate (with the Unique-id) and other >> alternative names, or even name the unique-id field >> - As far as I can see the only difference to an alias is the display >> tittle would be the current (subtitle, caption or title} of the tiddler >> containing the alias. >> - In its own field or included in the list of aliases the user just >> needs to honour the convention (make it unique, and not edit or delete >> this >> value) which you could recover by searching for its use anyway, and if >> not >> used simply regenerated. >> >> The concept is clear ... I'm only concerned about complexity ... for new > users ... > > I think a Editor Tool bar option to support the tiddler selection of using >> (the current) tiddler name (with an alt-name) but inserts an alias to the >> alt-name not the tiddler title. I think I can make this. >> > > I personally don't use the toolbar. Clicking buttons, while typing a text > is a pain, and drop down menus are evil. The editor needs to handle those > functions. The toolbar should have been a plugin, that I can remove. > > What would be seriously nice is if we could transclude a tiddler using its >> Alias or uniqueID because even templates and other special tiddlers could >> become name independent. >> > > Yea, the aliasing mechanism has to be deeply implemented into the "core > mechanics" ... That's why, there is still a long way to go until it will be > ready for "the core" ;) > > Transcluding items by their alias could allow the alias to change where it >> is set (ie change the relevant tiddler) or permit multiples to be >> trancluded because they share the alias. >> > > We only would need to see, how fast the look-up functions can be made. ... > The internal structure of TW is optimized handle tiddler titles. Every > other lookup needs a significant amount of javascript, to be executed. .. > tiddler-title is (kind of) "basic memory access". > > This would be a simpler way to replicate the behaviour of display items >> tagged such as in view and page templates, without using tags. >> > > I'm not sure, what you mean here. ... > > 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5c567ad7-edef-4c6d-8e82-c67da85a96a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
