Thank you, Daniel. I have had the benefit of a lot of feedback and experimentation from some smart and dedicated people over many years - astonishingly, TiddlyWiki will hit its 10th anniversary in September this year.
Best wishes Jeremy — Sent from Mailbox for iPad On Sun, Feb 23, 2014 at 11:12 PM, Daniel Baird <[email protected]> wrote: > Awesome. That's one of my favourite metafeatures of TiddlyWiki -- the > clear and careful thinking that goes into selecting features :) > ;Daniel > On 21 February 2014 19:39, Jeremy Ruston <[email protected]> wrote: >> My plan is indeed to implement a very similar feature (listed in the >> roadmap on tiddlywiki.com as "Aliases"). >> >> The idea is indeed that certain operations will be capable of >> dereferencing special alias tiddlers, which would end up resolving to a >> different tiddler. There would be an option on the transclude widget to >> select whether or not to dereference aliases (that would be necessary to >> allow us to edit aliases themselves). >> >> Quite early on I discarded the idea of maintaining a separate list of >> aliases attached the each tiddler. The problem there is that (a) one has to >> modify a tiddler in order to give it an alias, and (b) that looking for a >> tiddler would require us to look separately through the aggregated alias >> lists, which would also be expensive to maintain. >> >> Best wishes >> >> Jeremy >> >> >> >> >> On Fri, Feb 21, 2014 at 2:16 AM, Daniel Baird <[email protected]>wrote: >> >>> >>> I prefer redirection to just having a bunch of explicit aliases. >>> >>> I like the infinitely-nestable idea but it might be difficult to >>> implement. An alternative might be that if you make a tiddler into a >>> redirect tiddler, part of the process of saving that goes and finds other >>> tiddlers that pointed at this one, and rewrites them to point to the new >>> destination directly. >>> >>> That way redirection is always one step (but if you saved the wrong >>> redirection, you'd have to go back and update all the other redirections >>> etc, which would suck). >>> >>> I'd rather have the nesting, but getting that might require some crazy >>> implementation hoop jumping. >>> >>> >>> >>> On 21 February 2014 12:03, <[email protected]> wrote: >>> >>>> Is it remotely possible to add internal handling of something like >>>> symbolic link tiddlers such that a link tiddler, when referenced in any >>>> capacity (link, transclusion template, etc.) is seamlessly dereferenced to >>>> its target first? Links should be nestable, so if the target of a link is >>>> also a link it dereferences again, etc. Though then there would have to be >>>> a check for cycles ... hmm. >>>> >>>> This would sidestep the renaming / refactoring that is listed in the >>>> future plans. If you want your tiddler to have a new name you just create a >>>> new tiddler with that name and all the properties you want it to have, then >>>> turn the original into a "symlink" tiddler. >>>> >>>> More importantly it would allow for circumstances where a tiddler has >>>> more than one correct name. E.g. suppose you are keeping a TW of plants and >>>> each tiddler is titled with its proper latin name, but you still want to be >>>> able to [[link]] to it by its common name. Elegantly, it would also handle >>>> the case where a tiddler has a whole list of correct names, for which I >>>> can't come up with a good example! >>>> >>>> I'm happy to try implementing something like this if you can point me in >>>> the right direction. >>>> >>>> Thoughts? >>>> >>>> -- >>>> 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 http://groups.google.com/group/tiddlywiki. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> Daniel Baird >>> retro objoke: Chuck Norris had a problem so he decided to use regular >>> expressions. Now, every problem in the world is solved. >>> >>> -- >>> 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 http://groups.google.com/group/tiddlywiki. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> >> -- >> Jeremy Ruston >> mailto:[email protected] >> >> -- >> 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 http://groups.google.com/group/tiddlywiki. >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- > Daniel Baird > retro objoke: Chuck Norris had a problem so he decided to use regular > expressions. Now, every problem in the world is solved. > -- > 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 http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
