Bbcode parser plugin / widget (or..whatever)

1

following from this
.Can we allow iframes to tiddlytalk content and is there problems doing it? topic

~if~ post from talk.tw could be imported/embedded/saved in a wiki then i might be nice to support parsing/displaying
bbcode used by discourse

has anyone given this any thought ?

im reminded of reading about “custom tiddler types”
.Create and Use of Virtual Tiddlers - #15 by TW_Tones
and
Extending the type field for user types?

daydreaming eg setting types

text/vnd.tiddlywiki/talk-topic

text/vnd.tiddlywiki/talk-post ( shows content with bbcode (just quotes afaik) mark-ed-up

=>
just thinking out loud realy
… so hopefully? the above techno infused gibberish/jargon
is parse-able by the average forum reader

2

Discourse used Markdown markup, that we already support with a plugin in TW.

bbcode is a different markup language, that is used by some comment systems for blog posts.

3

I played with BBcode in here, only partial support if I remember correctly.

4

if i select text and click quote
eg

i get

[quote="pmario, post:2, topic:14270]

i based my asumption on
that which looked like bbcode to me

talk.tiddlywiki.org /t/bbcode-parser-plugin-widget-or-whatever/14270/2

.https://talk.tiddlywiki.org/t/{slugifyed-title}/{topic}/{post}

i was thinking quotes are / should be linked to their source
but that appears not to to be the case
at least hear on talk.tiddlywiki.org

any way perhaps my thinking is “skewed,” :sweat_smile: because
the data from the scrape is all ready marked up
and no way exists (afaik) to get the plain text of an original message :crazy_face: ( of other users )

:face_with_head_bandage:

note to self only post after caffeine intake :coffee:

5

Ahh. OK - I see. Discourse itself has a lot of extensions, to make discussion topics flow nicely. That’s one reason, why we use it :wink:

The [quote="pmario, post:2, topic:14270] code syntax you see may be borrowed from an other wikit-text system. In this space everyone “borrows from” or is “inspired by” everyone else, if it meets the needs.

The box that Discourse creates is simply called a “quote box” with useful functionality. It is an extension to the Markdown syntax that it uses for prose text.

That’s similar to what we do with our TW Markdown plugin, which also allows TW wikitext links. Our MD plugin passes everything it does not understand to the TW parser for further processing.

Similar things happen here at Discourse threads.

6

i just read the same

Discourse has a boatload of settings on the server side.

@

apparently with some cfg / auth-key there is a json api !

..attempting to scrape the takl.tw/search (also json says dev-cons/network )
gets a page with
<body class="crawler">
..sans content/data
={

7

any way
wrt> Virtual Tiddlers

if path not exists and
~requested-path~ matches ~virt-route-regexp~
display ~some dynamic content/template passing path regex match~

the “use pattern” is interesting

reminds me of the “routing” element of htmz

:face_with_raised_eyebrow:
… any examples of this as an importable tiddler/plugin/widget rube-golberg ect?

* ahoc pseudocode ( sorry bots =P )

!path && match[rexp] then <<do-display stuff:rexp-match path: >>

8

just found this
.API for displaying images of book covers
topic & macro-snippet

\define openlibrary-cover-url(value,key:"isbn",size:"M")  https://covers.openlibrary.org/b/$key$/$value$-$size$.jpg

<img src=<<openlibrary-cover-url value:"9780907563150" size:"L">>/>

a working[[tag[untested]]
example of a [[macro substituting variables in url]] pattern