On Wednesday, September 30, 2020 at 5:10:49 AM UTC+2, TonyM wrote:
I have published [RFC] Request for Comment and collaboration - Unique
> renamable Tiddlers and children with any name, a total Database?
> <https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/-8tzR8ikVyw>
> Just now, the features of which could be leveraged by custom wiki-text
> especially when looking for state and unique tiddlers;
> Eg; Rather than qualify use [<tsn>prefix[$:/checkboxes/]suffix[a]]...
> perhaps checkboxes against children.
>
The problem I have with TSNs as you described them is, that they are not
universal unique. .. But that's not only your problem. I do have the same
problem with aliases. ...
The DAT/HYPER infrastructure may be a solution here, since they use a UUID
as their address. eg:
hyper://<very-long-public-key>/recipes/{recipe-name}/tiddlers/{tiddler-name}
if the <very-long-public-key> is hashed and stored with the tiddler, it can
be used to identify tiddlers with the same name.
Question(s)?
>
> - Given "_params = class definitions" perhaps it could become _classes
> and _map becomes _params?
> - It would be easy/clearer to say the syntax is
> .class(s):param1:param2
>
> Yea, I did think about this myself. At first I wanted to use _params like:
=".a.b:a:b", but it gets really messy with longer names.
It will be a breaking change. So may be in 0.6.0, which should also use
angle instead of angel... which makes me sad a little bit :/
>
> - I have experimented to see If I can introduce custom definitions in
> the story list or view templates as I am keen to get at least a
> conditional
> global customise pragma.
> - I am not concerned, too much, how we achieve this, only that we
> document at least one method to do it, that does not demand \customise
> or
> something similar in the text field.
> - Transcludeing a tiddler of definitions should work, but if this
> could relate to a tag not unlike $:/tags/macro
> - For example if a tiddler has object-type[book-page] bring in a
> set of *custom wiki-text *and styles can be handled separately.
> - One day I hope to toggle custom-wiki text definitions such that
> one can render for a screen, newsletter or PDF print layouts using the
> same
> content and wikitext but alternate customise pragma.
>
> As I wrote earlier. I couldn't find a way to have global parser pragmas.
.. The problem is: Internally TW core creates a new Parser() for every
tiddler, similar to:
tiddler-parser = new Parser(type,text,options), which parses the tiddler
text. eg:
\define test()
test-parser=new Parser(type,text,options)
test
\end
some text
As you can see, there will be a new parser for the tiddler and a different
completely independent parser for the macro content. ... So as soon as a
template uses a macro, the settings from the "outer" parser are invisible
to the "inner" parser, because they use completely different memory.
The same is true for many widgets, that create several temporary parsers
... That's the reason why the \whitespace pragma has to be used per macro.
... I do have the same problem.
I couldn't find a way, to "climb up the memory ladder", to store parser
info persistently. Parsers are created and thrown away on demand. I'll have
a second look.
> *Review discovery;*
>
> - If I clone test-checkbox-widget-maps-transclusion and change the
> text in one of the checkboxes, I seem to get the same state tiddler as in
> the original (only on refresh), that state tiddler is listed by not
> honoured.
> - I was wondering about checkboxes that are internal vs global, one
> checklist could prefill another using different text marked elsewhere.
>
> Yea, the new tiddlers have 2 lists: Global stat tiddlers, which is the
default now and "local state" tiddlers, which are responsible for 1
tiddler.
> FYI
>
> - I have discovered a number of powerful techniques on top of custom
> Wikitext I have not had the time to share yet.
>
> I'm looking forward to see the tests.
-mario
--
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/3a8a79da-9b99-4e6c-9052-96770b3d5819o%40googlegroups.com.
