[twdev] Re: [TW5 Plugin] JsonMangler v2.2.3 Released!

[TonyM]

Joshua,

Thanks so much for building on this comprehensive solution. I have not yet 
made use of it much yet, but it is very important to tiddlywiki, because it 
opens many integration possibilities.

I stumbled on https://en.wikipedia.org/wiki/WordNet and 
https://wordnet.princeton.edu/ 
which I hope to find a JSON file.

WordNet® is a large lexical database of English. Nouns, verbs, adjectives 
and adverbs are grouped into sets of cognitive synonyms (synsets), each 
expressing a distinct concept. Synsets are interlinked by means of 
conceptual-semantic and lexical relations. The resulting network of 
meaningfully related words and concepts can be navigated with the browser(link 
is external) . WordNet is also 
freely and publicly available for download 
. WordNet's structure makes it a 
useful tool for computational linguistics and natural language processing.


   - This would allow in TiddlyWiki some natural language processing or 
   even a simple thesaurus. 
   - It could be added temporarily to a wiki or permanently.
   - It could be used to find unknown relationships by relying on the 
   relationships within the language itself.
  - Eg Synonyms or antonyms verbs adverbs etc... become part of the 
  relationship and link identification from texts.
   

Thanks again.

Regards
Tony

On Sunday, 27 September 2020 09:32:12 UTC+10, Joshua Fontany wrote:
>
> This release ads two new filter operators: "comparefield[]" and 
> "compareindex[]" operators that function as "compare[]" on a specific field 
> or index. The first prefix is now the field or index name. See the help 
> documentation in the example wiki.
>
> Requires TiddlyWiki v5.1.23-pre
>
> I now have a new domain that hosts all my wiki experiments. The demo wiki 
> for this plugin is now located at: 
> https://chronicles.wiki/TW5-JsonMangler/
>
> Download the node-folders at: 
> https://github.com/joshuafontany/TW5-JsonMangler/releases/tag/v2.2.3
>
> Best,
> Joshua Fontany
>

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/5dded6f6-81d9-4cbf-ac64-6bff573377b3o%40googlegroups.com.

[twdev] Re: Custom markup (continued 3)

[TonyM]

Mario,

Yes Very interesting.

Please keep this possibility alive, I agree the checklist plugin is great, 
and its very low complexity in wikitext one of its key advantages however I 
do like the ability to have a minimalist output or read only view of those 
we can build in custom wiki text


   - The Checkbox and map solutions are great.

I have published [RFC] Request for Comment and collaboration - Unique 
renamable Tiddlers and children with any name, a total Database? 

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 [prefix[$:/checkboxes/]suffix[a]]... 
perhaps checkboxes against children. 

   - Which can be renamed and have additional content. ie a checkbox item 
   can become a tiddler.

This will help!


   - Especially if I get help building widget(s) that can be used within 
   custom wiki text
   - Of course if you can find the time, I would like to collaborate with 
   you (and others) on this as well.

*I will continue with the evaluation of your new releases. *

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
   - 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.
   
*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.
   

FYI

   - I have discovered a number of powerful techniques on top of custom 
   Wikitext I have not had the time to share yet.



Regards
Tony

On Tuesday, 29 September 2020 23:48:38 UTC+10, PMario wrote:
>
> Hi folks, 
> I did just upload V 0.5.3 that contains 3 more very powerful parameters. 
> It lets us do the following: 
>
> \customize degree=☐ _element="$macrocall" $name="check" _1=tid 
>
> \define check(src, tid) 
> <$checkbox tiddler=<> tag=done class="db"> 
> <<__src__>> 
> \end
>
> °☐:a This is a test
> °☐:b This is a test 
> °☐:c This is a test 
>
> With the "old" mechanism only 1 state tiddler would have been created. 
> With this mechanism it is possible to add 2 new parameters to the macro. eg:
>
> °☐:a .. a is the text, that will be written to the tid parameter of the 
> "check" macro. 
>
>
> It's possible to have 2 new parameters. If there are more, it gets way to 
> complicated. IMO it will be much more readable to use the existing 
> mechanism. 
>
> \customize degree=☐ _element="$macrocall" $name="check" _1=tid _2=test
>
> \define check(src, tid, test) 
> <$checkbox tiddler=<> tag=done class="db"> 
> <<__src__>> - $test$ 
> \end
>
> °☐:a:noSpacesAllowed This is a test
>
> Since this
>
> °☐:a:noSpacesAllowed This is a test
>
> may be too much clutter it is possible to define a new _maps parameter eg: 
>
> \customize degree=☐ _element="$macrocall" $name="check" _1=tid _2=test 
> _maps=":a:noSpacesAllowed"   
>
> °☐ This is a test
>
> More info can be found in the examples. .. The _maps parameter can do some 
> cool stuff. 
> See: Examples in GG 
> 
>
> Have fun!
> 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 tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/16332238-3211-44d9-ad9a-31ea286a64b4o%40googlegroups.com.

[twdev] Re: Custom markup (continued 3)

[PMario]

I did add a bit more colour to the examples, to visualize the data-flow a 
bit better.
-m

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/9ec6cdaf-6513-4efb-9fb3-a03bc9cc45a3o%40googlegroups.com.

[twdev] Re: Custom markup (continued 3)

[PMario]

Hi,

I'm not 100% sure about the parameter names. So they may change. 

-m

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/52dea22b-ad9e-4cb0-bd01-f7a272ec2373o%40googlegroups.com.

[twdev] Re: Custom markup (continued 3)

[PMario]

Hi folks, 
I did just upload V 0.5.3 that contains 3 more very powerful parameters. It 
lets us do the following: 

\customize degree=☐ _element="$macrocall" $name="check" _1=tid 

\define check(src, tid) 
<$checkbox tiddler=<> tag=done class="db"> 
<<__src__>> 
\end

°☐:a This is a test
°☐:b This is a test 
°☐:c This is a test 

With the "old" mechanism only 1 state tiddler would have been created. With 
this mechanism it is possible to add 2 new parameters to the macro. eg:

°☐:a .. a is the text, that will be written to the tid parameter of the 
"check" macro. 


It's possible to have 2 new parameters. If there are more, it gets way to 
complicated. IMO it will be much more readable to use the existing 
mechanism. 

\customize degree=☐ _element="$macrocall" $name="check" _1=tid _2=test

\define check(src, tid, test) 
<$checkbox tiddler=<> tag=done class="db"> 
<<__src__>> - $test$ 
\end

°☐:a:noSpacesAllowed This is a test

Since this

°☐:a:noSpacesAllowed This is a test

may be too much clutter it is possible to define a new _maps parameter eg: 

\customize degree=☐ _element="$macrocall" $name="check" _1=tid _2=test 
_maps=":a:noSpacesAllowed"   

°☐ This is a test

More info can be found in the examples. .. The _maps parameter can do some 
cool stuff. 
See: Examples in GG 


Have fun!
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 tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/c0f711e0-f524-41f3-9edf-bf7fc5c1734co%40googlegroups.com.