Re: [tw5] "I moved to Discourse" - add your name too?

['Werner' via TiddlyWiki]

Same here, also notoriously late to the show. Also just created an account 
on talk.tiddlywiki.org. Can only get better than GG.

Kind regards
Werner

j.te...@gmail.com schrieb am Sonntag, 29. August 2021 um 22:58:07 UTC+2:

> Hello all,
>
> As always, late to the party. Seems lots has happened while I was away.
> Good to hear an alternative to Google Groups in underway.
>
> Just signed up in: talk.tiddlywiki.org
>
> Stay safe, stay healthy everyone.
>
> Regards,
>
> Julio
>
> On Thursday, August 26, 2021 at 3:35:23 AM UTC-4 TW Tones wrote:
>
>> Ed,
>>
>> It is truly amazing given what you have gone through that you are here 
>> and keeping an interest and sharing your story. I believe strongly that 
>> TiddlyWiki is a tool towards democratising software for every one with 
>> different skills, ability, experience, capacities in different areas. If it 
>> is what I believe it to be, it must be able to support all our needs small 
>> or large. Everyone of our community members especially with different needs 
>> are valuable participants, because without you all we cant be exposed to 
>> the issues that arise, and our communities capacity diminishes.
>>
>> If we play our cards right tiddlywiki will enable far more than average 
>> Joes.
>>
>> Best wishes
>> Tony
>>  
>>
>>
>> On Thursday, 26 August 2021 at 16:18:17 UTC+10 eddi...@gmail.com wrote:
>>
>>> Hi Tony,
>>>
>>> I honestly didn't read your reply as a complaint but thought mine may 
>>> have sounded that way or offended someone. Misunderstandings and confusion 
>>> are now a cloud that surrounds not only me but all those who dare try to 
>>> interpret what I am attempting to express as well LOL and a good reason to 
>>> keep that picture handy! Anyway, after looking at discourse (I hadn't even 
>>> peeked) and seeing I can go there and find out what is happening from time 
>>> to time without even setting up an account and knowing Jeremy is behind 
>>> this, I see nothing to worry about. I like sticking to the core and 
>>> avoiding addons as much as possible anyway. 
>>>
>>> Thanks Jeremy for letting me know what's happening and you are behind 
>>> this. I am so sorry to hear you had to deal with this bug! We do not want 
>>> you in my shape, get or stay well whichever best applies! 
>>>
>>> So, If it helps? I have been pretty much just lurking since 2014 when 
>>> all this stuff happened to me anyway and regretfully right in the middle of 
>>> a group effort with many here to build an add on for TW5 that would fulfill 
>>> a very specific need in education and I see has now been done ( a moodle 
>>> extension using scorm or whatever they are calling it now)! I am so happy 
>>> to see that but feel I had to let down many and regretfully it's of little 
>>> use to me now (no longer able to teach). The purpose I had was to use on 
>>> very limited tablets, in correctional (prison) systems, to get around the 
>>> fact that they had no internet access, only a browser for email, but with 
>>> TW5 would be able to pull and receive data from a learning 
>>> management server on site which I had already established, allowing 
>>> the teacher and student to track progress etc. I do appreciate and 
>>> apologize to all here that were in that group when this happened; it did 
>>> present capabilities far beyond my use in a greater educational role as 
>>> well and we were all very excited about it at the time. My stroke and brain 
>>> tumor came out of nowhere (I can't even remember if I was able to let 
>>> anyone here know about it). My first surgery I came out OK but not right, 
>>> requiring a second that really did some damage but I am one of a very few 
>>> who have survived everything that happened to me I am told. I am still in a 
>>> fight trying to recover memories, and some of the very basic abilities I 
>>> had before like simply playing my guitar for relaxation (I was a 
>>> professional musician for decades before teaching full time). Administering 
>>> a network much less teaching others to do so is definitely never going to 
>>> be an option again (or working for that matter the cloud of confusion is 
>>> very real. Cognitive abilities tested and with everything else surrounding 
>>> this I am no longer able to work in any setting. I am now on 
>>> full disability just trying to write this is taking an eternity). We had an 
>>> awesome team but it serves as a great example of why not to get married to 
>>> any platform including Goole. Perhaps if our GG here can be exported that 
>>> would be wise? We were using something I think G+ or Google+ but whatever 
>>> it was is now gone and all that was communicated within it. I would hate to 
>>> see that happen here regardless of platform and know you guys 
>>> definitely know what's going on now better than I do.
>>>
>>> I read these condensed email updates weekly and then only occasionally 
>>> the full threads within them when I think there might be something I need 
>>> to know or I can use. I 

[tw5] Change the Map in Tiddlymap via Link?

['Matthias Werner' via TiddlyWiki]

Hello, I've some maps, is it possible to switch from one map to another via 
link in Tiddlymap?

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/87255094-6d0e-419d-af20-2d507727b9cfn%40googlegroups.com.

[tw5] Re: Please vote for your favour banner for v5.1.23

['Werner' via TiddlyWiki]

Great stuff, everyone. Voted!

BurningTreeC schrieb am Dienstag, 8. Dezember 2020 um 09:38:24 UTC+1:

> Nice banners everyone :) ! Voted!
>
> BTC
>
> TW Tones schrieb am Dienstag, 8. Dezember 2020 um 03:30:49 UTC+1:
>
>> They are all good! 
>>
>> On Tuesday, 8 December 2020 at 02:52:00 UTC+11 jeremy...@gmail.com wrote:
>>
>>> The voting to choose the banner for TiddlyWiki v5.1.23 is now open. 
>>> Please pick your favourite here:
>>>
>>>
>>> https://docs.google.com/forms/d/e/1FAIpQLSdODdlyb7RNvzk0pf1-aNAqgbS2LUURhte3EsVnhHPvoZRtrQ/viewform
>>>
>>> Thanks to everyone who entered the competition (see 
>>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ). 
>>> There’s a lot of creativity in the group, and I’mv grateful to have four 
>>> excellent designs to choose from.
>>>
>>> Best wishes
>>>
>>> Jeremy.
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ef306dba-6c1a-4c6b-81c9-fc11ba0953adn%40googlegroups.com.

[tw5] Re: Query: German Alternative Naming Of TW Might Be Germane

['Werner' via TiddlyWiki]

Just out of curiosity: how would it be spelled in Norwegian? BTW, there's 
actually a song in Norwegian on heavy rotation at our regional public radio 
station: Mopedbart by the HubbaBubba Club

TiddlyTweeter schrieb am Mittwoch, 25. November 2020 um 10:58:01 UTC+1:

> Werner wrote:
>
>> Eierlegende Wollmilchsau?
>>
>>
>> https://as1.ftcdn.net/jpg/00/36/38/70/500_F_36387075_1AdkFSD4FdbLTV8r4JDEeOSo1vjJTVqL.jpg
>>
>> Nails it pretty much, IMO, but somewhat hard to write for non-German 
>> speakers...
>>
>
> Lol! It works in Norwegian too.
>
> TT 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5b92d721-f97e-4e9d-a4d3-d6b8b2ad2e67n%40googlegroups.com.

[tw5] Re: Query: German Alternative Naming Of TW Might Be Germane

['Werner' via TiddlyWiki]

Eierlegende Wollmilchsau?

https://as1.ftcdn.net/jpg/00/36/38/70/500_F_36387075_1AdkFSD4FdbLTV8r4JDEeOSo1vjJTVqL.jpg

Nails it pretty much, IMO, but somewhat hard to write for non-German 
speakers...
thomas@gmail.com schrieb am Montag, 23. November 2020 um 22:15:53 UTC+1:

> TT, as a translator I would have to ask: Are you sure? Does that make 
> sense in English? – Let me suggest adaptations instead of translations.
>
> -- "a-program-that-changes-itself" (in German, one word?)
> ein selbst-anpassbares Programm (a program you can adapt yourself – as a 
> program it should not do anything that was not programmed into it)
>
> -- "a-self-filtering-webpage" (in German, one word?)
> eine Webseite mit Inhalts-Filterfunktionen (it is content you might want 
> to filter instead of the page)
>
> -- "a-20-year-wiki" (in German, one word?)
> ein Wiki mit Langzeit-Funktionsgarantie (20 years is a long time after all)
>
> See what I mean? 
>
> Cheers,
> Thomas
>
> TiddlyTweeter schrieb am Samstag, 14. November 2020 um 14:07:24 UTC+1:
>
>> Though I can't speak German I recognize its *superb ability to recombine 
>> words into new concepts*.
>>
>> Describing TiddlyWiki is not easy. Germans are common here and could 
>> likely provide neat one-word-concepts of ...
>>
>> -- "a-program-that-changes-itself" (in German, one word?)
>>
>> -- "a-self-filtering-webpage" (in German, one word?)
>>
>> -- "a-20-year-wiki" (in German, one word?)
>>
>>
>>and others ...
>>
>> IMO it would be useful.
>>
>> I use a lot the French word "Bricolage" (DIY activity plus serendipity) 
>> to describe use of TW in practice.
>> It is pretty accurate.
>> But German linguistic precision would be interesting to see too.
>>
>> Best wishes
>> TT
>>
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/026c791d-62a6-4a50-8fa4-b8053163f7b7n%40googlegroups.com.

Re: [tw5] A HOWTO: Working with tables in wikitext and marking where yer at

['Werner' via TiddlyWiki]

I found it easier resorting to plain HTML and using the CSS elements 
provided by Mohammad's great SHIRAZ plugin.

clutterstack schrieb am Dienstag, 13. Oktober 2020 um 02:04:06 UTC+2:

> I like the marker idea, Charlie. Markdown tables (or wikitext tables) are 
> such a pain to edit that I have been repeatedly quelling an urge to write 
> separate tiddlers for each row of the one I'm writing (documenting for 
> myself which macros do what, and where they live, in a personal plugin). 
> It's so tempting in TW to write a "solution," thereby opening yet another 
> set of parentheses before I finish the task at hand. Right now I'm jumping 
> around between cells, so every time I look for my place I have to put down 
> a new urge to institute a System. :)
>
> ...I actually broke down and wrote the tiddler to generate the table, and 
> one single data-containing tiddler, just to scratch the itch, and went back 
> to trying to maintain my discipline until the job is done. 
>
> Tables are an annoyance in any Markdown environment, but TiddlyWiki is 
> devilish in that you know you could write something on top of it to 
> generate the table you're making, and organize the data while you're at 
> it...
>
> On Saturday, October 10, 2020 at 1:23:38 PM UTC-4 Charlie Veniot wrote:
>
>> G'day,
>>
>> Normally I would entirely agree (I had also thought of using journals), 
>> but in this particular case (for a multi-tracking thing for two power banks 
>> and multiple tests), I wanted the one no fuss no muss tiddler with 
>> everything "right there" so to speak.
>>
>> Sometimes, when wanting to just do something quickly, extra layers of 
>> "fancy formality" overhead just gets in the way. 
>>
>> I prefer keep that good stuff "fancy formality" for when it really 
>> matters.
>>
>>
>> On Saturday, October 10, 2020 at 1:55:06 PM UTC-3, Atronoush wrote:
>>>
>>> Charlie,
>>>  Creating long tables is error prone and boring when you come back to 
>>> edit them. Why do not use a tiddler (look at tiddler philosophy)?
>>> In your case each row can be a tiddler. Every tiddler can have three 
>>> fields: text field, time field and data field
>>> Then simply use TiddlyTables or Shiraz dynamic table to create such a 
>>> long table.
>>>
>>> --Atro
>>>
>>>



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b146c9f9-e2f3-48b5-aafe-847f4a5e5248n%40googlegroups.com.

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

['Werner' via TiddlyWiki]

Oh, ok, I get it. So far, I have helped myself out with something like

<$list filter="[tag[theTag]type[application/json]search:text]">

but compareindex[] obviously provides a way through the front door. 

Great, thanks.
Werner



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1668487a-3691-46c6-8aab-2efb3ccd41c5n%40googlegroups.com.

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

['Werner' via TiddlyWiki]

Joshua, thanks for providing and caring for JsonMangler. Two stupid noob 
questions.

- couldn't "compareindex[]" be achieved with getindex[]compare[]? Or have I 
got something wrong?
- is something like  [[Test]compareindex::number:eq[3]]  legit? 
e.g. when I want to dynamically create the field name?

Thanks, Werner

joshua@gmail.com schrieb am Sonntag, 27. September 2020 um 01:32:15 
UTC+2:

> 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 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8939336d-4b7c-45ac-ab66-3fa2ad8754e7n%40googlegroups.com.

[tw5] Re: Number Format

['Werner' via TiddlyWiki]

Thanks, guys. Great starting point.

Werner

TW Tones schrieb am Samstag, 19. September 2020 um 10:53:45 UTC+2:

> Eric Beat me to it,
>
>  should have refreshed GG, His solution is superior of course and worthy 
> of the Core.
>
> However mine still demonstrates the extendibility of tiddlywiki with only 
> macros and wikitext.
>
> Regards
> Tones
>
> On Saturday, 19 September 2020 at 18:51:30 UTC+10 TW Tones wrote:
>
>> Werner,
>>
>> As you say, would be good in the core, but almost as good is a simple 
>> macro.
>>
>> See attached and import to any wiki, then open $:/PSaT/format-numbers 
>>  For instructions
>>
>> Syntax
>> <>
>>
>>- *n* is the number with or without decimal places (no default)*t* is 
>>the thousands separator (optional) - defaults to ","
>>   - (Can change default in format-number macro, set 
>>   thousands-separator)
>>- *d* is the decimal separator (optional) - defaults to "."
>>- (Can change default in format-number macro, set decimal-separator)
>>- *p* is the decimal places to use (optional) - defaults to "2"
>>- (Can change default in format-number macro, set decimal-places)
>>
>> For example <> results in 1, 
>> <#m_1244614928399698320_m_8478119421336035852_%2C>234, 
>> <#m_1244614928399698320_m_8478119421336035852_%2C>567, 
>> <#m_1244614928399698320_m_8478119421336035852_%2C>654, 
>> <#m_1244614928399698320_m_8478119421336035852_%2C>321.67 
>>  
>> *$:/PSaT/format-numbers/macro*
>> \define format-number(n t d p)
>> <$set name=thousands-separator value="$t$" emptyValue=",">
>> <$set name=decimal-separator value="$d$" emptyValue=".">
>> <$set name=decimal-places value="$p$" emptyValue="2">
>> <$set name=fixed-decimal value={{{ [[$n$]fixed] }}}>
>> <$set name=integer value={{{ [split[.]first[]] }}}>
>> <$set name=remainder value={{{ [split[.]last[]] }}}>
>> <$set name=length filter="[length[]]">
>> <$macrocall $name=each-digit length=<> /><$list 
>> filter="[!match[0]]" 
>> variable=nul><><>
>> 
>> \end
>> \define each-digit(length)
>> \whitespace trim
>> <$list filter="[range[1,$length$]]" variable=position>
>> <$set name=digit filter="[[$(integer)$]split[]nth]">
>> <$set name=zeros filter="[[$length$]subtract]">
>> <>{{{ 
>> [!match[0]remainder[3]match[0]then] }}}
>> 
>> 
>> \end
>>
>> *Regards*
>> *Tones*
>> On Friday, 18 September 2020 at 23:20:14 UTC+10 Werner wrote:
>>
>>> Tony, 
>>>
>>> sorry, was absorbed by other projects, so couldn't reply earlier. OK, 
>>> I'll be a bit more specific:
>>>
>>> I have a number stored in a JSON tiddler. When I retrieve it, I get 
>>> plain old 3500 for example. But I want decimal points and comma separators 
>>> to have it rendered like 3,500. Or 3.500 in German. Or whatever is your 
>>> default locale. And, if DateFormat is included in the view widget, I think 
>>> NumberFormat should also be. So I think, the most elegant solution would be 
>>> extending the view widget source code to allow for "number" and pass it 
>>> through to JavaScript intl.Numberformat (cf.: 
>>> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat).
>>>  
>>> Should not be that hard to implement. Maybe I try it, if I find the time.
>>>
>>> Of course there are plugins, but I think something as basic as a number 
>>> format should be in the core.
>>>
>>> Werner
>>>
>>> TW Tones schrieb am Dienstag, 8. September 2020 um 02:32:41 UTC+2:
>>>
 Post script

 Actualy i think using simple templates to display a number in a desired 
 format would be smart and the template can be changed to suit localisation 
 if not automaticaly respond to localisation. Macro access to templates is 
 also easy to provide.

 Tones

 On Tuesday, 8 September 2020 at 10:25:30 UTC+10 TW Tones wrote:

> Werner
>
> Perhaps some examples?
>
> Evans formulae plugin has features to support this from memory. There 
> are other maths plugins that may.
>
> I can imagin a gap that exists between basic maths and the more 
> advanced maths especialy in relation to display.
>
> However i can see these gaps would be easy to solve with a few wiki 
> text macros or taping into javascript functions that already handle it.
>
> Please research your percived gaps and post back some details.
>
> Tones
>
> On Tuesday, 8 September 2020 at 02:09:26 UTC+10 Werner wrote:
>
>> Guys,
>>
>> am I right that there is no TW-inherent way to display a number 
>> format or, better, locale-specific number format?
>>
>> Wouldn't it be great if it was integral part of the <$view> widget, 
>> much like date format is?
>>
>> Is there an easy fix? I mean, without having to install another 
>> plugin just for this purpose.
>>
>> Thanks, Werner
>>
>

-- 
You received this message because you are subscribed to the Google Groups 

[tw5] Re: Number Format

['Werner' via TiddlyWiki]

Tony, 

sorry, was absorbed by other projects, so couldn't reply earlier. OK, I'll 
be a bit more specific:

I have a number stored in a JSON tiddler. When I retrieve it, I get plain 
old 3500 for example. But I want decimal points and comma separators to 
have it rendered like 3,500. Or 3.500 in German. Or whatever is your 
default locale. And, if DateFormat is included in the view widget, I think 
NumberFormat should also be. So I think, the most elegant solution would be 
extending the view widget source code to allow for "number" and pass it 
through to JavaScript intl.Numberformat 
(cf.: 
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat).
 
Should not be that hard to implement. Maybe I try it, if I find the time.

Of course there are plugins, but I think something as basic as a number 
format should be in the core.

Werner

TW Tones schrieb am Dienstag, 8. September 2020 um 02:32:41 UTC+2:

> Post script
>
> Actualy i think using simple templates to display a number in a desired 
> format would be smart and the template can be changed to suit localisation 
> if not automaticaly respond to localisation. Macro access to templates is 
> also easy to provide.
>
> Tones
>
> On Tuesday, 8 September 2020 at 10:25:30 UTC+10 TW Tones wrote:
>
>> Werner
>>
>> Perhaps some examples?
>>
>> Evans formulae plugin has features to support this from memory. There are 
>> other maths plugins that may.
>>
>> I can imagin a gap that exists between basic maths and the more advanced 
>> maths especialy in relation to display.
>>
>> However i can see these gaps would be easy to solve with a few wiki text 
>> macros or taping into javascript functions that already handle it.
>>
>> Please research your percived gaps and post back some details.
>>
>> Tones
>>
>> On Tuesday, 8 September 2020 at 02:09:26 UTC+10 Werner wrote:
>>
>>> Guys,
>>>
>>> am I right that there is no TW-inherent way to display a number format 
>>> or, better, locale-specific number format?
>>>
>>> Wouldn't it be great if it was integral part of the <$view> widget, much 
>>> like date format is?
>>>
>>> Is there an easy fix? I mean, without having to install another plugin 
>>> just for this purpose.
>>>
>>> Thanks, Werner
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5b365ee0-6345-4e9c-8194-3f0fc036e7c8n%40googlegroups.com.

[tw5] Number Format

['Werner' via TiddlyWiki]

Guys,

am I right that there is no TW-inherent way to display a number format or, 
better, locale-specific number format?

Wouldn't it be great if it was integral part of the <$view> widget, much 
like date format is?

Is there an easy fix? I mean, without having to install another plugin just 
for this purpose.

Thanks, Werner

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d2b4ff2f-e40b-4729-83d3-7aed5542e47bn%40googlegroups.com.

[tw5] Re: Installing plugins via drag and drop in nodejs

['Werner' via TiddlyWiki]

Tony,

here's how I did it: 

- D installed the plugin in question. In my case, it was A. Aldrich's 
Tables plugin. 
- The result was two files in my tiddlers 
directory: $__plugins_aaldrich_tables.json 
and $__plugins_aaldrich_tables.json.meta. 
- Under my 
c:\\appdata\roaming\npm\node-modules\tiddlywiki\plugins 
directory, I now created two directories aaldrich and aaldrich\tables.
- Copied the .json file into the latter and renamed it to plugin.info. 
- Opened the json.meta file and copied the contents ahead of the "tiddlers" 
key in the plugin.info file. 
- Added proper JSON formatting (quotation marks and commas) to the new 
entries. If you have any wikitext plugin installed, you can use its 
plugin.info file as a template.
- Deleted the plugin from my wiki to get rid of the two above files
- Added the missing plugin information in tiddlywiki.info in my wiki's home 
directory. 
- Stopped and restarted the server. 

Voilà. 

Best, Werner

TW Tones schrieb am Samstag, 5. September 2020 um 08:33:37 UTC+2:

> Mark,
>
> Are there instructions anywhere to take an in wiki plugin and make it a 
> server plugin (file?).
>
> Regards
> Tones
>
>
> On Saturday, 5 September 2020 06:27:02 UTC+10, Mark S. wrote:
>>
>> Let me add, that there are two ways to add a plugin folder.
>>
>> The first is to add it to just a single wiki, in the plugins folder of 
>> your tiddly data folder.
>>
>> The second is to add it to your node.js master copy of tiddlywiki.
>>
>> The advantage of the first method is that the plugins will continue to be 
>> there as you upgrade, and it's pretty easy.
>>
>> The advantage of the second method is that once you have the plugins in 
>> place, they are available to all your wikis just by insert some lines into 
>> tiddlywiki.info.
>>
>> The disadvantage of the second method is that you have to find where your 
>> master copy of TW is (On Windows, the path to the default TW version is 
>> buried pretty deep.), and, possibly, your plugins won't survive when you 
>> upgrade (don't know for sure on this point.) Certainly if you relink to a 
>> different TW directory structure, your personal plugins aren't going to be 
>> there automatically. 
>>
>> On Thursday, September 3, 2020 at 4:56:07 PM UTC-7, TW Tones wrote:
>>>
>>> Mark,
>>>
>>> That is possibly the clearest description so far. We need to document 
>>> this a bit better.
>>>
>>> I admit I am no expert in this yet, and I hope if what I state is 
>>> incorrect someone will contradict me.
>>>
>>> I would add to your points, as I understand it, that if installed in 
>>> node apparently they are available to all wikis within Node such as under 
>>> Bob, but installed by Drag and drop they become tiddlers installed in the 
>>> specific wiki.
>>>
>>> You can see that except for the exceptions Mark mentions, drag and drop 
>>> can be an intentional approach to installing a different set of plugins in 
>>> different wikis.
>>>
>>> Despite this I am not sure what happens to to make correctly installed 
>>> server plugins visible in the wikis below.
>>>
>>> Regards
>>> Tony
>>>
>>>
>>> On Friday, 4 September 2020 00:56:10 UTC+10, Mark S. wrote:

 I think it means there some plugins meant for node.js that need to be 
 installed in a directory (maybe because they need to communicate directly 
 with the operating system).

 For most 3rd party plugins I think you're OK with d But if you have 
 a plugin that needs to directly communicate with the OS or over the 
 internet, then you will need to install local plugin directories.

 If you have official plugins, then you can "install" them just by 
 listing them in the tiddlywiki.info file. You do not want there to 
 also be a drag-and-drop plugin version of them because the d version 
 will 
 block the latest copy of the official version. The idea is that your 
 official plugins will automatically be upgraded on node.js when you 
 upgrade 
 your tiddlywiki installation on node.js.

 Having said that, if you're using code-mirror, and your drag-and-drop 
 version seems to be working, maybe just stick with it for the current 
 generation. It seemed to me that there was some internal inconsistency 
 with 
 the next gen of code-mirror. Whenever I tried to do the official install, 
 things broke. But that's just my thinking.


 Good luck!



 On Thursday, September 3, 2020 at 5:49:25 AM UTC-7, demon...@gmail.com 
 wrote:
>
> So I have my nodejs server up and running, but I did not want to start 
> an entirely new wiki, instead I wanted to import my old wiki and continue 
> using that. I imported it via just drag and dropping my .html file onto 
> the 
> newly made empty wiki. It imported everything just fine and everything 
> seems to work ok.
>
> However, I noticed that installing plugins in nodejs 
> 

[tw5] Re: Installing plugins via drag and drop in nodejs

['Werner' via TiddlyWiki]

>From my limited experience... while it is possible to install a plugin on 
Node.JS via D, and it seems to work properly, the plugin will only be 
available on the wiki it has been installed on. If you choose the more 
cumbersome way, as recommended for Node.JS, the plugin will be available on 
every wiki that is served from this Node.JS TW server. So, while the D 
installation will be fully sufficient, if the wiki concerned is the only 
one you intend to run, the Node.JS installation looks like the more 
sustainable method.

On a side note: it is possible to manually convert a plugin that is only 
available for D to a server-suitable version. At least, if it's a 
wikitext-only plugin. I have successfully done this for A. Aldrich's Tables 
plugin.

Best, Werner

demon...@gmail.com schrieb am Donnerstag, 3. September 2020 um 14:49:25 
UTC+2:

> So I have my nodejs server up and running, but I did not want to start an 
> entirely new wiki, instead I wanted to import my old wiki and continue 
> using that. I imported it via just drag and dropping my .html file onto the 
> newly made empty wiki. It imported everything just fine and everything 
> seems to work ok.
>
> However, I noticed that installing plugins in nodejs 
> server
>  
> should *not *be done by drag and dropping them as individual tiddlers but 
> instead you should make plugins folder in the server and put them there and 
> tell in the tiddlywiki.info file what plugins to load. It is said that:
>
> > Note that including a plugin as an ordinary tiddler (e.g. by dragging 
> and dropping a plugin into the browser) will result in the plugin only 
> being active in the browser, and not available under Node.js.
>
> So what does this *actually *mean? All my old plugins were installed this 
> way when I was not using nodejs. They still seem to work fine. Should I 
> remove all my plugins installed with drag and drop and install them 
> manually as per the link?
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4c65b5a6-ddd1-446a-aac1-48065e20209an%40googlegroups.com.

[tw5] Re: Variable scope question

['Werner' via TiddlyWiki]

OK, here's what worked for me. It took me a bit to figure it out, 
especially for making it work on a JSON tree, but it works.

\define makeRowspan()
 <$vars currentAction={{{ [all[current]indexes[Actions]sort[]first[]] }}} 
cnt="0" >
  <>
 
\end

define addRows() 
 <$set name="Items" filter=
"[all[current]indexes[Actions]addprefix[Actions/]addsuffix[/Items]]" select
=<> >
  <$set name="itemCount" value={{{ [all[current]indexescount[]] }}} >
   <$vars cnt={{{ [add] }}} >
<$list variable="currentAction" filter=
"[all[current]indexes[Actions]sort[]after]" emptyMessage=
"<>" >
 <>

   
  
 
\end

and then in the 

<$wikify name=rows text=<> >
> > 
...

Thanks so much, Saq and Tony, this took me a lot further on the learning 
curve. Without you, I would have never come across using first[] and 
after[].

Best, Werner



Am Donnerstag, 27. August 2020 19:56:38 UTC+2 schrieb Saq Imtiaz:
>
> @werner precisely, its a recursive macro that processes each row, and 
> calls the macro again with the next row, inside a new vars widget with the 
> new incremented value of the variable.
>
> The emptyMessage is triggered at the end and gives the final cumulative 
> value.
>
> On Thursday, August 27, 2020 at 6:36:01 PM UTC+2 Werner wrote:
>
>> Thanks, Saq, so this means you are using recursion? Didn't realize this 
>> was possible in TW. I will yet have to try it out and get back to you.
>>
>>
>> Am Mittwoch, 26. August 2020 22:41:16 UTC+2 schrieb Saq Imtiaz:
>>>
>>> I'm a bit tired so this isn't as clear as I would like, but hopefully 
>>> this pseudocode will point you in the correct direction for the pattern for 
>>> getting this done with just wikitext:
>>>
>>> \define processRow()
>>> nestedRows = level2 +count[]
>>> <$vars cnt={{{[add]}}}>
>>> <$list filter="[[allrows] +[after]]" 
>>> emptyMessage="<>">
>>> <>
>>> 
>>> 
>>> \end
>>>
>>> \define processAllRows()
>>> <$vars currentTiddler={{{[allrows] + first[]}}} cnt="0">
>>> <>
>>> 
>>> \end
>>>
>>> > > or set it to a variable for re-use.
>>>
>>> On Wednesday, August 26, 2020 at 9:16:30 PM UTC+2 Werner wrote:
>>>
 Good evening guys, me again.

 I understand that the scope of a variable is defined by the enclosing 
 <$vars> <$set> or <$wikify> widgets. I also understand that any new <$set> 
 widget opens up a new scope, where a variable  defined in an outer 
 scope would be overridden. I am facing a problem where I would need to 
 access out-of-scope variables (or come up with a completely different 
 approach).

 I am still working on a set of double-nested JSON data (using Josh 
 Fontany's JSONmangler plugin). I want to display the content of the data 
 in 
 a table using table cells spanning multiple rows like . 
 The problem here is, the rowspan is defined by the number of elements in 
 the lowest nested level and I would need it before rendering the table and 
 looping through the array elements fetching the data. So typically, in a 
 garden variety programming language, I would do something as follows:

 totalRows = 0
 Loop through Level1
nestedRows= Level2.count()
totalRows += nestedRows
 End Loop

 Could anybody enlighten me, if a construct like this is possible in TW 
 and how I would achieve it?

 Two fallback options: 
 - storing the number of elements in the JSON structure (yuck - feels 
 like cheating).
 - throwing the whole JSON data structure at an JS macro. Positive side 
 effect: I would have to dive into it and learn something new.

 Thanks for helping me out on this.
 Best, Werner







-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/25008790-0ef4-4215-971c-b44a53db2e42o%40googlegroups.com.

[tw5] Re: Variable scope question

['Werner' via TiddlyWiki]

Thanks, Tony, for pointing me at the range[] operator. Could you elaborate 
a bit on how you use it. So far I've gotten by using the <$list> widget, 
but your approach might be more efficient than mine.

Here's what I'm doing when looping through JSON data

<$set name="actions" filter="[all[current]indexes[Actions]sort[]]" > 
<$set name="actionCount" filter="[split[ ]count[]]" > 

<$list variable="currentAction" filter=<> >
...




Speaking of tables, is there anything to be aware of, as to how TW injects 
HTML tags? I can't seem to get  and  right in my dynamically 
created nested table. I have delegated some code to conditionally executed 
macros, and Chrome seems go get confused, when a  is used at a 
position it doesn't like.

Thanks again
Werner

Am Donnerstag, 27. August 2020 04:01:09 UTC+2 schrieb TW Tones:
>
> Werner,
>
> The exact detail needs to be worked out but I agree with Saq its all 
> doable in wikitext. I also use the HTML table tags rather than tiddlywiki 
> table markup. As long as you do not break the rules of html tables its easy 
> to have a variable number or rows or columns in a table if you wrap that 
> element in another and use a list to iterate the items. Boarders and 
> setting column title sis a little more tricky but doable
>
> Rather than rowspan you can iterate the cells but display: none; and other 
> methods.
>
> Also remember you can use the count widget or count operator to determine 
> how many items in a set and use the range operator to iterate them once you 
> know.
>
> Effectively you nest list widgets within table elements.
>
> Regards
> Tony
>
>
> On Thursday, 27 August 2020 05:16:30 UTC+10, Werner wrote:
>>
>> Good evening guys, me again.
>>
>> I understand that the scope of a variable is defined by the enclosing 
>> <$vars> <$set> or <$wikify> widgets. I also understand that any new <$set> 
>> widget opens up a new scope, where a variable  defined in an outer 
>> scope would be overridden. I am facing a problem where I would need to 
>> access out-of-scope variables (or come up with a completely different 
>> approach).
>>
>> I am still working on a set of double-nested JSON data (using Josh 
>> Fontany's JSONmangler plugin). I want to display the content of the data in 
>> a table using table cells spanning multiple rows like . 
>> The problem here is, the rowspan is defined by the number of elements in 
>> the lowest nested level and I would need it before rendering the table and 
>> looping through the array elements fetching the data. So typically, in a 
>> garden variety programming language, I would do something as follows:
>>
>> totalRows = 0
>> Loop through Level1
>>nestedRows= Level2.count()
>>totalRows += nestedRows
>> End Loop
>>
>> Could anybody enlighten me, if a construct like this is possible in TW 
>> and how I would achieve it?
>>
>> Two fallback options: 
>> - storing the number of elements in the JSON structure (yuck - feels like 
>> cheating).
>> - throwing the whole JSON data structure at an JS macro. Positive side 
>> effect: I would have to dive into it and learn something new.
>>
>> Thanks for helping me out on this.
>> Best, Werner
>>
>>
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/83a11d52-77b1-4183-b8c9-74e34107f65ao%40googlegroups.com.

[tw5] Re: Variable scope question

['Werner' via TiddlyWiki]

Thanks, Saq, so this means you are using recursion? Didn't realize this was 
possible in TW. I will yet have to try it out and get back to you.

Am Mittwoch, 26. August 2020 22:41:16 UTC+2 schrieb Saq Imtiaz:
>
> I'm a bit tired so this isn't as clear as I would like, but hopefully this 
> pseudocode will point you in the correct direction for the pattern for 
> getting this done with just wikitext:
>
> \define processRow()
> nestedRows = level2 +count[]
> <$vars cnt={{{[add]}}}>
> <$list filter="[[allrows] +[after]]" 
> emptyMessage="<>">
> <>
> 
> 
> \end
>
> \define processAllRows()
> <$vars currentTiddler={{{[allrows] + first[]}}} cnt="0">
> <>
> 
> \end
>
> > > or set it to a variable for re-use.
>
> On Wednesday, August 26, 2020 at 9:16:30 PM UTC+2 Werner wrote:
>
>> Good evening guys, me again.
>>
>> I understand that the scope of a variable is defined by the enclosing 
>> <$vars> <$set> or <$wikify> widgets. I also understand that any new <$set> 
>> widget opens up a new scope, where a variable  defined in an outer 
>> scope would be overridden. I am facing a problem where I would need to 
>> access out-of-scope variables (or come up with a completely different 
>> approach).
>>
>> I am still working on a set of double-nested JSON data (using Josh 
>> Fontany's JSONmangler plugin). I want to display the content of the data in 
>> a table using table cells spanning multiple rows like . 
>> The problem here is, the rowspan is defined by the number of elements in 
>> the lowest nested level and I would need it before rendering the table and 
>> looping through the array elements fetching the data. So typically, in a 
>> garden variety programming language, I would do something as follows:
>>
>> totalRows = 0
>> Loop through Level1
>>nestedRows= Level2.count()
>>totalRows += nestedRows
>> End Loop
>>
>> Could anybody enlighten me, if a construct like this is possible in TW 
>> and how I would achieve it?
>>
>> Two fallback options: 
>> - storing the number of elements in the JSON structure (yuck - feels like 
>> cheating).
>> - throwing the whole JSON data structure at an JS macro. Positive side 
>> effect: I would have to dive into it and learn something new.
>>
>> Thanks for helping me out on this.
>> Best, Werner
>>
>>
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dca174b6-9de4-44bf-95ec-0d0a286fbd08o%40googlegroups.com.

[tw5] Variable scope question

['Werner' via TiddlyWiki]

Good evening guys, me again.

I understand that the scope of a variable is defined by the enclosing 
<$vars> <$set> or <$wikify> widgets. I also understand that any new <$set> 
widget opens up a new scope, where a variable  defined in an outer 
scope would be overridden. I am facing a problem where I would need to 
access out-of-scope variables (or come up with a completely different 
approach).

I am still working on a set of double-nested JSON data (using Josh 
Fontany's JSONmangler plugin). I want to display the content of the data in 
a table using table cells spanning multiple rows like . 
The problem here is, the rowspan is defined by the number of elements in 
the lowest nested level and I would need it before rendering the table and 
looping through the array elements fetching the data. So typically, in a 
garden variety programming language, I would do something as follows:

totalRows = 0
Loop through Level1
   nestedRows= Level2.count()
   totalRows += nestedRows
End Loop

Could anybody enlighten me, if a construct like this is possible in TW and 
how I would achieve it?

Two fallback options: 
- storing the number of elements in the JSON structure (yuck - feels like 
cheating).
- throwing the whole JSON data structure at an JS macro. Positive side 
effect: I would have to dive into it and learn something new.

Thanks for helping me out on this.
Best, Werner





-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/efbb1542-9303-4eac-abde-143cbbf755can%40googlegroups.com.

[tw5] Re: Prior Art? Create tiddler in JSON file?

['Werner' via TiddlyWiki]

Tony, as you may recall, I've experimented a bit with Joshua Fontany's 
great JSONMangler plugin and (nested) JSON data tiddlers. I think, the 
plugin provides the tool you need.

But, after a bit of a learning curve, I found I was able to get it to work 
and to access and retrieve data. I am not fully happy, though.

The main issue I have is that JSON only offers minimum features. It stores 
data. Period. When you want to retrieve data, they come out in the way you 
have stored them, unless you want to mimic features in TW normally offered 
by a *DBMS. E.g. for retrieval in a given sort order, you will need to 
either use one of the sort functions on the whole data set or create an 
ISAM feature in TW. As I wrote before, this is a rabbit hole I would be 
reluctant to jump into. There has been work put into this topic by minds 
more proficient than me, So I'd rather resort to the work done by them. 
Also, I don't know, how JSON performs with large datasets, but I would 
assume at 800 records there won't be too much performance issues.

So, for the time being, I will stick to my TW-based solution, but in the 
long run I feel tempted to try out PouchDB/CouchDB which seems like the 
natural complement for this kind of problem.

Best, Werner

Am Mittwoch, 19. August 2020 04:42:56 UTC+2 schrieb TW Tones:
>
> Folks,
>
> Has anyone developed a method to create multiple tiddlers directly into a 
> JSON tiddler?
>
> *Background*
>
> I just built a macro to create color swatch tiddlers, more than 800.
>
>- I will share it soon, once I create some tools for color search and 
>copy tools
>- I did it Using a button containing a list and the 
>ActionCreateTiddlerWidget
>
> *What?*
>
> However I realised since the action create widget is basically handed a 
> set of field=values it should be easy enough to create such tiddlers in a 
> JSON file only as JSON tiddlers. 
>
>- It would need an append process
>
> I will eventually build this myself if there is no response however please 
> share any previous examples "Prior Art"  of doing this. It seems to me as 
> deserving of a facility in the core so perhaps others have done it better 
> than I can hope to.
>
> *Why?*
>
>- When creating large numbers of reference or data tiddlers they could 
>be created directly into a json file saving space ?, but permitting access 
>as shadow tiddlers. While keeping the number of real tiddlers small. 
>- It could allow an intermediate step from what you choose to make 
>into a real tiddler. Then delete the JSON when finished.
>- It would allow virtual tiddlers to be created from tiddlywiki 
>content that exist only in the JSON format. 
>- JSON's are readily converted to drag-able packages, import tiddlers 
>and plugins.
>- JSONS can be interrogated as shadow tiddlers or as data-tiddlers.
>
> Thanks in Advance
> Tones
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b734e1f6-38b5-43fa-b5d8-97df0dc2432co%40googlegroups.com.

[tw5] Re: Lost in transclusion

['Werner' via TiddlyWiki]

Thanks so much, Eric and Tony. As usal, this was extremely helpful. And 
<$wikify> actually solved the issue. 

In fact, I was assuming the transclusion chain had to do with it (hence the 
thread title), I am just not literate enough in TW to draw the right 
conclusions and find the remedies. But I keep on working at it.

Which brings me to another point: maybe I've overcomplicated things by 
storing a transclusion in a tiddler where a pointer to an array index in 
the JSON tiddler (i.e. a number) should have done the trick. But that's a 
different story.

So, thanks again, guys, much appreciated.

TW Tones schrieb am Mittwoch, 19. August 2020 um 01:47:32 UTC+2:

> Werner,
>
> I am confident Eric is spot on. It was the correct understanding of this 
> issue and the use of wikify that stopped me getting stuck regularly. I have 
> being trying to get some activity on this because it is a barrier to new 
> users. Perhaps this quick note will help as a rule until you fully 
> understand it.
>
>- If you need a value to be "evaluated" from wikitext to use within 
>subsequent Wikitext logic use the wikify widget at the last possible 
> moment.
>   - This guide suggests trying to use wikify in external macros is a 
>   path to disappointment
>- Make sure you close the wikify appropriately (as with all other 
>widgets) or unusual and broken result will occur
>- Its only at the final render of the tiddler that all things are 
>wikified automatically so a standalone `<>` appears to produce 
>the result you want, but as Eric said the result inside the wikitext 
>(before evaluation) without wikification it is not evaluated at that point.
>- It is fine to use the same name when wikifying to stop code 
>complexity
>
> \define macroname() blah blah
> <$wikify name=macroname text="<>">
>use <> here where it is the wikified version, or pre-
> evaluated
> 
>
> In closing
>
>- If some of our community developers see this what would be better is 
>something like the following;
>   - Allow any variable to be referenced in its "evaluated state" eg 
>   ((macroname)) would effectively wikify inline
>   - Automatically wikify/evaluate variables or macros when used in 
>   filters and other appropriate places.
>
> Regards
> Tones
>
>
> On Wednesday, August 19, 2020 at 7:15:51 AM UTC+10, Eric Shulman wrote:
>>
>> On Tuesday, August 18, 2020 at 10:06:59 AM UTC-7, Werner wrote:
>>>
>>> I am referring to a tiddler called activeDossier whose contents refers 
>>> to a JSON data tiddler. Tiddler content 
>>> is {{$:/data/CI/companyRegister##1/name}}.
>>>
>>> <$set name="theCompany" value={{$:/data/CI/activeDossier}}>
>>> !<$vars tv-wikilinks=no><> 
>>> <$list filter="[!is[system]search]" >
>>> <>
>>> 
>>>  
>>>
>>
>> The problem is that you are doing a "double transclusion".  That is, the 
>> value of <> retrieved via transclusion isn't the actual name of 
>> the company as text, but rather a secondary transclusion from a JSON 
>> tiddler (i.e., {{$:/data/CI/companyRegister##1/name}}).  When you render 
>> <>, TiddlyWiki automatically parses that transclusion and 
>> displays the actual value.  However, when you use search in the 
>> filter, the value isn't parsed any further, and you are literally searching 
>> for the transclusion syntax, not the actual company name as text.
>>
>> To resolve this, use <$wikify> instead of <$set> to fetch theCompany 
>> value, like this:
>> <$wikify name="theCompany" text={{$:/data/CI/activeDossier}}>
>> !<$vars tv-wikilinks=no><> 
>> <$list filter="[!is[system]search]" >
>> <>
>> 
>> 
>> The $wikify gets the value from the activeDossier tiddler AND then also 
>> parses that value, so the result is the desired text value from the 
>> underlying $:/data/CI/companyRegister tiddler.
>>
>> When you use it in the search filter, it's already fully 
>> resolved to be the actual company name as text, so the search should work 
>> as you intend.
>>
>> -e
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2a3567a4-b52a-4e8e-81a8-4f0bddec5aben%40googlegroups.com.

[tw5] Re: Lost in transclusion

['Werner' via TiddlyWiki]

Hi Mark, yes, as written to Mat, title and text will do. 

Mark S. schrieb am Dienstag, 18. August 2020 um 19:43:45 UTC+2:

> It looks like you want to search the text, title, or tag field for the 
> name of a company?? Is that what you want? If you want to search in some 
> non-default field, then you need to specify that field in your search.
>
>
> On Tuesday, August 18, 2020 at 10:06:59 AM UTC-7, Werner wrote:
>>
>> Once again, I am feeling like a complete dumbass when dealing with 
>> transclusion and substitution. Still having a hard time with it. OK, here's 
>> the code:
>>
>>
>> I am refering a tiddler called activeDossier whose contents refers to a 
>> JSON data tiddler. Tiddler content 
>> is {{$:/data/CI/companyRegister##1/name}}. What I basically want to do is 
>> auto-generating company dossiers, coming from various sources in my 
>> database. I have a list of companies as JSON from which I can select. This 
>> works up to the point below
>>  
>> <$set name="theCompany" value={{$:/data/CI/activeDossier}}>
>>
>> !<$vars tv-wikilinks=no><> 
>>
>> <$list filter="[!is[system]search]" >
>> <>
>> 
>>
>> 
>>
>> My problem is: the variable "theCompany" seems to be properly assigned, 
>> at least it gets displayed properly, so what am I doing wrong when I want 
>> to assign it to the list filter. I suspect, something along the 
>> transclusion chain is going wrong here, but I need someone to point me at 
>> it and how to find a remedy.
>>
>> Thanks to all helpful souls. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6f0a4d7b-0cb6-4118-a684-018a426c2324n%40googlegroups.com.

[tw5] Re: Lost in transclusion

['Werner' via TiddlyWiki]

Hi Mat, yes, I want to search globally. A pretty basic search on all text 
and title fields.

Mat schrieb am Dienstag, 18. August 2020 um 19:30:08 UTC+2:

> It might be as simple as needing to use triple quoting, in case your 
> theCompanies have quote characters in them.
>
> But note that the filter [!is[system]search] refers to all 
> tiddlers globally, not e.g the current tiddler if that is what you hope 
> for. IF you want to test if theCompany !is[system] you must do e.g 
> [!is[system]... etc.
>
> <:-)
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9dc49013-3b0c-4474-9430-1a49a00268fbn%40googlegroups.com.

[tw5] Lost in transclusion

['Werner' via TiddlyWiki]

Once again, I am feeling like a complete dumbass when dealing with 
transclusion and substitution. Still having a hard time with it. OK, here's 
the code:


I am refering a tiddler called activeDossier whose contents refers to a 
JSON data tiddler. Tiddler content 
is {{$:/data/CI/companyRegister##1/name}}. What I basically want to do is 
auto-generating company dossiers, coming from various sources in my 
database. I have a list of companies as JSON from which I can select. This 
works up to the point below
 
<$set name="theCompany" value={{$:/data/CI/activeDossier}}>

!<$vars tv-wikilinks=no><> 

<$list filter="[!is[system]search]" >
<>




My problem is: the variable "theCompany" seems to be properly assigned, at 
least it gets displayed properly, so what am I doing wrong when I want to 
assign it to the list filter. I suspect, something along the transclusion 
chain is going wrong here, but I need someone to point me at it and how to 
find a remedy.

Thanks to all helpful souls. 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9ed5e7b0-71d1-4211-96a1-f149ff014c80o%40googlegroups.com.

[tw5] Re: Temporarily getting rid of camel case

['Werner' via TiddlyWiki]

Tried the latter option. Works. Many thanks.

Am Montag, 17. August 2020 16:43:57 UTC+2 schrieb Eric Shulman:
>
> On Monday, August 17, 2020 at 6:45:32 AM UTC-7, Werner wrote:
>>
>> Eric, your solution only seems to work with static text, like
>> \rules except wikilink
>> CamelCaseText
>>
>> and not in a situation when the camel case text is generated 
>> programatically like transclusion.
>> Any clue would be greatly appreciated
>>
>
> ok... try this instead of the \rules
> \define tv-wikilinks() no
> This will suppress *all* links, even from transclusions (note: except for 
> external links, i.e., "http://...;)
> (see https://tiddlywiki.com/#tv-wikilinks%20Variable)
>
> Alternatively, you can write it this way:
> <$vars tv-wikilinks=no><$transclude tiddler="SomeTiddler" mode="block" 
> />
> This will only suppress the links for that specific transclusion, but 
> render all other links as usual
>
> -e
>
>
>
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/27eb424a-d48d-4b1b-9447-74f44abe082fo%40googlegroups.com.

[tw5] Re: Temporarily getting rid of camel case

['Werner' via TiddlyWiki]

Eric, your solution only seems to work with static text, like

\rules except wikilink
CamelCaseText

and not in a situation when the camel case text is generated 
programatically like transclusion.

as I wrote to TW Tones, normally I would resort to the text widget, but, so 
far, I haven't managed to properly assign the text parameter based on my 
dynamic content.

Any clue would be greatly appreciated
Werner


Am Freitag, 14. August 2020 19:43:33 UTC+2 schrieb Eric Shulman:
>
> On Friday, August 14, 2020 at 8:40:02 AM UTC-7, Werner wrote:
>>
>> Camel case is sort of an annoyance for me. I don't want to switch it off 
>> completely, but sometimes I don't want it while transcluding. Here's an 
>> example: I run a company database, and companies sometimes have camel case 
>> names.
>> ...when the company name is in camel case it gets auto-converted to a 
>> link. How do I get rid of this (without the global switch)? 
>>
>
> Add this "pragma" to the top of a tiddler:
> \rules except wikilink
> This will disable automatic CamelCase links only for content in that 
> tiddler.
>
> Notes:
> * There is also a "\rules only ..." pragma
> * To see the full list of rules that can be referenced, enter this in the 
> $:/AdvancedSearch, filter input:
> [[wikiparserrules[]]
>
> enjoy,
> -e
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/512c6258-5c7d-4d24-a84d-3cc52bab41aco%40googlegroups.com.

[tw5] Re: Temporarily getting rid of camel case

['Werner' via TiddlyWiki]

Hi Tones,

thanks. The text widget is usually the first thing I resort to in this 
case. I was not able getting transclusion to work though. 

Best, Werner

TW Tones schrieb am Samstag, 15. August 2020 um 02:50:48 UTC+2:

> Werner
>
> In some cases using the text widget will help produce a result which is 
> not evaluated as camelCase. The simple version of the link widget does this 
> to. So if a multiword title where one word is camel case that will not 
> become a link.
>
> Regards
> Tones
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e100f465-cd71-472a-9994-dbbc27024226n%40googlegroups.com.

[tw5] Re: Temporarily getting rid of camel case

['Werner' via TiddlyWiki]

Eric, you’re awesome. Thanks so much

Werner

Eric Shulman schrieb am Freitag, 14. August 2020 um 19:43:33 UTC+2:

> On Friday, August 14, 2020 at 8:40:02 AM UTC-7, Werner wrote:
>
>> Camel case is sort of an annoyance for me. I don't want to switch it off 
>> completely, but sometimes I don't want it while transcluding. Here's an 
>> example: I run a company database, and companies sometimes have camel case 
>> names.
>>
> ...when the company name is in camel case it gets auto-converted to a 
>> link. How do I get rid of this (without the global switch)? 
>>
>
> Add this "pragma" to the top of a tiddler:
> \rules except wikilink
> This will disable automatic CamelCase links only for content in that 
> tiddler.
>
> Notes:
> * There is also a "\rules only ..." pragma
> * To see the full list of rules that can be referenced, enter this in the 
> $:/AdvancedSearch, filter input:
> [[wikiparserrules[]]
>
> enjoy,
> -e
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4f650ad4-0aff-40e3-a57e-ada8d7071fcfn%40googlegroups.com.

[tw5] Temporarily getting rid of camel case

['Werner' via TiddlyWiki]

Camel case is sort of an annoyance for me. I don't want to switch it off 
completely, but sometimes I don't want it while transcluding. Here's an 
example: I run a company database, and companies sometimes have camel case 
names.

I dynamically create reports for companies which I have stored in a JSON 
tiddler. The currently active company is kept in a tiddler named 
activeDossier, its text field looks like {{companyRegister##0/name}}. I can 
transclude it into my dynamically created report, but when the company name 
is in camel case it gets auto-converted to a link. How do I get rid of this 
(without the global switch)? 

Apart from that, an additional parameter for the <$transclude> widget 
eliminating camel case would be great.

Thanks
Werner

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/63e6aa52-4a86-4460-8e08-c8612d98f116o%40googlegroups.com.

[tw5] Re: Curious Observation great date hack?, title field synonymous with currentTiddler & optional challenge.

['Werner' via TiddlyWiki]

Tony,

I tried it and also came upon that it just SEEMS to work. Consider this 
slight change to your code, and you will find out why:

<$list filter="[range[20210215,20210315,1]]">
<$view field=title format="number" />
<$view field=title format="date" template="-0MM-0DD"/>


So, the starting and end points in the range are interpreted as numbers and 
count up correctly (number-wise). So after 20210228, there'll be 20210229 
which the date formatter seems to interpret as 20210301. This goes on until 
20210299 and 20210300 which, again, is interpreted as 20120228. Then the 
count-up continues until 20210315. 

So, nice catch, but unfortunately doesn't work.

Best,
Werner

Am Freitag, 31. Juli 2020 12:35:48 UTC+2 schrieb TW Tones:
>
> The formatted date example given is not working. I am not sure why yet.
>
> Regards
> Tony
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a6d6b944-06d6-49b7-89d1-a214ea0c1eaao%40googlegroups.com.

[tw5] Re: Please educate me on _canonical_uri paths

['Werner' via TiddlyWiki]

Saq,

that was quick. I actually read the link you gave, but obviously wasn't 
able to make sense of it. Works. Thanks. Problem solved.

Kind regards
Werner


Am Freitag, 31. Juli 2020 11:37:12 UTC+2 schrieb Saq Imtiaz:
>
> You can set a canonical uri to any file path, but you also need a 
> webserver to serve the static file at that file path.
>
> TiddlyWiki on node has a built-in static file server that serves all 
> static files located in the files folder in the wiki folder, that is 
> parallel to the tiddlers folder:
>
> https://tiddlywiki.com/#Using%20the%20integrated%20static%20file%20server
>
> So you could create a logos subfolder in the files folder.
>
> On Friday, July 31, 2020 at 11:22:18 AM UTC+2, Werner wrote:
>>
>> Good morning,
>>
>> did some extensive research on it already, but seem too dumb to get it. 
>> Ok, here's the deal: Running TW on node.js and Windows 10. Did a normal NPM 
>> install, so tiddlywiki.cmd resides in C:\Users\\AppData\Roaming\npm. 
>> OTOH, I have a wiki in C:\Users\de00735\OneDrive - 
>> Company\Biologics\_Wiki\Repository. That's the path where my 
>> tiddlywiki.info sits, unfortunately with two blanks in it.
>>
>> I have a lot of png logos that, so far, I have imported using the regular 
>> import mechanism, i.e., in the tiddlers directory, it creates a tiddler, a 
>> tiddler.meta file and puts the associated.png into the directory too. So 
>> far so good.
>>
>> I thought, for OCD reasons, it might be a good idea putting all the logos 
>> into a separate directory which I wanted to call "logos". Unfortunately, 
>> any attempt to enter a _canonical_uri pointing at that directory failed. I 
>> initially assumed the directory where tiddlywiki.info sits as the root 
>> directory giving the _canonical_uri path the value ./tiddlers/logos, but no 
>> avail. Other attempts, like using the TW install directory as root 
>> directory and pointing at the logos directory using ../../../OneDrive - 
>> (etc) also failed.
>>
>> So, could any kind soul enlighten me on where I went wrong. Thanks so 
>> much in advance.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6c2f986f-6670-424b-b0c7-41d2ff1b6934o%40googlegroups.com.

[tw5] Please educate me on _canonical_uri paths

['Werner' via TiddlyWiki]

Good morning,

did some extensive research on it already, but seem too dumb to get it. Ok, 
here's the deal: Running TW on node.js and Windows 10. Did a normal NPM 
install, so tiddlywiki.cmd resides in C:\Users\\AppData\Roaming\npm. 
OTOH, I have a wiki in C:\Users\de00735\OneDrive - 
Company\Biologics\_Wiki\Repository. That's the path where my 
tiddlywiki.info sits, unfortunately with two blanks in it.

I have a lot of png logos that, so far, I have imported using the regular 
import mechanism, i.e., in the tiddlers directory, it creates a tiddler, a 
tiddler.meta file and puts the associated.png into the directory too. So 
far so good.

I thought, for OCD reasons, it might be a good idea putting all the logos 
into a separate directory which I wanted to call "logos". Unfortunately, 
any attempt to enter a _canonical_uri pointing at that directory failed. I 
initially assumed the directory where tiddlywiki.info sits as the root 
directory giving the _canonical_uri path the value ./tiddlers/logos, but no 
avail. Other attempts, like using the TW install directory as root 
directory and pointing at the logos directory using ../../../OneDrive - 
(etc) also failed.

So, could any kind soul enlighten me on where I went wrong. Thanks so much 
in advance.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b267364c-83f4-45ec-954c-8482637d7bffo%40googlegroups.com.

[tw5] Re: JSONMangler and nested JSON

['Werner' via TiddlyWiki]

OK, it took me quite a bit to get my head wrapped around, but I've come up 
with a solution that works for me. In order to dive into the nested array 
and access the indexes in there, I had to resort to a macro renderIndex(), 
but, as a positive side effect, this makes the code more readable. So 
here's the example code. Feel free to comment if I unnecessarily 
complicated it. Also, I still need to come up with a solution to add up 
fields with numeric content in a JSON array. Input here would be greatly 
appreciated



\define renderIndex(path: "0" index: "") 
<$set name="myFld2" tiddler="$(currentTiddler)$" index="$path$/$index$" > 
Displaying $path$/$index$: <>

\end

<$list filter="[tag[Facility]]">

<$view field="title"/>

Actions array Length:
<$set name="arrLength" filter="[indexes[/Actions]count[]]">
Array Length: <>
  

Actions array Full Content as JSON string:
<$set name="myVar" tiddler=<> index="/Actions">
<>


Looping through Actions array:
<$list variable="arrayIndex" filter="[indexes[/Actions]]">

<$set name="myFld", 
filter="[indexes[/Actions]addprefix[/Actions/]]" 
select=<> > 
Displaying contents of <> as JSON string:
<$transclude tiddler=<> index=<> />

<$macrocall $name="renderIndex" path=<> index="Action Date" />
<$macrocall $name="renderIndex" path=<> index="Action Type" />






So, Joshua and Tony, thanks so much for helping me on the way. Was quite a 
bit of a learning curve, but I enjoyed it.

Best, Werner

Am Montag, 13. Juli 2020 01:34:00 UTC+2 schrieb Joshua Fontany:
>
> I think you are almost there. One thing to keep in mind in Tiddlkywiki is 
> the difference between "shorthand" Wikitext and "long form" Widgets.
>
> {{Title##Index}} is "shorthand" Wikitest that is then rendered into the 
> following by the TW core:
> ```
> <$tiddler tiddler="Title">
>   <$transclude tiddler=<> index="Index" />
> 
> ```
> As you can see, leaving out the first part, like so {{##Index}} would 
> retain the value of the "current" <> variable and just use 
> the <$transclude> widget to pull an Index. Similarly, if you leave out the 
> "variable" parameter of a $list widget, it assumes you want to set the 
> <> variable in each rendered tempalte. This is equivalent 
> to your "each()" request. (Make sure to have an empty line after the 
> opening <$list> tag if you want block fomatting.)
>
> The next thing to note is that with JsonMangler you always want to use 
> full paths to any nested data. Always consider the Tiddler as the object, 
> and path from the root to the required data. Your list would look like so:
> ```
> <$list filter="[tag[Facility]]">
>
> <$set name="arrLength" filter="[indexes[/Actions]count[]]">
> Facility Array Length: <>
> <$list variable="arrItemPath" 
> filter="[indexes[/Actions]addprefix[/Actions]]" >
>
> <>:  <$transclude tiddler=<> 
> index=<> />
>  
> 
> ```
>
> Best,
> Joshua Fontany
> On Sunday, July 12, 2020 at 7:11:12 AM UTC-7 Werner wrote:
>
>> Hi Joshua,
>>
>> thanks so much for your answer. This has taken me a lot further.
>>
>> But, reconsidering my original question, I found, that, maybe, I got 
>> stuck too much in the procedural paradigm, and a more elegant approach 
>> would be, if one could could use each[] for looping through a JSON array. 
>> Taking your example this should look something like:
>>
>> <$list filter="[[MyJson]indexes[/path/to/array]each[]]">
>> {{##FieldFromJsonArray}}
>> 
>>
>> I tried to do it, but didn't succeed. I understand that each[] expects a 
>> list separated with spaces, so my assumption would be that this does not 
>> work unless an overloaded version of each[] is provided. OTOH, I found an 
>> undocumented function ForEach[] in JSONMANGLER. Any clue?
>>
>> I created three JSON test tiddlers. One with a nested array of 4 elements 
>> and another with 3 and a third one with a one-element array. I looped 
>> through them like this
>>
>> <$list filter="[tag[Facility]]">
>> ...
>> <$set name="arrLength" filter="[indexes[/Actions]count[]]">
>> Array Length: <>
>>  
>> 
>>
>> and was able to display all fields and the array fields as JSON text. 
>> Strangely, the arrLength variable displayed a value of 4 for all three 
>> tiddlers. No idea why. Will have to dive deeper into it.
>>
>> Thanks again
>> Werner
>>
>>
>>
>> Am Samstag, 11. Juli 2020 21:24:07 UTC+2 schrieb Joshua Fontany:
>>>
>>> Hi,
>>>
>>> Great to see people experimenting with my tools. 
>>>
>>> Two things to note. 1) 0-index based arrays can always have a new object 
>>> written to an index equal to the length of the array. Example, "[0,1,2]", I 
>>> can push "3" to {{MyJson##3}}, and it will be "[0,1,2,3]". Neat trick. 2) 
>>> You can count an array's length using filters as long as you know the 
>>> position of the array within the nexted JSON structure, like so:
>>> ```
>>> <$var name="arrLength" filter="[[MyJson]indexes[/path/to/array]count[]]">
>>> Array Length: <>
>>>   
>>> ```
>>>
>>> Combine the two techniques like so (note the final slash on the new path 
>>> 

[tw5] Re: JSONMangler and nested JSON

['Werner' via TiddlyWiki]

Hi Joshua,

thanks so much for your answer. This has taken me a lot further.

But, reconsidering my original question, I found, that, maybe, I got stuck 
too much in the procedural paradigm, and a more elegant approach would be, 
if one could could use each[] for looping through a JSON array. Taking your 
example this should look something like:

<$list filter="[[MyJson]indexes[/path/to/array]each[]]">
{{##FieldFromJsonArray}}


I tried to do it, but didn't succeed. I understand that each[] expects a 
list separated with spaces, so my assumption would be that this does not 
work unless an overloaded version of each[] is provided. OTOH, I found an 
undocumented function ForEach[] in JSONMANGLER. Any clue?

I created three JSON test tiddlers. One with a nested array of 4 elements 
and another with 3 and a third one with a one-element array. I looped 
through them like this

<$list filter="[tag[Facility]]">
...
<$set name="arrLength" filter="[indexes[/Actions]count[]]">
Array Length: <>
 


and was able to display all fields and the array fields as JSON text. 
Strangely, the arrLength variable displayed a value of 4 for all three 
tiddlers. No idea why. Will have to dive deeper into it.

Thanks again
Werner



Am Samstag, 11. Juli 2020 21:24:07 UTC+2 schrieb Joshua Fontany:
>
> Hi,
>
> Great to see people experimenting with my tools. 
>
> Two things to note. 1) 0-index based arrays can always have a new object 
> written to an index equal to the length of the array. Example, "[0,1,2]", I 
> can push "3" to {{MyJson##3}}, and it will be "[0,1,2,3]". Neat trick. 2) 
> You can count an array's length using filters as long as you know the 
> position of the array within the nexted JSON structure, like so:
> ```
> <$var name="arrLength" filter="[[MyJson]indexes[/path/to/array]count[]]">
> Array Length: <>
>   
> ```
>
> Combine the two techniques like so (note the final slash on the new path 
> gets added on as a prefix before adding the path to the array):
> ```
> <$var name="arrLength" filter="[[MyJson]indexes[/path/to/array]count[]]">
> <$var name="newIndex" 
> filter="[addprefix[/]addprefix[/path/to/array]]">  
> <$button setTitle="MyJson" setIndex=<> setTo="New Data" />
> 
>  
> ``` 
> You could use the form `setTo={{New Data Tiddler}}` to grab the new data 
> from the text-field of the "New Data Tiddler", etc, etc.
>
> Best,
> Joshua Fontany
> On Friday, July 10, 2020 at 1:14:52 AM UTC-7 Werner wrote:
>
>> Hi Tony,
>>
>> thanks for taking your time and your extensive reply. Perhaps I've made 
>> it too complicated. Ok, I try to reformulate it. Disclaimer also: I work in 
>> a corporate environment, so I'm not completely free in the tools I am 
>> allowed to use (to my surprise, Node.js is ok - ye!) and how much 
>> information I can disclose.
>>
>> Let's put it that way: I have set up an internal information repository 
>> which contains more or less textual information only so far. But now and 
>> then, I would like to display some figures. And I would have to perform 
>> some simple arithmetics with that figures (basically summing up).
>>
>> Let's call the things I am looking at "facilities". A "facility" should 
>> be displayed in a templated tiddler, displaying textual and quantitative 
>> information. Each "facility" can feature several "units" (that's the 1:n 
>> relation), figures for which should also be displayed and/or shown as a 
>> grand total. 
>>
>> The data for the facility/unit information should initially come from an 
>> Excel table. For further use (the CRUD part), I would like to create a 
>> TW-based interface. As "facility" is a comprehensive entity for my 
>> purposes, I thought it would be ok to store it in a nested JSON tiddler, 
>> i.e. store the units per facility in a JSON array. This, of course, breaks 
>> the RDBMS dogma, but it saves me from having to fiddle with primary keys. 
>> Mimicking a RDBMS in TW is definitely not a rabbit hole I want to jump 
>> into. If I needed something like that, I would try if I could connect a DB 
>> backend via Node.js (in my special environment I would end up with SQLite 
>> or ODBC), and let this do the grunt work. 
>>
>> All this being said, here's the core of my question: Accessing nested 
>> JSON data using Joshua Fontenay's JSONMANGLER plugin works great, as long 
>> as the index position is known, but I need a way to determine the length of 
>> a variable-length array in a JSON structure, for not running out-of-bounds 
>> while looping into the nested data. I understand $:/History is such a 
>> variable-length array, and thanks for pointing me at this. In that case, 
>> maybe I need to look up how data are retrieved from there. I know, as a 
>> workaround, I still could store the number of units as a data field in the 
>> JSON structure, but then I would have to take care of it programatically, 
>> which I want to avoid.
>>
>> Thanks again and apologies for any confusion I caused
>> Werner
>>
>>
>> TW Tones schrieb am Freitag, 10. 

[tw5] Re: JSONMangler and nested JSON

['Werner' via TiddlyWiki]

Hi Tony,

thanks for taking your time and your extensive reply. Perhaps I've made it 
too complicated. Ok, I try to reformulate it. Disclaimer also: I work in a 
corporate environment, so I'm not completely free in the tools I am allowed 
to use (to my surprise, Node.js is ok - ye!) and how much information I 
can disclose.

Let's put it that way: I have set up an internal information repository 
which contains more or less textual information only so far. But now and 
then, I would like to display some figures. And I would have to perform 
some simple arithmetics with that figures (basically summing up).

Let's call the things I am looking at "facilities". A "facility" should be 
displayed in a templated tiddler, displaying textual and quantitative 
information. Each "facility" can feature several "units" (that's the 1:n 
relation), figures for which should also be displayed and/or shown as a 
grand total. 

The data for the facility/unit information should initially come from an 
Excel table. For further use (the CRUD part), I would like to create a 
TW-based interface. As "facility" is a comprehensive entity for my 
purposes, I thought it would be ok to store it in a nested JSON tiddler, 
i.e. store the units per facility in a JSON array. This, of course, breaks 
the RDBMS dogma, but it saves me from having to fiddle with primary keys. 
Mimicking a RDBMS in TW is definitely not a rabbit hole I want to jump 
into. If I needed something like that, I would try if I could connect a DB 
backend via Node.js (in my special environment I would end up with SQLite 
or ODBC), and let this do the grunt work. 

All this being said, here's the core of my question: Accessing nested JSON 
data using Joshua Fontenay's JSONMANGLER plugin works great, as long as the 
index position is known, but I need a way to determine the length of a 
variable-length array in a JSON structure, for not running out-of-bounds 
while looping into the nested data. I understand $:/History is such a 
variable-length array, and thanks for pointing me at this. In that case, 
maybe I need to look up how data are retrieved from there. I know, as a 
workaround, I still could store the number of units as a data field in the 
JSON structure, but then I would have to take care of it programatically, 
which I want to avoid.

Thanks again and apologies for any confusion I caused
Werner

TW Tones schrieb am Freitag, 10. Juli 2020 um 01:19:01 UTC+2:

> Werner,
>
> Despite clearly having a lot in common with an understanding of databases 
> I don't completely follow you need or argument here. However I believe I 
> can offer you some helpful leads.
>
> One part that confuses me is your 1:n or one to many, I have already build 
> one to one, one to many and many to many half a dozen ways without a data 
> tiddler in tiddlywiki. What is the particular issue here?
>
> First look at tiddlywikis existing functionality.
>
>- The history mechanism stores tiddler titles and more during a 
>session in the $:/historyList this may be an analogue
>- The Import and export mechanism extract and package tiddlers as json 
>representations
>- Mohammad's Trash Plugin moves deleted tiddlers into another 
>structure to keep them aside, I think it is JSON as well.
>- In my demo site here 
> the active 
>tiddler process extracts titles from the history list using splitregexp 
> not 
>standard JSON as the key is not unique
>
> However It would not necessarily be too concerned about using tiddlers 
> unless your number will be truly astounding in numbers. We had a 66,000 
> word tiddler example in the last year and that was single file.
>
> Speculation
>
> If you packed more static tiddlers (eg a reference table)  into a plugin 
> and access them as shadow tiddlers you are effectively packing them into a 
> json file and allow yourself to edit exceptions and the database becomes 
> the combination of the packaged and overwritten providing a lot of 
> flexibility to your design. In effect you CRUD will make use of standard 
> tiddlywiki features, just treat the records like standard tiddlers. The D 
> or delete of CRUD could get smart (adding and removing from JSON) or you 
> could simply flag deleted tiddlers as such and treat them as deleted with 
> an occasional rebuild recommended after N tiddlers are flagged as deleted.
>
> I can already foresee a lot of sophisticated features being possible 
> including tracing and logs, difference engines, database snapshot at a 
> point in time and more. I have recently designed an alternative to shadow 
> tiddlers I call ghost tiddlers that may also be a useful algorithm.
>
> Offer
> I as a tiddlywiki superuser, I am investing totally in the TiddlyWiki 
> platform, if you are interested in collaboration to build a database model 
> process, making full use tiddlywiki's unique features I think it will be a 
> good investment in the future.
>
> 

[tw5] JSONMangler and nested JSON

['Werner' via TiddlyWiki]

Dear all, heavy user and rare poster here. Using TW has become a daily 
treat for me, but I have managed to still stay at the surface so far. Now, 
I have to dive in deeper.

I have been using TW so far to store semi-structured information, but now I 
need to integrate structured information, i.e. a database featuring an 1:n 
relation. 

I thought it might be a good idea using JSON. I also thought, for my 
purposes, I don't want to mimic an RDBMS in TW with all the primary key 
hassles and a deluge of .TID files (I am running TW on Node.js), so I 
wanted to use a JSON tiddler for the entities and use arrays in JSON for 
sub-entities. 

I came across Joshua Fontenay's JSONMangler plugin (Kudos, Josh!) and so 
far so good.

BUT

Eventually I want to implement CRUD (create-retrieve-update-delete) 
functionalities for this special data. And I want to display the 1:n 
relation in a single tiddler. And this is where I'm stuck at the moment:

- how to get the total number of array items in a JSON array in order to be 
able to display the 1:n 

apart from the variable array length, the JSON structure is fix, so 
everything else should be fairly straightforward. OK, there are some 
numeric fields in the array I need to sum up, but one thing after the 
other...

Any insight would be greatly appreciated

Best,
Werner


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/da6d99bc-43b7-4b30-a349-3aa750c76a1cn%40googlegroups.com.

[tw5] Re: TiddlyWiki vs OneNote (comparison on slant.co)

['Werner' via TiddlyWiki]

Am Mittwoch, 31. Juli 2019 08:06:43 UTC+2 schrieb TonyM:
>
> Werner
>
> Thanks for sharing. A few quick notes;
>
> I don't think one notes functionality is diminishing in office 365 in some 
> ways its stronger than ever in the o365 platform. I stand to be corrected.
>
> One note is an application, a single app, be it designed to support cross 
> application notes or not, and a propriatary one at that. Where tiddlywiki 
> is a platform on which much more can be done in the long run.
>
> Since learning tw5 I never think about one note at all.
>
> Regards
> Tony
>

Hi Tony,

tried to track down where I got my information from. It's from mid-2018, so 
things might have changed/improved in the meantime. My understanding is 
that there is basically a function freeze with ON 2016. There is no ON in 
Office 2019 and Office 365 (but ON 2016 still works). Instead, current ON 
users are nudged to using the ON app coming with Windows 10, which (at that 
time) lacked some functionalities present in ON 2016. It seems that 
Microsoft has addressed quite a few original issues, so they seem to be 
basically doing their homework (don't nail me down on this, I'm not playing 
Microsoft's advocate). 

You will find all the information available starting from here: 
https://support.office.com/en-us/article/onenote-2016-is-missing-after-installing-office-2019-or-office-365-1844ba87-7248-4bd8-a735-66a52f98e6e5

The biggest issue for me is that ON does no longer support local notebook 
files. You will be bound to OneDrive. You may convert your local notebooks 
to OneDrive, but it's a one-way street. Some people may not bother, but I 
do. So, that's it for me.

Oh, BTW, there's one ON feature I am missing with TW: Searchable PDFs. 
Importing a PDF and having the text auto-imported into a Tiddler would be 
awesome. But maybe I've just missed out on something

Best
Werner

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7d3204d1-d59e-4ced-91c1-e1c4f72e5196%40googlegroups.com.

[tw5] Re: TiddlyWiki vs OneNote (comparison on slant.co)

['Werner' via TiddlyWiki]

Am Dienstag, 30. Juli 2019 14:32:11 UTC+2 schrieb Mat:
>
> Werner wrote:
>  
>
>> To be fair, the search function in ON is great.
>>
>
> What makes it great?
>
> <:-) 
>

Just wanted to be fair and not seem to be bashing OneNote. It's fast and it 
spans over multiple notebooks which I found useful :-) 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fa231840-9b39-4b62-abdb-152984fcc45e%40googlegroups.com.

[tw5] Re: TiddlyWiki vs OneNote (comparison on slant.co)

['Werner' via TiddlyWiki]

Am Montag, 22. Juli 2019 04:57:41 UTC+2 schrieb Mark S.:
>
> I came across this accidentally. Maybe everyone else is familiar with it?
>
>
> https://www.slant.co/versus/2130/5116/~microsoft-onenote_vs_tiddlywik
>
> I found the "con" that said "Without JavaScript nothing is visible" to be 
> incredibly silly. Like "without electricity light bulbs are useless."
>
> On the other hand, ON had a much longer list of cons.
>


I have come from OneNote to TiddlyWiki. I've used ON (as part of Office 
2010) for several years as a personal information repository. My 
understanding is, that with Office 365 there will only be a very limited 
version of OneNote available, with a functionality reduced to the app 
version. I was looking for other solutions and eventually chose TW/BobWin. 
Honestly, I've never looked back. I find it much easier to maintain the 
semi-structured information I need (i.e. a combination of free-form text 
and information stored in fields) in TW. Also, working in a corporate 
environment, I was able to install everything under the radar. I also was 
able to use TW vanilla on our sharepoint environment, but having to load a 
potentially big html file everytime across a sluggish network deterred me. 

To be fair, the search function in ON is great. But the flexibility in TW 
beats everything.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6250cc0e-be91-48f7-b72b-2872932b2c0d%40googlegroups.com.

[tw5] Re: How to use variables in filter expressions

['Werner' via TiddlyWiki]

Thanks Tony, works. Still, what kind of string/variable concatenation works 
under what circumstances is pretty confusing. Bit of a learning curve 
actually.

Best
Werner

Am Mittwoch, 20. Februar 2019 23:42:48 UTC+1 schrieb TonyM:
>
> Werner,
>
> Just remove the [ ] from []
>
> >
>
> I have a* draft document* covering this and more here 
> http://tiddlywiki.psat.com.au/#Variables%2C%20Parameters%20and%20transclusions
>
> See the within filters
>
>
>- There is no need to include html or widgets in Filters so single 
>bracket versions are used (unlike *Within wikiText*)
>
> In Wiki text we must allow  to be identified as they 
> are different from <>, <$widgetname> but not in 
> filters.
>
> so  and {tiddlername} or {tiddlername!!fielodname} are 
> used in filters
>
>
>- since the above delineate the beginning and end of a variable or 
>transclusion you leave out a set of [ ] in filters.
>
> eg filter="[!has]" or 
> "filter="[backlinks[]]" 
> "filter="[subfilter]"
>
> While a variable's 'value', or a macros 'output', can be used as a filter 
> parameter, 'macro parameters' are not supported in filters.
>
>  can be used but the parameter is ignored ? TEST
>
>
> Regards
> Tony
>
> On Thursday, 21 February 2019 05:20:23 UTC+11, Werner wrote:
>>
>> Hi, pretty new to TiddlyWiki and still trying to wrap my head around 
>> various concepts. Also did some searching in this group but haven't found 
>> anything that could help me.
>>
>> OK, I want do some kind of dynamic filtering, according to a given 
>> variable. Basically, I want to set a variable and use it in a filter to 
>> reference the contents of a field. So, the result should look something 
>> like that
>>
>> <]tag[Products]!field:status[1]]">>
>>
>> where  would be the variable to be used.
>>
>> Thanks for helping me out on this.
>>
>> Best
>> Werner
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6444b429-6e65-4198-9c22-797bc0a98044%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] How to use variables in filter expressions

['Werner' via TiddlyWiki]

Hi, pretty new to TiddlyWiki and still trying to wrap my head around 
various concepts. Also did some searching in this group but haven't found 
anything that could help me.

OK, I want do some kind of dynamic filtering, according to a given 
variable. Basically, I want to set a variable and use it in a filter to 
reference the contents of a field. So, the result should look something 
like that

<]tag[Products]!field:status[1]]">>

where  would be the variable to be used.

Thanks for helping me out on this.

Best
Werner

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/66c19a11-c893-4ce7-8708-a8651a0c3255%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.