[tw5] Re: Hitting a barrier at 36,000 tiddlers

[TonyM]

Possibly related To tag search performance.

Unless you use sort[] list of tiddlers with a given tag will be sorted in 
the order they are listed in a list field. I would assume thus tiddlywiki 
needs to look for list field existence on any tag.

Also any tag pill for a tag, one exists for every Word in the dictionary 
tagged with Vorto if you click on the tag pill it will list all 36,000 
words so tagged in the tag pill drop down. Are there dropdown populated 
only once opened or before hand. If before hand every tag pill with contain 
a 36,000 item drop down.

I note that in my high performing wiki of ESPDIC 
https://tiddlywiki.psat.com.au/ESPDIC/ that the More Tags field does not 
include Vorto, and there is no vorto tiddler. 

Regards
Tony


On Monday, September 23, 2019 at 2:43:10 PM UTC+10, Mat wrote:
>
> Did you try [contains:tags[Vorto]] ?
>
> <:-)
>

-- 
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/75c4e96c-5393-43f9-a2cf-e3d18c37ee48%40googlegroups.com.

[tw5] Re: Task: Filter all tiddlers created between 01.09.2019 and 15.09.2019. How/where to find information/documentation to get this task done?

[TonyM]

Cd.K

Thanks for sharing back. I expect the scheduled solution is the best 
however;

On returning I had a thought. Place this in a tiddler on tiddlywiki.com

Filter-Var: <$edit-text tiddler="$:/temp/filtervar" tag=input/>
Filter: <$edit-text tiddler="$:/temp/filter" tag=input/> can also use 
``
<$set name=filter-var value={{$:/temp/filtervar}}>
<$set name=filter value={{$:/temp/filter}}>
<$list filter={{$:/temp/filter}}>





Then enter in filter-var
201909(0[1-9|1[0-5])

And in filter reference filter-var
[regexp:created]

Basically this make possible the introduction of a variable to the filter 
used in the search, as one has to do when using regex with square brackets 
in wikt text.

This could also be used to test the use of subfilters
Filter-var
title text modified modifier created creator tags type list caption

Filter
[fields[]!subfilter]

So I wonder if there was a way to allow the setting of a variable in the 
advanced search filter tab would be useful. It would only work if included 
in the filter.
Or alternatively use {$:/temp/filtervar} in the advanced search filter

[fields[]!subfilter{$:/temp/filtervar}]

Or in the original example

Enter in filter-var
201909(0[1-9|1[0-5])

And in advanced search filter reference filter-var tiddler
[regexp:created{$:/temp/filtervar}]

And there is yet another option:
in a tiddler tagged $:/tags/Macro
Place
\define varname() 201909(0[1-9|1[0-5])

and use  in your advanced filter

[regexp:created]

I have tested all of the above and they work

Regards
Tony

On Monday, September 23, 2019 at 1:03:28 PM UTC+10, Cd.K wrote:
>
> TonyM
>
> Advanced Search with regexp:created and nested square brackets:
>
>
> [image: 23-09-_2019_04-48-05.png]
> The solution is surprisingly simple and requires only a few changes in `
> $:/core/modules/filters.js` (see issue #4267). 
> 
>
> Next step is to create the mod for the mod-loader plugin. As so often a 
> link is missing in the description.   
>
>
> Regards
> Cd.K
>
>
>
>
> On Saturday, September 21, 2019 at 3:52:36 AM UTC+2, TonyM wrote:
>>
>> Cd.K
>>
>> Yes, and alternate regex search tab that permits entry into a variable 
>> could overcome this limitation. It could include more regex advice 
>> including that which you ask for.
>>
>> Outside of regex and the inappropriate use of [ ] in title (not 
>> recommended) I am not sure many would expose this issue. Perhaps a not can 
>> be added in the documentation on tiddlywiki.com. Just edit a tiddler to 
>> propose the change.
>>
>> Regards
>> Tony
>>
>> On Friday, September 20, 2019 at 9:22:10 PM UTC+10, Cd.K wrote:
>>>
>>> TiddlyTweeter
>>>
>>> I don't agree. 
>>>
>>> I've stumbled across these very places. The problem ist that you can't 
>>> set up variables in Advanced Search and this hint is missing. For those who 
>>> know it, it's obvious, but not for newbies.  It's not easy to get used to 
>>> TiddlyWiki and such things make it unnecessarily difficult.
>>>
>>> BTW the use of RegExpr's in Advanced Search is massively restricted. 
>>> Either a correct error message or a possibility in Advanced Search to set 
>>> up variable(s) for the RegExpr operator via the interface of the tiddler - 
>>> not in edit mode. It would also be correct to remove the RegExpr operator 
>>> from Advanced Search.  But nobody wants that.  
>>>
>>> Regards
>>> Cd.K
>>>
>>> On Friday, September 20, 2019 at 12:49:33 PM UTC+2, @TiddlyTweeter wrote:

 Ciao Cd.K

 The "brackets problem" is actually documented at 
 https://tiddlywiki.com/#regexp%20Operator

 | The filter syntax  makes it 
 impossible to directly specify a regular expression that contains square 
 brackets. 

 There is also an example at: 
 https://tiddlywiki.com/#regexp%20Operator%20(Examples)

 I agree it might be highlighted more like this ...

 | The filter syntax  makes it 
 impossible to directly specify a regular expression that contains  regex 
 character class  [...]  brackets. 

 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/628bdb4b-0faa-46b8-9040-82ab6f811231%40googlegroups.com.

[tw5] Re: Hitting a barrier at 36,000 tiddlers

[Mat]

Did you try [contains:tags[Vorto]] ?

<:-)

-- 
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/65ad745e-51a0-4f20-bac8-d9fce448f4cd%40googlegroups.com.

[tw5] Re: Hitting a barrier at 36,000 tiddlers

['Mark S.' via TiddlyWiki]

Seems like the answer might be a separate tag filter operator for use on 
data with high use counts. Then the
developer could decide when it was most appropriate to use whichever tag 
filter operator.


On Sunday, September 22, 2019 at 4:13:40 AM UTC-7, Jed Carty wrote:
>
> Each filter operator only works on the output of the previous operator, so 
> the order matters with later operators in a run generally working with 
> fewer inputs than earlier operators.
> To my knowledge none of the operators do anything in parallel, that may be 
> difficult to set up because javascript is single threaded.
>
> The tags field is treated differently, the tags field is sorted and stored 
> as a different type of list than the title lists normally used in 
> tiddlywiki are, this means that accessing or manipulating the tags field 
> introduces an extra step or two.
>
> In the worst case it has to load the field, parse it as the list type it 
> uses, do whatever the operator does, re-encode it as the tags list and then 
> save it.
>
> Reading or searching the tags field doesn't need to re-encode it or save 
> the field, but the extra parsing can add some overhead.
>
> Other than that each filter step takes a title list and returns a title 
> list, there isn't any other memory that carries over between each step.
>
> The tag operator is a pretty heavy operator. It finds every tiddler in the 
> wiki that has the current tag then checks each input title to see if it is 
> on that list and returns the list of input titles that pass that test.
>
> So if you have a million tiddlers with the tag Vorto it is searching 
> through a list of a million tiddlers once for each input tiddler.
>
> I think that the current version has a better worst-case behaviour than 
> many alternatives, but it's speed is based on the number of tiddlers in the 
> input list and the number of tiddlers in the wiki that have the same tag.
>
> It could be changed so that the speed is based off of the number of input 
> tiddlers and the number of tags each input tiddler has which may be worse 
> in small wikis but a lot better in very large wikis. It depends on the cost 
> of checking the tags list of each tiddler in the input list individually vs 
> the cost of getting a list of all tiddlers in the wiki that have the input 
> tag.
>
> Most of the improvements that immediately come to mind don't preserve the 
> order of the input titles. In large wikis resorting the output could be far 
> faster than the current version, but much slower in smaller wikis.
>
> I don't know how much overhead would be added by adding a check to see 
> which one is faster, that check may be a complex task by itself.
>
> The tag operator may be a place where some significant improvements can be 
> made.
>

-- 
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/6c49003f-e6fe-4139-8c89-49220d4e3cdb%40googlegroups.com.

[tw5] Re: Task: Filter all tiddlers created between 01.09.2019 and 15.09.2019. How/where to find information/documentation to get this task done?

['Cd.K' via TiddlyWiki]

TonyM

Advanced Search with regexp:created and nested square brackets:


[image: 23-09-_2019_04-48-05.png]
The solution is surprisingly simple and requires only a few changes in `
$:/core/modules/filters.js` (see issue #4267). 


Next step is to create the mod for the mod-loader plugin. As so often a 
link is missing in the description.   


Regards
Cd.K




On Saturday, September 21, 2019 at 3:52:36 AM UTC+2, TonyM wrote:
>
> Cd.K
>
> Yes, and alternate regex search tab that permits entry into a variable 
> could overcome this limitation. It could include more regex advice 
> including that which you ask for.
>
> Outside of regex and the inappropriate use of [ ] in title (not 
> recommended) I am not sure many would expose this issue. Perhaps a not can 
> be added in the documentation on tiddlywiki.com. Just edit a tiddler to 
> propose the change.
>
> Regards
> Tony
>
> On Friday, September 20, 2019 at 9:22:10 PM UTC+10, Cd.K wrote:
>>
>> TiddlyTweeter
>>
>> I don't agree. 
>>
>> I've stumbled across these very places. The problem ist that you can't 
>> set up variables in Advanced Search and this hint is missing. For those who 
>> know it, it's obvious, but not for newbies.  It's not easy to get used to 
>> TiddlyWiki and such things make it unnecessarily difficult.
>>
>> BTW the use of RegExpr's in Advanced Search is massively restricted. 
>> Either a correct error message or a possibility in Advanced Search to set 
>> up variable(s) for the RegExpr operator via the interface of the tiddler - 
>> not in edit mode. It would also be correct to remove the RegExpr operator 
>> from Advanced Search.  But nobody wants that.  
>>
>> Regards
>> Cd.K
>>
>> On Friday, September 20, 2019 at 12:49:33 PM UTC+2, @TiddlyTweeter wrote:
>>>
>>> Ciao Cd.K
>>>
>>> The "brackets problem" is actually documented at 
>>> https://tiddlywiki.com/#regexp%20Operator
>>>
>>> | The filter syntax  makes it 
>>> impossible to directly specify a regular expression that contains square 
>>> brackets. 
>>>
>>> There is also an example at: 
>>> https://tiddlywiki.com/#regexp%20Operator%20(Examples)
>>>
>>> I agree it might be highlighted more like this ...
>>>
>>> | The filter syntax  makes it 
>>> impossible to directly specify a regular expression that contains  regex 
>>> character class  [...]  brackets. 
>>>
>>> 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/62991b0a-21eb-4247-a275-688d98131ab8%40googlegroups.com.

[tw5] A Little advanced HTML for a tiddlywiki solution

[TonyM]

Folks,

I am working on a way to reference tiddlywiki content from static pages to 
either static or interactive wikis.

For example I have a static version of Filter Operators that can be its own 
HTML page or embedded in a Tiddler. 

Inside the HTML file Head tag it's possible to modify the HTML  tag 
to change either the base or the target attribute that applies to all href 
links.

To complete this project I would be keen to identify one or both of the 
following

   - Add the facility to toggle the base tag href and target values in a 
   html page
   - Add the facility to do the equivalent of changing the above in a 
   section of html within a tiddler

This is just a little more than my current expertise, so if you can help me 
please.

Thanks
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/1c974da0-4e3a-4c61-a61a-ec6832602027%40googlegroups.com.

[tw5] Re: Itty.bitty - a cousin to the tiddler?

[TonyM]

Mat,

In a similar vein when this kind of sharing matures we can leverage these 
instead https://css-tricks.com/how-to-use-the-web-share-api/ and along with 
the fall back options perhaps someone can make a tiddlywiki widget for this?

Similar to copy to clipboard of the permalink as a sharing mechanism, 
perhaps we could copy to clipboard an ittybity link (With content). 

Actually we could make our own link structure which contains a tiddlers 
content in it, as long as once pasted back into tiddlywiki the import 
mechanisium can recognise and deconstruct the tiddler. So that in any wiki 
on any tiddler click a button, then on any wiki ctrl-v and import and it 
rebuilds the source tiddler.

Regards
Tony


On Monday, September 23, 2019 at 10:10:03 AM UTC+10, TonyM wrote:
>
> Mat,
>
> This is a quite interesting idea. I am yet to fully understand the 
> implications and functionality especially as it relates to tiddlywiki but 
> its worth investigating.
>
> It also made me think when it comes to desirable features in tiddlywiki we 
> do need to look further afield as tiddlywiki can make use of the standard 
> internet technologies well. It makes sense not to reinvent the wheel. 
>
> The work that needs to be done, with such solutions is providing a mapping 
> with tiddlywiki object such being able to package a tiddler as a link. 
>
>
>- I wonder if we provided an edit tiddler option on a read only wiki 
>that someone could provide documentation updates then they share the 
> change 
>as a link, then the link used to update the master wiki. 
>- There are many ways to share links using many different solutions 
>especially on mobile devices, so to enable tiddlers to be share this way 
>could be very helpful
>- Perhaps static tiddlers generated by node server could be packages 
>as itty.bitty links.
>- Perhaps ittybitty links could be parsed into tiddlers 
>
> Thanks for sharing
>
> Regards
> Tony
>
>
> On Monday, September 23, 2019 at 3:46:06 AM UTC+10, Mat wrote:
>>
>> @dubiousscript just shared 
>> 
>>  
>> something over at gh:
>>
>> Itty.bitty 
>> 
>> ...or try it here 
>> ...and find it on gh here 
>>
>> Come ON! Is this a cousin to the tiddler?! I'm in love at first glance 
>> but I'm not sure what to do with it!
>>
>> Could we convert tiddlers to itty.bittys? If one wants to share a 
>> tiddler, instead of export+email a file, you just share a link. One 
>> itty.bitty can contain surprisingly much 
>> 

[tw5] Re: SVG logotype as $:/SiteTitle /

[TonyM]

Thierry

Just use the system tag $:/tags/SideBarSegment to introduce any new element 
like your image to the sidebar, click on a tag pill 
for $:/tags/SideBarSegment to change the order.

This will just add the logo and leave the $:/SiteTitle intact, but if you 
then want to hide the title, change only its display in the sidebar (remove 
sidebarsegment tag on $:/core/ui/SideBarSegments/site-title), since the 
site title is used to construct the save filename, the tab title and more 
"leave it alone).

You may also consider modifying $:/core/wiki/title 
 
to 
change the text on the browser tab.

Regards
Tony

On Monday, September 23, 2019 at 5:14:37 AM UTC+10, Thierry wrote:
>
> Hello,
>
> I'd like to use a SVG as a header inside the sidebar.
> The result is appropriate but the site has no title.
> Therefore the browser displays a blank space in the tab/window title.
> Look at the screenshots.
>
> How could I use the logotype and have the title LABSud displayed ?
>
> Thank you very much for helping me.
>
> Thierry
>
>
>
>

-- 
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/5fca2a3b-e994-4e09-9c5b-0a4cbc59c291%40googlegroups.com.

[tw5] Re: Itty.bitty - a cousin to the tiddler?

[TonyM]

Mat,

This is a quite interesting idea. I am yet to fully understand the 
implications and functionality especially as it relates to tiddlywiki but 
its worth investigating.

It also made me think when it comes to desirable features in tiddlywiki we 
do need to look further afield as tiddlywiki can make use of the standard 
internet technologies well. It makes sense not to reinvent the wheel. 

The work that needs to be done, with such solutions is providing a mapping 
with tiddlywiki object such being able to package a tiddler as a link. 


   - I wonder if we provided an edit tiddler option on a read only wiki 
   that someone could provide documentation updates then they share the change 
   as a link, then the link used to update the master wiki. 
   - There are many ways to share links using many different solutions 
   especially on mobile devices, so to enable tiddlers to be share this way 
   could be very helpful
   - Perhaps static tiddlers generated by node server could be packages as 
   itty.bitty links.
   - Perhaps ittybitty links could be parsed into tiddlers 

Thanks for sharing

Regards
Tony


On Monday, September 23, 2019 at 3:46:06 AM UTC+10, Mat wrote:
>
> @dubiousscript just shared 
>  
> something over at gh:
>
> Itty.bitty 
> 
> ...or try it here 
> ...and find it on gh here 
>
> Come ON! Is this a cousin to the tiddler?! I'm in love at first glance but 
> I'm not sure what to do with it!
>
> Could we convert tiddlers to itty.bittys? If one wants to share a tiddler, 
> instead of export+email a file, you just share a link. One itty.bitty can 
> contain surprisingly much 
> 

[tw5] Re: SVG logotype as $:/SiteTitle /

[Birthe C]

The title would be there but invisible - only your logo visible, but the 
browser shows the title. 
Keep what you have and add:

@@display:none;LABSud@@


Birthe

-- 
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/2bfedbf2-a4c5-478a-ab5a-5b6e301c7103%40googlegroups.com.

[tw5] Re: SVG logotype as $:/SiteTitle /

[Mark Kerrigan]

Hello

I'm sure someone else might have a more clever answer, but I'm not sure if 
it's possible to use an image as part of the site title.

You could modify the following shadow tiddler and replace it with your text 
"LABSud". This would put the text in the site title.

$:/core/wiki/title

Then you could also create a favicon. See the instructions below.

https://tiddlywiki.com/#Setting%20a%20favicon

Thanks
Mark Kerrigan

On Sunday, September 22, 2019 at 12:14:37 PM UTC-7, Thierry wrote:
>
> Hello,
>
> I'd like to use a SVG as a header inside the sidebar.
> The result is appropriate but the site has no title.
> Therefore the browser displays a blank space in the tab/window title.
> Look at the screenshots.
>
> How could I use the logotype and have the title LABSud displayed ?
>
> Thank you very much for helping me.
>
> Thierry
>
>
>
>

-- 
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/8f65018a-adbd-4108-b301-026eb94aa5f1%40googlegroups.com.

[tw5] Itty.bitty - a cousin to the tiddler?

[Mat]

@dubiousscript just shared 
 
something over at gh:

Itty.bitty 

...or try it here 
...and find it on gh here 

Come ON! Is this a cousin to the tiddler?! I'm in love at first glance but 
I'm not sure what to do with it!

Could we convert tiddlers to itty.bittys? If one wants to share a tiddler, 
instead of export+email a file, you just share a link. One itty.bitty can 
contain surprisingly much 

Re: [tw5] Control of node.js instance(s)

[Jeremy Ruston]

I think Bob may do what you want:

https://github.com/OokTech/TW5-Bob

Best wishes

Jeremy

> On 20 Sep 2019, at 19:17, 'Torax Malu' via TiddlyWiki 
>  wrote:
> 
> Hi,
> 
> is there a known control plugin for TiddlyWiki on node.js do control the 
> server instance out of the wiki itself? I refer here primarily to stopping 
> and restarting the server without using the command-line.
> 
> thanks for a short answer.
> 
> cheers
> 
> Torax
> 
> -- 
> 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/6867dbd3-e249-480a-a426-8f6d6b715d0d%40googlegroups.com
>  
> .

-- 
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/EB3AC15D-FD9D-4D13-839A-A1FF689CA00F%40gmail.com.

Re: [tw5] Unpacking json plugin file - algorithms for creating tiddlywiki.files

[Jeremy Ruston]

Hi David

The tiddlywiki.files mechanism is primarily intended for extracting tiddlers 
out of existing libraries, without needing to modify those files. It’s a lossy 
process (because not all the files necessarily end up in tiddlers), and it 
isn’t generally possible to reconstruct the original files from the extracted 
tiddlers.

You may be interested in the source for the savewikifolder command which does 
what you’re trying to do but within TW5:

https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/commands/savewikifolder.js
 


Best wishes

Jeremy.

> On 22 Sep 2019, at 02:30, David Nebauer  wrote:
> 
> I'm playing with a script that unpacks a single json plugin file to 
> individual tiddler files for installing under a node.js server. The script 
> would also create a plugin.info file and, if necessary, a tiddlywiki.files 
> file. (Note that TW is not involved in this process - the script acts 
> directly on the json file.)
> 
> I am only using a subset of tiddlywiki.files functionality at the moment - 
> just the 'tiddlers' section with the 'file' and 'fields' fields.
> 
> My question is this: is there any way of determining solely from the contents 
> of a tiddler whether its metadata should be provided via the tiddlywiki.files 
> file rather than the tiddler's own file? Another way to put that is: is there 
> an algorithm based on tiddler content that determines whether a tiddler's 
> metadata is provided via the tiddlywiki.files file rather than the tiddler's 
> own file?
> 
> -- 
> 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/a200fbdb-4bfe-4aee-81ec-5d70dae578ed%40googlegroups.com
>  
> .

-- 
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/529E866C-B373-4136-A794-3F668B776834%40gmail.com.

Re: [tw5] What prefix for _canonical_uri?

[Jeremy Ruston]

Hi RA

> Trying to add FontAwesome as a plugin. The wiki is working, the plugin is 
> recognized, and it contains shadow tiddlers for each svg file.
> The only part I cannot get right is the _canonical_uri, so I get a "broken 
> image" icon in each shadow tiddler instead of an svg image.

If you’re using _canonical_uri, then the SVGs would also need to be exposed via 
HTTP. You could put them in the “files” folder of the wiki:

https://tiddlywiki.com/#Using%20the%20integrated%20static%20file%20server

If you went that route you should be able to use `files/` as the prefix.

I’d be inclined to not bother with _canonical_uri, and instead embed the SVG 
text fields as shadow tiddlers.

Best wishes

Jeremy.

> 
> The documentation says "The URI can be absolute or relative to the HTML 
> document."
> What is the location of "HTML document" in case of Node.js? Is it where 
> tiddlywiki.js is, or where tiddlywiki.info is? Or the current path in the 
> shell where I'm launching the nodejs command from?
> What should I set the prefix to? Is it even possible for _canonical_uri to 
> point to a relative path that is outside the "HTML document"?
> 
> My wiki URL is
> http://:/work
> 
> The tiddlywiki command:
> nodejs /srv/TiddlyWiki5/app/tiddlywiki ++/srv/TiddlyWiki5/plugins/fontawesome 
> /srv/TiddlyWiki5/wikis/work --listen host=0.0.0.0 port=8083 
> 'root-tiddler=$:/core/save/lazy-all' 'path-prefix=/work'
> 
> Filesystem structure:
> /srv/TiddlyWiki5/
>   app/tiddlywiki.js
>   plugins/fontawesome/tiddlywiki.files
>   plugins/fontawesome/svgs/regular/*.svg
>   wikis/work/tiddlywiki.info
>   wikis/work/tiddlers/*.tid
> 
> tiddlywiki.files (cannot get the prefix right):
> {
> "directories": [
> {
> "path": "svgs/regular",
> "filesRegExp": "^.*\\.svg$",
> "isTiddlerFile": false,
> "fields": {
> "title": {"source": "basename-uri-decoded"},
> "created": {"source": "created"},
> "modified": {"source": "modified"},
> "type": "image/svg+xml",
> "_canonical_uri": {"source": "filename", "prefix": " should I put here?>"}
> }
> }
> ]
> }
> 
> 
> -- 
> 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/3fb7cd4b-7f02-4a96-b975-f909070de27f%40googlegroups.com
>  
> .

-- 
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/2DD3009A-72DE-4928-9489-EFEA5A3750B6%40gmail.com.

Re: [tw5] Re: Introducing the Voynich Extended Hand font plugin

[Pit.W.]

Thank you Julio.

Now you can write your own manuscript :)

Pit

Am 22.09.2019 um 15:34 schrieb Julio Peña:

Hello there Pit,

Nice stuff!

OooofeeearieI was just watching a documentary last night on 
the History of the Voynich manuscript.



Regards,

Julio
--
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/53dd4e53-ed03-4d24-9757-fd5b3d06c0d4%40googlegroups.com 
.



_

Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte 
E-Mail-Adresse mitnehmen! https://www.eclipso.de

--
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/170cf38a-5eba-23ae-9c92-40dc273cc3a0%40eclipso.ch.

[tw5] Re: Introducing the Voynich Extended Hand font plugin

[Julio Peña]

Hello there Pit,

Nice stuff!

OooofeeearieI was just watching a documentary last night on the 
History of the Voynich manuscript.


Regards,

Julio

-- 
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/53dd4e53-ed03-4d24-9757-fd5b3d06c0d4%40googlegroups.com.

[tw5] Re: What's the point of effort?

[Mohammad]

Hi Watt!
Sure I will!

Cheers
Mohammad

On Sunday, September 22, 2019 at 4:20:20 PM UTC+3:30, Watt wrote:
>
> @Gloom Looks interesting! Have you got a link to share?
>
> @Mohammad - sorry for the delayed response - just a simple link to your 
> active TW-Scripts site was what I was thinking, not to any specific 
> solution. After your github problems I wasn't sure of the correct location. 
> Thanks.
>

-- 
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/0e0c03ef-31c1-41af-b071-59216027b014%40googlegroups.com.

[tw5] Re: Today TiddlyWiki is 15 years old

[Watt]

Happy Birthday TW! Thanks Jeremy, it's used here every day!

-- 
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/68f3fc88-f6bd-406d-a1bc-c8206bb68712%40googlegroups.com.

[tw5] Re: What's the point of effort?

[Watt]

@Gloom Looks interesting! Have you got a link to share?

@Mohammad - sorry for the delayed response - just a simple link to your active 
TW-Scripts site was what I was thinking, not to any specific solution. After 
your github problems I wasn't sure of the correct location. Thanks.

-- 
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/30bb06b3-529d-4121-82e4-af85a39e3fa5%40googlegroups.com.

[tw5] Re: Introducing the Voynich Extended Hand font plugin

[David Gifford]

Thanks Pit, I added this and the Editor Stamp plugin to the toolmap. I 
already had the Swot tows. 

On Saturday, September 21, 2019 at 8:31:31 AM UTC-5, Pit.W. wrote:
>
> If someone feels the desire to write their texts in the myterious Voynich 
> alphabet
>
> Here: http://pocketknife.tiddlyspot.com/#
>
> you find the $:/plugins/+PGA/EVA plugin. 
>
> It might be usefull when working in a public space where you dont want 
> observers to read your laptop screen.
>
> Well, you will have to learn Voynich letters...
>
>
> Otherwise it serves as a demonstration on how to fiddle with fonts. Hattip 
> to Aidan Grey for helping.
>
>
> Pit.W
>
>
> _
> 
> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte 
> E-Mail-Adresse mitnehmen! https://www.eclipso.de
>
>
>

-- 
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/0033f6ae-68bd-4468-9b8c-8dc3197393e3%40googlegroups.com.

[tw5] Re: Hitting a barrier at 36,000 tiddlers

[Jed Carty]

Each filter operator only works on the output of the previous operator, so 
the order matters with later operators in a run generally working with 
fewer inputs than earlier operators.
To my knowledge none of the operators do anything in parallel, that may be 
difficult to set up because javascript is single threaded.

The tags field is treated differently, the tags field is sorted and stored 
as a different type of list than the title lists normally used in 
tiddlywiki are, this means that accessing or manipulating the tags field 
introduces an extra step or two.

In the worst case it has to load the field, parse it as the list type it 
uses, do whatever the operator does, re-encode it as the tags list and then 
save it.

Reading or searching the tags field doesn't need to re-encode it or save 
the field, but the extra parsing can add some overhead.

Other than that each filter step takes a title list and returns a title 
list, there isn't any other memory that carries over between each step.

The tag operator is a pretty heavy operator. It finds every tiddler in the 
wiki that has the current tag then checks each input title to see if it is 
on that list and returns the list of input titles that pass that test.

So if you have a million tiddlers with the tag Vorto it is searching 
through a list of a million tiddlers once for each input tiddler.

I think that the current version has a better worst-case behaviour than 
many alternatives, but it's speed is based on the number of tiddlers in the 
input list and the number of tiddlers in the wiki that have the same tag.

It could be changed so that the speed is based off of the number of input 
tiddlers and the number of tags each input tiddler has which may be worse 
in small wikis but a lot better in very large wikis. It depends on the cost 
of checking the tags list of each tiddler in the input list individually vs 
the cost of getting a list of all tiddlers in the wiki that have the input 
tag.

Most of the improvements that immediately come to mind don't preserve the 
order of the input titles. In large wikis resorting the output could be far 
faster than the current version, but much slower in smaller wikis.

I don't know how much overhead would be added by adding a check to see 
which one is faster, that check may be a complex task by itself.

The tag operator may be a place where some significant improvements can be 
made.

-- 
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/e74c067c-7115-4bb0-baa2-33703b46e97b%40googlegroups.com.

[tw5] Re: Hitting a barrier at 36,000 tiddlers

[Mat]

Mark, that might be a huge step forward.

Here is a brain dump of hypotheses and thoughts from someone who doesn't 
really know what he is talking about. You will, for sure, think "what is 
this fool twaddling about?" but while my ignorance is typically a weakness 
it occasionally brings an out-of-the-box perspective that is fruitful. I 
used to think most people were too shy or polite to express ignorant ideas 
but it turned out they just barely have any ideas to begin with - so, for 
what it's worth:


   - I'm assuming that filtering works by saving the step output in a 
   variable that progressively changes for each new step. However if, to our 
   surprise, the position of the tag operator in the filter doesn't affect the 
   time it takes then maybe it happens to not use the latest instance of the 
   variable but an earlier one? A question here is if the variable status is 
   saved somewhere and the tag op somehow accesses this earlier filter step 
   output instead of the latest instance?
   - I believe the tags field is treated differently from other fields. 
   Matching a tag, means iterating over all items in this field. Just maybe 
   the system is made to deal with this in some parallel (asynched?) process 
   and this messes things up when one of the parallel processes needs the 
   input from the other one?
   - Maybe the repeated iteration in the tag operator gets stuck in some 
   recursive loop? Are the edge cases properly investigated - a tiddler with 
   no tag? A tiddler with tag fooX when using tag[foo]? Might some tag fields 
   overflow a magic max number of allowed tags? 
   - And are tiddlers that DO fulfill the filter properly dealt with? For 
   example "tag[foo]" will get the tiddler with "tags: foo bar baz" but will 
   it effectively avoid iterating over the rest of the tags when "foo" is 
   already found? (This possible behaviour would not explain Marks wikis 
   behaviour but maybe it is relevant anyway)
   - Is there some magic number of parallel processes where the *browser* 
   switches methods for performing calculations? Might specifically the tag 
   operator initiate an atypical number of processes which triggers this?
   - Does the tag op - or filters in general - treat pure tags (i.e tags 
   without existing such-named tiddlers) differently from TagTiddlers? 
   - Does the system do any preprocessing on the filter before the steps 
   are processes? Perhaps it cleans up the syntax, e.g trimming white spaces 
   or some such, which affects specifically the tag op?

Again, just a brain dump to trigger ideas. I'm not expecting anyone to 
*answer* these .

<:-)



-- 
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/30626d7b-13c4-4b92-8d4e-fd1bda2b5f4d%40googlegroups.com.

[tw5] What prefix for _canonical_uri?

[RA]

Trying to add FontAwesome as a plugin. The wiki is working, the plugin is 
recognized, and it contains shadow tiddlers for each svg file.
The only part I cannot get right is the _canonical_uri, so I get a "broken 
image" icon in each shadow tiddler instead of an svg image.

The documentation says "The URI can be absolute or relative to the HTML 
document."
What is the location of "HTML document" in case of Node.js? Is it where 
tiddlywiki.js is, or where tiddlywiki.info is? Or the current path in the 
shell where I'm launching the nodejs command from?
What should I set the prefix to? Is it even possible for _canonical_uri to 
point to a relative path that is outside the "HTML document"?

My wiki URL is 
http://:/work

The tiddlywiki command:
nodejs /srv/TiddlyWiki5/app/tiddlywiki ++/srv/TiddlyWiki5/plugins/fontawesome 
/srv/TiddlyWiki5/wikis/work --listen host=0.0.0.0 port=8083 
'root-tiddler=$:/core/save/lazy-all' 'path-prefix=/work'

Filesystem structure:
/srv/TiddlyWiki5/
  app/tiddlywiki.js
  plugins/fontawesome/tiddlywiki.files
  plugins/fontawesome/svgs/regular/*.svg
  wikis/work/tiddlywiki.info
  wikis/work/tiddlers/*.tid

tiddlywiki.files (cannot get the prefix right):
{
"directories": [
{
"path": "svgs/regular",
"filesRegExp": "^.*\\.svg$",
"isTiddlerFile": false,
"fields": {
"title": {"source": "basename-uri-decoded"},
"created": {"source": "created"},
"modified": {"source": "modified"},
"type": "image/svg+xml",
"_canonical_uri": {"source": "filename", "prefix": ""}
}
}
]
}

-- 
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/3fb7cd4b-7f02-4a96-b975-f909070de27f%40googlegroups.com.

[tw5] Re: Hitting a barrier at 36,000 tiddlers

[TonyM]

Mark,

Perhaps try these test in a 5.1.19 Wiki given the additional indexing to 
improve performance was introduced in 5.1.20 and if there was any change 
that could have had an unexpected impact in this area I think it could be 
those changes. Keeping in mind the tags field potentially contains multiple 
values and if different order so how is this sort indexing operating. I 
believe Jeremy's 60K tiddlers were working before 5.1.20 was introduced.

Its great that you are possibly closing in on this. Are you confident your 
sidebar is closed and there is nothing that could be interfering? Like my 
range of suggestions before?

Regards
Tony

On Sunday, September 22, 2019 at 1:35:18 PM UTC+10, Mark S. wrote:
>
> It appears that having a search, list, or list-links that uses a *tag 
> operator*
> running in any currently open tiddler will create a performance problem 
> EVEN if the tag
> operator is applied *AFTER *a previous search operator. 
>
> So this 
>
>
> [all[shadows+tiddlers]search:title{$:/temp/search2}has[en]sort[title]limit[10]]
>
> performs fine, but this
>
>
> [all[shadows+tiddlers]tag[Vorto]search:title{$:/temp/search2}sort[title]limit[10]]
>
> or this
>
>
> [all[shadows+tiddlers]search:title{$:/temp/search2}tag[Vorto]sort[title]limit[10]]
>
> Perform poorly.
>
> This last one is especially puzzling, since you would expect at this point 
> that the tag 
> only has to filter a handful of input titles. This suggests that there 
> might be something 
> wrong with the tag operator, that goes undetected except when there is a 
> large number of tiddlers.
>
> If a process uses the *tag operator* in any open tiddler, then the 
> performance of EVERYTHING,
> including simply typing in some other random tiddler, will be degraded.
>
> Or at least that's what it's looking like to me at the moment.  
>
> Thanks!
>
>

-- 
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/15b9503c-5251-44b9-a0c3-488dcbccb400%40googlegroups.com.