It would be useful if TW could work as a custom markup 
constructor+interpretator.

I.e that it featured "*potential* wikitext markdown" that people can 
CSS-style freely. For example, we currently have the list elements * and : 
that give predefined <ul><li> and <dl><dd> with specific styling. It would 
be neat if e.g § or other characters would trigger custom styling IF the 
user choses to define such styles. If no style is defined then, I guess, 
the characters and subsequent content displays as usual.

Notably, HTML has this built in i.e it allows custom tags like <mytag>Lorem 
ipsum</mytag>, but the requred angle brackets and possibly closing tags 
make this too verbose. I want a smooth wikitext markdown command.

I identify two "base cases"; one with a opening and a closing mark (compare 
to a div). And the other as list element marker with only an explicit 
opening mark and an implied closing mark consisting of newline or similar.

One idea would be to use the aforementioned § character. IF a row is 
prefixed with § and has a subsequent empty row (or end of tiddler) then it 
is interpreted as a list element. If the row instead is encapsulated with a 
§ and a suffixing § then it is interpreted as a div. For example the first 
case could be interpreted as <li class="custom-li"> and the second case as 
<div class="custom-div">....</div>.

We'd get infinite options if one could use §1, §2, ...

(Possibly the character should trigger more than mere CSS. I would guess 
pipe characters, when creating wikitext tables, do this, right? In that 
case, § could trigger some user defined *macro*, perhaps titled § ...or §1, 
§2... to operate on the text snippet in question.)

Thoughts?

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/5903cfa3-a73d-475c-8762-876adb903d16o%40googlegroups.com.

Reply via email to