Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

Hi Evan > > The trouble there is that the plaintext vocabulary wouldn't permit widgets, > which would rule out using the list widget. So we would need to be able to > select the output mode between HTML and plain text (that's a setting that we > already support for transclusion). > > A

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

Hey, Jeremy — > The trouble there is that the plaintext vocabulary wouldn't permit > widgets, which would rule out using the list widget. So we would need to be > able to select the output mode between HTML and plain text (that's a > setting that we already support for transclusion). > A

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

Hi Evan > Vocabulary as a general concept seems like it fits the bill. At that point, > "smart" attributes would just be treated as wikitext with the "plaintext" > vocabulary. The trouble there is that the plaintext vocabulary wouldn't permit widgets, which would rule out using the list

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

Vocabulary as a general concept seems like it fits the bill. At that point, "smart" attributes would just be treated as wikitext with the "plaintext" vocabulary. I have to confess I'd forgotten about typed blocks when I wrote the OP, and by running at parse-time they solve some of the

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

Hi Evan I think that this ancient ticket might be roughly equivalent to what you’re after: https://github.com/Jermolene/TiddlyWiki5/issues/345 The proposal still reflects my thinking in this area. Best wishes Jeremy. > On 12 Jan 2018,

[twdev] Proposing a plaintext parse & render mode for attributes & more

Hey, all — Currently TiddlyWiki implements plain-text wikification by applying WikiText parsing to generate a DOM, then extracting and concatenating any text-widgets in the DOM while discarding everything else. While this functionality is very useful, it has some tricky drawbacks —