Opinion: Potentials #1: TW Markup

[@TiddlyTweeter]

The markup potential of #TiddlyWiki is huge.

Its architecture, in theory, could make it a universally clever markup machine.

IMO "smart markup" in now needed. Older systems are looking a bit tired with ridiculous incompatibilities. The days of the "dedicated method" are really well over. We have flex.

Would it not be a good idea to enable users to more easily design their own markup coding systems? Or provide easier access to the multiple simple systems that already exist for markup?

Best wishes
Josiah

[coda coder]

Hi Josiah

On Friday, November 10, 2017 at 5:14:52 AM UTC-6, @TiddlyTweeter wrote:

The markup potential of #TiddlyWiki is huge.

Its architecture, in theory, could make it a universally clever markup machine.

A UMM :)

You just coined a new term, I think.  Nice.

 

Would it not be a good idea to enable users to more easily design their own markup coding systems?

Yes.  As a first step, improved JSON handling would help the ecosystem. That is, TiddlyWiki's "shallow" parsing of JSON structures needs improving, IMO.

Javascript isn't going anywhere (not for a long time, anyway).  Everything that happens in TiddlyWiki is marshaled by/through Javascript.  JSON (as Javascript's native data interchange format), is (should be) therefore, the "currency of choice" for any Javascript ecosystem. Indeed, just as it is in TiddlyWiki right now, but moreso.

How that might be exposed to the masses to get back what you're asking for, I'm really not sure.  Maybe (maybe!) some JSON-defined ASTs, providing the mappings of terms-to-productions (yes, even regexes) would work?

 

Or provide easier access to the multiple simple systems that already exist for markup?

Not sure I know what this means... what are these "simple systems" you refer to? Examples?

Coda

[Mark S.]

If there was a universal mark-up, then there could be a mark-up for all those Tiddlers still in TWC format.

Mark