If WhatIfMark would be a subset of TW syntax and TW syntax would be a subset of WhatIfMark we could do really crazy stuff.
The main downside is: That's completely incompatible, to everything that exists at the moment. So it would be a completely new system.
...
Having said that - a significant subset of tiddlers can bemade with simple transclusion and filters - it might be nice tohave a portable subset of tiddlers that did not do anything too fancy.
... In retrospect I was far too influenced by Markdown back in 2011/12 when TW5 wikitext was first being defined.
Joe Armstrong wrote: Tiddlers contain far more than markup. There's wiki text with an embedded programming language and an implicit environment ...
from another thread, relevant here ...
Jeremy Ruston wrote:... In retrospect I was far too influenced by Markdown back in 2011/12 when TW5 wikitext was first being defined.
Side note I want to make on just this point about Markdown. I remember when Markdown emerged (as an end-user / avid blogger) thinking "this is a godsend". But also, "this is likely to become a somewhat messy non-standard standard long-term" -- because its "just too easy." If you get what I mean?
Content-Type: text/markdown; charset=UTF-8; variant=Original
As you pointed out, there is a lot missing in "original" markdown, but now there is a formalized mechanism to register all kind of new very specific syntax additions. ...
AND TW is _not_ one of them. So in the long run we will loose, if we don't do it right.
As you pointed out. TW has the potential, to convert one syntax to an other (with some limitations). ... BUT ... not with the internal AST, that we use at the moment.
See my first post. ATM we are loosing whitespace information.
just some thoughts
mario
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/NKOnq3hKryo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
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/f14591a6-f08d-482e-a80e-f10953d57171%40googlegroups.com.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
How important, in your opinion, PMario, are RFC's to TiddlyWiki's uptake?
I can't honestly say for myself that an RFC motivated me to do anything. At the same time I do understand they have a role. BUT is it *before* the fact or *after*?
In other words, for TW, WHAT exactly should we be promoting to it?
And WHY?
MD took off, as github and others "re-discoved" it to create static html sites in 2010. Github used it first "to prettify" README files ...
On 13 Mar 2018, at 19:15, Joe Armstrong <joe...@gmail.com> wrote:This would involve partitioning (splitting big pages into smaller tiddlers)removing styling and guessing the structure
If you have a closer look, there is no "table" definition. .. It's missing.
AND they don't have an idea about transclusions, widgets, and other stuff that is essential for tiddlywiki. ... But as far as I can see it, at the moment they don't use syntax like <<>>, {{}}, {{{}}} or <$abc>
On CommonMark ...
PMario:If you have a closer look, there is no "table" definition. .. It's missing.
AND they don't have an idea about transclusions, widgets, and other stuff that is essential for tiddlywiki. ... But as far as I can see it, at the moment they don't use syntax like <<>>, {{}}, {{{}}} or <$abc>
Frankly, I can't see how dynamically rendered "programmatic syntax" (i.e. markup that invokes functions specific to an implementation) could become any standard. As far as I understand it all the simple "markups" use HMTL/CSS substitution and it is THAT which allows inter-variant conversion. But for anything else: WHAT are they substituting?
+-----+-----+
| text | more text |
+-----+-----+
table-title: test
table-caption: bla bla
table-rows: 3
table-columns: 3
h1: header 1
h2: header 2
h3: header 3
a1:
As much text, as I want to write here
a2:
more text<br>
with a hard line break
b2:
column 2 row 2
b1 is empty
c1..c3:
Text that spans 3 columns
I don't want to mess with some ASCII art to get a table going.
On further thought and reading some of the below replies, I wonder if we are often confusing TiddlyWiki Features with Markups/Markdowns.
I ... do everything I can to have only markdown in the text field of tiddlers I expect me or a user to read. I am quite content with TiddlyWikis standards although I do extend it with CSS or HTML tags some times...
The way I do this is to use the view template ... keeping macros out of text tiddlers as much as possible.