maintain links to dev edition

[Eucaly]

There are couple of tiddlers moved to "dev edition" and lost link from tw5.com Could we maintain those links by a batching method, or should we re-link them manually to http://tiddlywiki.com/dev/index.html# ...

The tiddlers are now in below folder TiddlyWiki5 / editions / dev / tiddlers / from tw5.com https://github.com/Jermolene/TiddlyWiki5/tree/master/editions/dev/tiddlers/from%20tw5.com

[Jermolene]

Hi @Eucaly

Could we maintain those links by a batching method, or should we re-link them manually

How many links are involved? I'd be inclined to deal with them manually.

[Eucaly]

• by "standard search" or "filter search" (e.g. [regexp:text[JavaScript Macro(?i)]] ) with the essential keyword from some of below titles, I think there's 1~3 links from each of below.
• I can do the modification later, because any how I would like to go through some of them to learn something.
• But, [[How to create a translation for]] seems not referenced by tw5.com ??
• And, should I modify something mentioned in release note also?
• for example, [[Release 5.0.9-beta]] mentioned
• * Added overview diagram of [[TiddlyWiki Architecture]]
• * Added documentation from buggyj: [[Developing plugins using Node.js and GitHub]]

Developing plugins using Node.js and GitHub How to create a translation for How to create plugins in the browser How to customise the password prompt JavaScript Macros Procedure for releasing a new version of TiddlyWiki5 TiddlyWiki Architecture TiddlyWiki Coding Style Guidelines TiddlyWiki for Developers TiddlyWiki on node-webkit TiddlyWiki5 Development Environment package.json for node-webkit

SyncAdaptorModules WidgetModules WikiRuleModules

[Jermolene]

Hi @Eucaly

But, [[How to create a translation for]] seems not referenced by tw5.com ??

I tried to clean up some of the links from tw5.com to the dev material, and I guess that was one of them.

And, should I modify something mentioned in release note also?

I tend not to retrospectively update the release notes as it can make things confusing.

[tobibeer]

I know this can be easily done and I'll be writing a litte tutorial, but I think a JSON DataTidler for conditionally showing a link to the new destination for all indexed tiddlers will be nice (even if they exist!), containing something like...

{
    "$:/old/title": "moved to [[$:/new/title]]",
    "Another Old Title": "deprecated: please look [[here|New New New]]"
}

[Jermolene]

Hi @tobibeer it sounds like you're asking for a species of simple alias support?

[tobibeer]

It's all there already, I love this stuff. ;)

Redirecting Dead Links

[Jermolene]

Cool.

You've given the content type "application/JSON" when I think it actually has to be lower case.

Also, wouldn't it be more convenient to use a application/x-tiddler-dictionary tiddler?

[tobibeer]

You've given the content type "application/JSON" when I think it actually has to be lower case.

Yes, thank you, fixed... didn't pay attention. Does it matter for the core? (didn't find right spot)

Also, wouldn't it be more convenient to use a application/x-tiddler-dictionary tiddler?

For other users, yes. Practically, I am hiding my configuration stuff / templates / macros / stylesheets as system tiddlers which appears to not make application/x-tiddler-dictionary an option... unless the dictionary-handling were designed exactly to account for this one exception where a key can contain $:/foo without being understood as $ = '/foo'... which sounds like a smart choice to make. Or even better: allow for the ability to set any [[tiddler with titles and: foo]] as keys.

Not sure if there are other advantages or disadvantages between the two. If you know of any off the top of your head, please post them here or at the appropriate doc tiddler on TiddlyWiki.com