[tw5] Re: Tiddlywiki and Codepen, JSFiddle, .... or similar

[TonyM]

Mohammad,

So what about yammer is not free and the content is open and exportable. I am 
not even asked about this except once.

That can not be the explanation in my view.

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 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/1609ffae-4db8-41e1-a571-0d7e6d815d97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tiddlywiki and Codepen, JSFiddle, .... or similar

[Mohammad]

Tony,
 I understood people like a free and open host like google forum.


-Mohammad

-- 
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/3ead9e33-9d47-425b-bfdf-5e4f517f2db7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Bob - Usage of "Save Plugin As Folder"

[Joshua Fontany]

I have not used Bob yet, but I see it has the same tiddlers-as-files support 
that TiddlyServer does. Theres nothing stopping you from "expanding" a plugin 
tiddler (make non-shadow copies of all the shadow tiddlers) in vanilla 
tiddlywiki.

Back up your data! 

Apparently, the easiest way to generate a non-shadow tiddler from a shadow is 
to delete a field that does not exist. The below filter generates a list of 
plugin content tiddlers, then calls delete on a gibberish string field name. 
Replace the  and  tokens with the names from the tiddler you 
wish to unpack. 

<$button>
<$list filter="[[$:/plugins//]plugintiddlers[]]">
<$action-deletefield jhsfjh/>

Unpack!


You could then manually move the folder and setup the info.json 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 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/51e2ece9-544d-479b-bbeb-bc7dbe6e4da3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tiddlywiki and Codepen, JSFiddle, .... or similar

[TonyM]

Example Yammer Integration

Post Yammer messages with new GitHub commits 

Make sure everyone knows what's going on with development, even if they're 
not checking GitHub, by setting up this automation to post about it. Every 
new commit on GitHub will trigger this Zap, posting a new message on Yammer 
with the details (which can optionally be posted only for a specific group.)
How this GitHub-Yammer integration works 
   
   1. A new commit is made on GitHub 
   2. Zapier automatically posts a message on Yammer 

Apps involved 
   
   - GitHub 
   - Yammer 

Regards
Tony

On Monday, December 17, 2018 at 12:34:15 PM UTC+11, TonyM wrote:
>
> Mohammad,
>
> You tell me the answer to your Question. I built Yammer at 
> https://www.yammer.com/tiddlywiki/
>
> But even with 25+ people joining only a few even tried to have a 
> conversation, with this tool. 
>
> We do not even have the community involvement to discuss its pros and cons
>
> I suggested it is likely to be a very helpful tool (my experience with a 
> 45,000 people network) and can present a detailed argument in its favour, 
> yet I cant get many to even try it.
>
> Change is hard to implement but considering change evaluation in the first 
> place even harder.
>
> Then if Yammer + another tool (eg Git) was a good solution, people would 
> complain before we could consider the combination.
>
> Yammer has a lot of integrations.
>
> You can see how I would not dare propose Microsoft teams and other 
> solutions I know about if I cant even get a hearing on the first one I 
> propose. PS I have looked at other proposed solutions but they too did not 
> progress due to lack of involvement.
>
> How do we open the community up to evaluation?
>
> Regards
> Tony
>
>
> On Sunday, December 16, 2018 at 2:02:00 PM UTC+11, Mohammad wrote:
>>
>> Tony
>> This is a very active forum, it is a pity we have minimum facilities 
>> here. There were many discussions over this forum, how we can use a better 
>> solution but never come to a decision.
>>
>> Mohammad
>>
>

-- 
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/d22de972-75fd-47c1-9c12-fe4f760a546b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tiddlywiki and Codepen, JSFiddle, .... or similar

[TonyM]

Mohammad,

You tell me the answer to your Question. I built Yammer 
at https://www.yammer.com/tiddlywiki/

But even with 25+ people joining only a few even tried to have a 
conversation, with this tool. 

We do not even have the community involvement to discuss its pros and cons

I suggested it is likely to be a very helpful tool (my experience with a 
45,000 people network) and can present a detailed argument in its favour, 
yet I cant get many to even try it.

Change is hard to implement but considering change evaluation in the first 
place even harder.

Then if Yammer + another tool (eg Git) was a good solution, people would 
complain before we could consider the combination.

Yammer has a lot of integrations.

You can see how I would not dare propose Microsoft teams and other 
solutions I know about if I cant even get a hearing on the first one I 
propose. PS I have looked at other proposed solutions but they too did not 
progress due to lack of involvement.

How do we open the community up to evaluation?

Regards
Tony


On Sunday, December 16, 2018 at 2:02:00 PM UTC+11, Mohammad wrote:
>
> Tony
> This is a very active forum, it is a pity we have minimum facilities here. 
> There were many discussions over this forum, how we can use a better 
> solution but never come to a decision.
>
> Mohammad
>

-- 
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/8a21afde-94c6-4385-8c9d-a7d631f744ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tagging --- Organise From Serendipity

[TonyM]

Folks,

I believe I have argued it in the past, but I would like to offer my 
opinion that you should not use prefixes on tags to represent what they 
mean.
 Apart from anything you are breaking database normalisation rules by 
making an attribute of an object be part of the key to the object, what if 
you want to change that attribute,? you loose the key!

More often than not, a tag name is enough to imply its use, if you had the 
tag "urgent" and the tag "Windows" you would possibly guess that urgent is 
a status and Windows is a Operating system.

In the above cases I would have had a tiddler called "priority" which tags 
urgent standard low. It then becomes possible to interrogate all the tags 
on a given tiddler and determine if they are "priority"  tag. 
That is you can use the same tagging mechanism to group tags into 
meaningful groups. The Windows could have the tag OS, this a software title 
could have Windows, Linux, Android tags which are each also tagged OS.

What I think a lot of people miss about tags is they have a particular 
nature, imagine you have a tray of all possible tags sitting on your table, 
and you are packing a box. You can apply zero or more tags to your box as 
required. 

If however you want to categorise the box then you have to ask, can you 
only use existing categories, can a box belong to only one category at a 
time.

Now imagine subjects, perhaps subjects are linked to the category used, you 
can't place a subject on the wrongly categorised item.

Keywords, they may be unlimited in nature but they should first be sourced 
from existing keywords to avoid synonyms being used.

If you consider S S example tag types

   1. tags prefixed $:/ for the TW system
   2. tags for creating "parent-child" relationships - i.e. ordering a 
   Table of Contents
   3. tags for keeping track of excised data for transclusion back into the 
   original
   4. tags for changing style (custom css, display, colour, adding text, 
   triggering a veiw template, etc)
   5. tags for creating groups
   6. tags for categories
   7. tags for keywords
   8. other uses ???

All of the above can be indicated by tagging the "tags tiddler" and may 
need their own handling rules. Although we can use the $:/ prefix for the 
hidden system case. I would even like to see this abstracted away. Such a 
item could be made system hidden with a tag eg "$:/" we would then need 
tiddlywiki to honour this, by removing adding it to the is[system] group, 
or removing it from standard search.

The thing with tagging is they are the most permissive way of organising 
information, so they are the first things we call on to start organising 
tiddlers. If you want a more structured tagging system, less permissive, 
you are no longer really using tags but starting to use them as categories 
etc... Now this is great because you can use tags to do this without 
encoding rules, no need to develop the infrastructure/definition for 
categories just use then as if they were categories. The permissiveness of 
tags allows us to use them to represent all the above "relationships" in an 
ad hoc maner. Greate for design, prototyping and small solutions. 

As I build more complex repositories I move non tags (not the most 
permissive way of organising information) into tag groups, or into another 
field (less complexity). 

Do you understand what I am saying?
I can propose some improvements for handling tags and these other 
relationships but thought it best not to make this reply too long.

Tony






On Monday, December 17, 2018 at 5:12:09 AM UTC+11, Riz wrote:
>
> @TiddlyTweeter wrote:
>>
>> Ciao Riz
>>
>> Some time ago you made for me a neat system (later refined by Mark S.) 
>> which auto-adds tags based on save on IN-LINE words.
>>
>> The specific use-case was I post to #Twitter. Any in-line #hastagged word 
>> would get auto added as a tag to a Tiddler on save. Very neat. For those I 
>> never need to manually add tags.
>>
>> And I think that is part of the issue here in this thread. Efficiency of 
>> use. 
>>
>> TW is unusual that taggery is (1) about many dimensions of usage; (2) 
>> very flexible in practical usage.
>>
>> Best wishes
>> Josiah
>>
>
> I am glad it came handy.
>
> sincerely, 
> Riz
>

-- 
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/cf5a5a94-fbe0-4698-ada4-edc08e9d627c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] problem with authenitication on nodejs with 5.1.18

[Donald Coates]

Thank you so much for all you do and for the reply - it's nice to know!!  
For anyone else having problems - my workaround:

I use tmux inside the docker container to start two instances of the nodejs 
server using the same wiki folder (obviously) but having two ports - one 
with the 'anon' and one without.  When I want to make changes I just spin 
up the non reader - 'admin' - server, make changes, then restart the 
'reader' server and the changes are there.

There have been a few times where, after I sign in to the 'admin' server, 
the 'reader' server will then log me in and allow additions but if I clear 
my browser it goes back to 'reader' mode.



On Sunday, December 16, 2018 at 12:43:56 PM UTC-5, Jeremy Ruston wrote:
>
> Hi Donald
>
> Thanks, I’m afraid this turns out to be a bug introduced late in v5.1.18:
>
> https://github.com/Jermolene/TiddlyWiki5/issues/3647
>
> I’ll include a fix as part of v5.1.19 shortly,
>
> Best wishes
>
> Jeremy
>
> On 16 Dec 2018, at 11:39, Donald Coates > 
> wrote:
>
> Hello all and thank you for all your hard work!
>
> I am running tiddlywiki 5.1.18 on node inside docker.  when I start the 
> server with 
> tiddlywiki myserver --listen host=0.0.0.0 port=9067 "readers=(anon)" 
> writers=joe username=joe password=joe
>
> I am taken to the appropriate page without the ability to add a tiddler or 
> make changes.  When I force a login with /login/basic the prompt 
> comes up and validates, however I am never given the ability to make 
> changes.
>
> When I start the server without the 'readers' parameter I am prompted for 
> authentication and taken to the correct page and am able to add changes 
> which are persistent with restarts.
>
> Thank you in advance for any advice.  A simple workaround has been to have 
> two servers running off different ports in the same folder; one with the 
> readers parameter and one without.  But it would be nice to know if there 
> is a way to use it as intended.
>
> -- 
> 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+...@googlegroups.com .
> To post to this group, send email to tiddl...@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/382c160e-18d7-44f6-b5e0-461178b64c33%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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/fde68d67-3545-496a-9018-8b7b4ffdd7db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Searching Tiddlers with transcluded content

[TonyM]

Mark,

Love it.

If as I hope Bimlas's Kin operator becomes part of the core, you could use 
the kin operator to find the parents of this "backlinks" field, or for that 
matter any other kin relationship. The field should be a title list 
allowing multiple references such that if transcluded in more than one 
place the second and subsequent references will be appended to the 
"backlinks" field.

You could also use tiddler-citations as a toc structure to picture the 
relationships

My Black hat, What happens if the transcludion, reference is removed after 
the citation link is created?

PS I do nit recommend the field-name backlinks as it has other meanings 
that it will not live up to or confuse. Perhaps tiddler-citation(s) and we 
could build other manual interlinks or tools around this.

Regards
Tony

On Monday, December 17, 2018 at 11:22:06 AM UTC+11, Mark S. wrote:
>
>
> Idea #665
>
> Modify excision so that when the new tiddler is made, it has a "backlinks" 
> field pointing to the tiddler from which it was excised. Modify the search 
> routine to add the backlinks field to the output list. Possibly each time 
> an excision occurs, add to the backlinks field, so all tiddlers leading to 
> the original text end up in the final list.
>
> -- Mark  
>

-- 
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/240b97ea-5fa0-4f21-a446-0eaf76115d9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Autonumbering

[TonyM]

Olegh,

That looks good and it should be practical in many cases?

Tony

On Thursday, December 13, 2018 at 2:24:32 AM UTC+11, oleghbond wrote:
>
> Having based on the core macros:
>
> <>
>
> I redesigned macros for setting (anchoring), showing (referencing) and 
> listing artifacts:
>
> <>
> <>
> <>
>
> All tiddlers are packed and attached as a single JSON file.
>
> Within a single tiddler almost every thing works fine, except the showing 
> is prior the setting (in this case the reference is unknown).
>
> Similar drawback (the reference is unknown) when the setting is done in 
> another tiddler (without <>).
>
> So far the set of macros looks promising. However, to manage the situation 
> understanding of core JS programming (deeper than mine) is needed. 
>
> Olegh
>
> четвер, 6 грудня 2018 р. 19:09:54 UTC+2 користувач Mohammad написав:
>>
>> Is there any reference or experience using auto-numbering for captions in 
>> TW?
>>
>> I mean when you insert images with captions in a tiddler, TW number them?
>>
>>
>> --Mohammad
>>
>

-- 
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/a932f59f-65eb-4b34-8e0b-fd96995957d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Searching Tiddlers with transcluded content

['Mark S.' via TiddlyWiki]

Idea #665

Modify excision so that when the new tiddler is made, it has a "backlinks" 
field pointing to the tiddler from which it was excised. Modify the search 
routine to add the backlinks field to the output list. Possibly each time 
an excision occurs, add to the backlinks field, so all tiddlers leading to 
the original text end up in the final list.

-- Mark  

-- 
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/30c9507e-67c5-46aa-b379-1b5e07946403%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Autonumbering

[TonyM]

Olegh,

See the tabbed internal 
TOC, 
https://tiddlywiki.com/#Example%20Table%20of%20Contents%3A%20Tabbed%20Internal 
defined here $:/core/macros/toc

The above provides some background to marks helpful example 
outlier 
https://groups.google.com/forum/#!msg/tiddlywiki/ol_3zvGPbk8/-EdORwtrBAAJ

The thing to note is the TOC macro can be  passed a Template The  view 
template is default, but you could build your own (possibly cloning the 
existing one) to alter what is presented in the right hand side of the TOC 
internal nave pain.

This is a quick answer, feel free to ask more.

Regards
Tony
 



On Monday, December 17, 2018 at 6:03:04 AM UTC+11, oleghbond wrote:
>
> Tony,
>
> I'd be interested to have a look at your modified TOC approach. 
>
> It is also my understanding that AUTOREF has to be based on passing all 
> the tiddlers involved according to the TOC order. But instead of revealing 
> the tiddler titles (as TOC does) AUTOREF has to build indexes of artifacts 
> for each artifact type.
>
> Thanks.
>
> Olegh
>
> неділя, 16 грудня 2018 р. 02:12:00 UTC+2 користувач TonyM написав:
>>
>> Thomas,
>>
>> I have already done something like this based on "outlier" and or the toc 
>> internal navigation by providing an alternate viewtemplate to display 
>> tiddlers.
>>
>> 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 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/3bd86fce-143c-4962-8e60-6d185e77cc43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Searching Tiddlers with transcluded content

[TonyM]

Folks,

Speculation

Would it be posible to export a fully wikified tiddlywiki to a file, a bit like 
an index file, then use search in that file to identify the target tiddlers 
with rendered content? Is the static html version like this?

Now somehow intergrate this with the original wiki so that the above process is 
somewhat hidden from users? Perhaps even in an iframe, in which you can see the 
rendered content and search results with a way to open tiddlers in the main 
wiki.

A solution like this could also assist search engin optimisation for rendered 
content, perhaps with links to the main wiki.

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 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/59a0ce4f-d6d6-442a-b14f-149f15a7a089%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Searching Tiddlers with transcluded content

[Jeremy Ruston]

Hi Mark

> Running it all the time would be resource-intensive, for sure.
> 
> But what about a tool that renders all the tiddlers ON DEMAND with a title 
> like $:/rendered/ with a tag "rendered" and the original title in the 
> caption field. Before the tools runs, it would delete existing items tagged 
> as "rendered".  The search engine would display the original title and link 
> of any item marked as "rendered". So to a user it would feel like they're 
> finding everything, including transcluded text. And of course, the rendered 
> tiddlers could be deleted whenever needed to improve performance. 

I think that’s equivalent to my suggestion of restricting the search to a 
subset of tiddlers combined with something equivalent to our existing caching 
mechanism. We already cache the results of parsing tiddlers, and we could reuse 
the same mechanism to cache the wikified tiddlers. The trouble is that caching 
is of limited value cache invalidation would be very hard. The current refresh 
mechanism doesn’t work at the level of a whole tiddler, it works at the level 
of a node in the render tree. In order to find out whether a cached rendered 
tiddler needed re-rendering we’d have to run the refresh process over its 
render tree. In fact, right now things would actually work more efficiently by 
rendering all the tiddlers direct to the DOM, and then searching via the DOM 
(ie using the browser search).

Best wishes

Jeremy

> 
> -- Mark
> 
> On Sunday, December 16, 2018 at 11:30:28 AM UTC-8, Jeremy Ruston wrote:
>> I'm wondering whether an option could be added to the search operator 
>> allowing to search a "wikified" version of the text (or the field) of a 
>> tiddler.
> 
> It's an interesting idea, and I'm sure worth some experimentation but there 
> is a substantial performance issue in having to wikify all tiddlers before 
> every search operation.
> 
> The closest thing we've got at the moment is the orphan and missing filters 
> which have to parse every tiddler in order to gather all the explicit links. 
> Accessing the Missing and Orphans tabs is very slow on big wikis because of 
> that parsing overhead.
> 
> Adding the overhead of rendering on top of parsing would be a lot slower, in 
> some cases several orders of magnitude slower. Some tiddlers are inherently 
> slow to render, and we'd probably need a way to exclude them from the search, 
> or restrict the search to tiddlers of interest.
> 
> Best wishes
> 
> Jeremy
> 
>> The change in the code could be in the search function that lives in 
>> wiki.js. The field that is to be searched could be wikified before the 
>> search according to an option or a field value for this particular tiddler.
>> 
>> I believe there should be more tools to manage transclusions as 
>> transclusions are an ordinary way to organize knowledge in TW. I feel 
>> sometimes that :
>> - on one hand we don't have "sections" anymore (I was a fan of sections in 
>> TWC) and so we have to cut information into small pieces and use 
>> transclusions. And I'm fine with that.
>> - but on the other hand we don't have many tools to deal with transclusions.
>> 
>> A search with wikified content could be such a tool.
>> 
>> Regards
>> 
>> FrD
>> 
>> Le vendredi 14 décembre 2018 19:23:28 UTC+1, S. S. a écrit :
>> Emily, there was a discussion some months ago which may shed some (very dim) 
>> light : Backlinking' transclusions ? 
>> 
>> 
>> 
>> The rest of this is not an answer - just some thoughts relating to the 
>> question.
>> 
>> As I create more and more "written" material, I keep running against this 
>> "smallest semantic unit" - and "small tiddlers re-used by transclusion."
>> 
>> My constant concern is, when I want to find that "written" material, will I 
>> be able to find it in its proper context (with the other main material of 
>> which it is a part) - quickly, easily, and without fail.
>> 
>> For example, I take an excerpt of a few paragraphs from a book by one author 
>> and put it in a tiddler. Within that excerpt is a quote from another book 
>> with another author. If I put the quote in a second tiddler and transclude 
>> it back into the first tiddler, I would need a way to know later, which 
>> tiddler has transcluded this second tiddler, as a search will find the quote 
>> in the second tiddler, but in itself, without its context, this quote is 
>> useless.
>> 
>> I may be able to find its place by searching for the literal " {{second 
>> tiddler}} ". But what if the transclusion is done by a macro, or 
>> <$transclude .../>, or <$list filter=" ... "/>
>> 
>> One solution would be to have a "related" field in the second tiddler (or 
>> maybe first tiddler?) that is manually updated each time it is transcluded, 
>> but this is more cumbersome to do than first imagined.***See the note below
>> 
>> To avoid this happening, whenever I have material that I expect may need to 
>> be searched for and 

Re: [tw5] Re: Searching Tiddlers with transcluded content

['Mark S.' via TiddlyWiki]

Running it all the time would be resource-intensive, for sure.

But what about a tool that renders all the tiddlers ON DEMAND with a title 
like $:/rendered/ with a tag "rendered" and the original title in 
the caption field. Before the tools runs, it would delete existing items 
tagged as "rendered".  The search engine would display the original title 
and link of any item marked as "rendered". So to a user it would feel like 
they're finding everything, including transcluded text. And of course, the 
rendered tiddlers could be deleted whenever needed to improve performance. 

-- Mark

On Sunday, December 16, 2018 at 11:30:28 AM UTC-8, Jeremy Ruston wrote:
>
> I'm wondering whether an option could be added to the search operator 
> allowing to search a "wikified" version of the text (or the field) of a 
> tiddler.
>
>
> It's an interesting idea, and I'm sure worth some experimentation but 
> there is a substantial performance issue in having to wikify all tiddlers 
> before every search operation.
>
> The closest thing we've got at the moment is the orphan and missing 
> filters which have to parse every tiddler in order to gather all the 
> explicit links. Accessing the Missing and Orphans tabs is very slow on big 
> wikis because of that parsing overhead.
>
> Adding the overhead of rendering on top of parsing would be a lot slower, 
> in some cases several orders of magnitude slower. Some tiddlers are 
> inherently slow to render, and we'd probably need a way to exclude them 
> from the search, or restrict the search to tiddlers of interest.
>
> Best wishes
>
> Jeremy
>
> The change in the code could be in the search function that lives in 
> wiki.js. The field that is to be searched could be wikified before the 
> search according to an option or a field value for this particular tiddler.
>
> I believe there should be more tools to manage transclusions as 
> transclusions are an ordinary way to organize knowledge in TW. I feel 
> sometimes that :
> - on one hand we don't have "sections" anymore (I was a fan of sections in 
> TWC) and so we have to cut information into small pieces and use 
> transclusions. And I'm fine with that.
> - but on the other hand we don't have many tools to deal with 
> transclusions.
>
> A search with wikified content could be such a tool.
>
> Regards
>
> FrD
>
> Le vendredi 14 décembre 2018 19:23:28 UTC+1, S. S. a écrit :
>>
>> Emily, there was a discussion some months ago which may shed some (very 
>> dim) light : Backlinking' transclusions ? 
>> 
>>
>> --
>>
>> The rest of this is not an answer - just some thoughts relating to the 
>> question.
>>
>> As I create more and more "written" material, I keep running against this 
>> "smallest semantic unit" - and "small tiddlers re-used by transclusion."
>>
>> My constant concern is, when I want to find that "written" material, will 
>> I be able to find it in its proper context (with the other main material of 
>> which it is a part) - quickly, easily, and without fail.
>>
>> For example, I take an excerpt of a few paragraphs from a book by one 
>> author and put it in a tiddler. Within that excerpt is a quote from another 
>> book with another author. If I put the quote in a second tiddler and 
>> transclude it back into the first tiddler, I would need a way to know 
>> later, which tiddler has transcluded this second tiddler, as a search will 
>> find the quote in the second tiddler, but in itself, without its context, 
>> this quote is useless.
>>
>> I may be able to find its place by searching for the literal " {{second 
>> tiddler}} ". But what if the transclusion is done by a macro, or 
>> <$transclude .../>, or <$list filter=" ... "/>
>>
>> One solution would be to have a "related" field in the second tiddler (or 
>> maybe first tiddler?) that is manually updated each time it is transcluded, 
>> but this is more cumbersome to do than first imagined.***See the note 
>> below
>>
>> To avoid this happening, whenever I have material that I expect may need 
>> to be searched for and found within its proper context - and I cannot find 
>> a way to "safely" transclude it - I do not separate it into a smaller unit. 
>> I keep it within its context no matter how big the tiddler becomes.
>>
>> I have a feeling this philosophy I am using is inherently wrong. Perhaps 
>> one day I will understand a better way of doing it.
>>
>>
>>
>> *** Note:
>> Automagically keeping track of related tiddlers 
>> 
>> Handling Changing Relationships Between Tiddlers 
>> 
>>
>> -- 
> 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+...@googlegroups.com .
> To post to this group, send 

Re: [tw5] Re: Searching Tiddlers with transcluded content

[Jeremy Ruston]

> I'm wondering whether an option could be added to the search operator 
> allowing to search a "wikified" version of the text (or the field) of a 
> tiddler.

It's an interesting idea, and I'm sure worth some experimentation but there is 
a substantial performance issue in having to wikify all tiddlers before every 
search operation.

The closest thing we've got at the moment is the orphan and missing filters 
which have to parse every tiddler in order to gather all the explicit links. 
Accessing the Missing and Orphans tabs is very slow on big wikis because of 
that parsing overhead.

Adding the overhead of rendering on top of parsing would be a lot slower, in 
some cases several orders of magnitude slower. Some tiddlers are inherently 
slow to render, and we'd probably need a way to exclude them from the search, 
or restrict the search to tiddlers of interest.

Best wishes

Jeremy

> The change in the code could be in the search function that lives in wiki.js. 
> The field that is to be searched could be wikified before the search 
> according to an option or a field value for this particular tiddler.
> 
> I believe there should be more tools to manage transclusions as transclusions 
> are an ordinary way to organize knowledge in TW. I feel sometimes that :
> - on one hand we don't have "sections" anymore (I was a fan of sections in 
> TWC) and so we have to cut information into small pieces and use 
> transclusions. And I'm fine with that.
> - but on the other hand we don't have many tools to deal with transclusions.
> 
> A search with wikified content could be such a tool.
> 
> Regards
> 
> FrD
> 
> Le vendredi 14 décembre 2018 19:23:28 UTC+1, S. S. a écrit :
>> 
>> Emily, there was a discussion some months ago which may shed some (very dim) 
>> light : Backlinking' transclusions ?
>> 
>> 
>> The rest of this is not an answer - just some thoughts relating to the 
>> question.
>> 
>> As I create more and more "written" material, I keep running against this 
>> "smallest semantic unit" - and "small tiddlers re-used by transclusion."
>> 
>> My constant concern is, when I want to find that "written" material, will I 
>> be able to find it in its proper context (with the other main material of 
>> which it is a part) - quickly, easily, and without fail.
>> 
>> For example, I take an excerpt of a few paragraphs from a book by one author 
>> and put it in a tiddler. Within that excerpt is a quote from another book 
>> with another author. If I put the quote in a second tiddler and transclude 
>> it back into the first tiddler, I would need a way to know later, which 
>> tiddler has transcluded this second tiddler, as a search will find the quote 
>> in the second tiddler, but in itself, without its context, this quote is 
>> useless.
>> 
>> I may be able to find its place by searching for the literal " {{second 
>> tiddler}} ". But what if the transclusion is done by a macro, or 
>> <$transclude .../>, or <$list filter=" ... "/>
>> 
>> One solution would be to have a "related" field in the second tiddler (or 
>> maybe first tiddler?) that is manually updated each time it is transcluded, 
>> but this is more cumbersome to do than first imagined.***See the note below
>> 
>> To avoid this happening, whenever I have material that I expect may need to 
>> be searched for and found within its proper context - and I cannot find a 
>> way to "safely" transclude it - I do not separate it into a smaller unit. I 
>> keep it within its context no matter how big the tiddler becomes.
>> 
>> I have a feeling this philosophy I am using is inherently wrong. Perhaps one 
>> day I will understand a better way of doing it.
>> 
>> 
>> 
>> *** Note:
>> Automagically keeping track of related tiddlers
>> Handling Changing Relationships Between Tiddlers
>> 
> 
> -- 
> 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/3062125d-37ee-4d19-a601-b306db345141%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/94C16F92-05BA-4C26-BEE1-114874A80643%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Css Stylesheet for table: Background-color for only specific cells

['Surya' via TiddlyWiki]

Hi Tony, Mohammad & Ton,
sorry for my late answer...

I think, I mean a different thing.
I *don't* have a "normal" static table like 
|head1|head2|head3|
|cell1|cell2|cell3|


*But I generated a table with the formula plugin 
(https://evanbalster.com/tiddlywiki/formulas.html 
).*
The table-tiddler is:

\define formulaFixed() 2
\define ss_cols() A B C D E F G H I J
\define ss_rows() 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
\define ss_cell() $(c)$$(r)$

<$tiddler tiddler="Spreadsheet/Data My table">



<$vars popupState=<> popupCell=<> >

<$reveal type="popup" state=<> >


<$set name="cell" filter="[titleget[text]]">
''<>'': <$edit-text tag=input index=<> size=150 />
<$button 
class="tc-btn-invisible">{{$:/core/images/save-button}}<$action-setfield 
$tiddler=<> text=""/>






<$list variable=c filter=<> ><>
<$list variable=r filter=<> >

<>
<$list variable=c filter=<> >
<$button popup=<> style=
"width:100%;margin:0;padding:6px;display:block;background:none;border:none;cursor:pointer;"
><$action-setfield $tiddler=<> text=<>/> <$formula 
formula=<>/>
















It is styled with a Stylesheet-tiddler like this (only a little bit of the 
stylesheet-tiddler copied, just to show how):

.my-table th:nth-child(11),
.rezepterechner-table td:nth-child(1) {
  background-color:white;font-size:0.5em;
}

.my-table td:nth-child(3) {
  background-color:#ffa366;
}

.my-table tr:nth-child(1) {
  font-weight:bold;
}



Now it looks like (a screenshot is -because of a lot of rows- too big I 
think and in german, so I show it like this and just as an example):

|*header1*|*header2*|*header3*|*head**er4*|*head**er5*|*head**er6*|
|cell1|cell2|cell3|cell4|cell5|cell6|
|cell11|cell12|cell13|cell14|cell15|cell16|
|cell21|cell22|cell23|cell24|cell25|cell26|
|*cell31*|*cell32*|*cell33*|*cell34*|*cell35*|*cell36*| >this row is styled 
to be green. But it is overwritten from the styled columns (2, 3, 5 & 6), 
so only the not-styled cells are green)
|*cell41*|*cell42*|*cell43*|*cell44*|*cell45*|*cell46*| >this row is styled 
to be orange. But it is overwritten from the styled columns (2, 3, 5 & 6), 
so only the not-styled cells are orange)



But it should look like this:

|*header1*|*header2*|*header3*|*head**er4*|*head**er5*|*head**er6*|
|cell1|cell2|cell3|cell4|cell5|cell6|
|cell11|cell12|cell13|cell14|cell15|cell16|
|cell21|cell22|cell23|cell24|cell25|cell26|
|*cell31*|cell32|*cell33*|cell34|cell35|cell36|
|*cell41*|cell42|*cell43*|cell44|cell45|cell46|

Do you understand, what I mean??
Any help??? Pleeeaaase... :-)
Surya

-- 
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/f7e90378-081d-47dc-9bfd-16c5cf7530bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Autonumbering

[oleghbond]

Tony,

I'd be interested to have a look at your modified TOC approach. 

It is also my understanding that AUTOREF has to be based on passing all the 
tiddlers involved according to the TOC order. But instead of revealing the 
tiddler titles (as TOC does) AUTOREF has to build indexes of artifacts for 
each artifact type.

Thanks.

Olegh

неділя, 16 грудня 2018 р. 02:12:00 UTC+2 користувач TonyM написав:
>
> Thomas,
>
> I have already done something like this based on "outlier" and or the toc 
> internal navigation by providing an alternate viewtemplate to display 
> tiddlers.
>
> 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 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/e5a34583-a650-451d-a018-5f35fe41144d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Different link actions; when in Story River; within Tabbed Internal Table of Contents; possible?

[Mohammad]

Hi S.S
Look at 
https://kookma.github.io/Reveal-Gradually/

See how wizard and steps work!
To see a smooth navigation set animation duration in control panel to zero.

BTW, I want to thank you for your great efforts on beginner guide!

- Mohammad

On Sunday, December 16, 2018 at 7:42:56 PM UTC+3:30, S. S. wrote:
>
> Ha! You're right of course. I did not notice! The scrolling out of the ToC 
> tiddler threw me. Thank you.
> I wonder how a beginner will deal with that. Will it confuse them too? I 
> don't know.
>
> I also notice now that EVERY link clicked in tiddlers in theToC's  view 
> pane - opens within the view pane.
> What effect will that have on a beginner? I don't know.
>
> I will sleep on it.
>
> Cheers.
>
> On Sunday, December 16, 2018 at 10:52:24 PM UTC+7, BurningTreeC wrote:
>>
>> Coming back again :o)
>>
>> I believe we've both been mislead by the scrolling behavior of the story 
>> river
>>
>> try closing all tiddlers but the one containing the ToC - I think your 
>> links work well! 
>>
>

-- 
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/7e538758-8a0e-47a6-9138-c4398989169f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tagging --- Organise From Serendipity

[Riz]

@TiddlyTweeter wrote:
>
> Ciao Riz
>
> Some time ago you made for me a neat system (later refined by Mark S.) 
> which auto-adds tags based on save on IN-LINE words.
>
> The specific use-case was I post to #Twitter. Any in-line #hastagged word 
> would get auto added as a tag to a Tiddler on save. Very neat. For those I 
> never need to manually add tags.
>
> And I think that is part of the issue here in this thread. Efficiency of 
> use. 
>
> TW is unusual that taggery is (1) about many dimensions of usage; (2) very 
> flexible in practical usage.
>
> Best wishes
> Josiah
>

I am glad it came handy.

sincerely, 
Riz

-- 
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/f01275d5-3629-465a-b568-ada6c13d63cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Searching Tiddlers with transcluded content

[FrD]

Hi,

I'm wondering whether an option could be added to the search operator 
allowing to search a "wikified" version of the text (or the field) of a 
tiddler.
The change in the code could be in the search function that lives in 
wiki.js. The field that is to be searched could be wikified before the 
search according to an option or a field value for this particular tiddler.

I believe there should be more tools to manage transclusions as 
transclusions are an ordinary way to organize knowledge in TW. I feel 
sometimes that :
- on one hand we don't have "sections" anymore (I was a fan of sections in 
TWC) and so we have to cut information into small pieces and use 
transclusions. And I'm fine with that.
- but on the other hand we don't have many tools to deal with transclusions.

A search with wikified content could be such a tool.

Regards

FrD

Le vendredi 14 décembre 2018 19:23:28 UTC+1, S. S. a écrit :
>
> Emily, there was a discussion some months ago which may shed some (very 
> dim) light : Backlinking' transclusions ? 
> 
>
> --
>
> The rest of this is not an answer - just some thoughts relating to the 
> question.
>
> As I create more and more "written" material, I keep running against this 
> "smallest semantic unit" - and "small tiddlers re-used by transclusion."
>
> My constant concern is, when I want to find that "written" material, will 
> I be able to find it in its proper context (with the other main material of 
> which it is a part) - quickly, easily, and without fail.
>
> For example, I take an excerpt of a few paragraphs from a book by one 
> author and put it in a tiddler. Within that excerpt is a quote from another 
> book with another author. If I put the quote in a second tiddler and 
> transclude it back into the first tiddler, I would need a way to know 
> later, which tiddler has transcluded this second tiddler, as a search will 
> find the quote in the second tiddler, but in itself, without its context, 
> this quote is useless.
>
> I may be able to find its place by searching for the literal " {{second 
> tiddler}} ". But what if the transclusion is done by a macro, or 
> <$transclude .../>, or <$list filter=" ... "/>
>
> One solution would be to have a "related" field in the second tiddler (or 
> maybe first tiddler?) that is manually updated each time it is transcluded, 
> but this is more cumbersome to do than first imagined.***See the note 
> below
>
> To avoid this happening, whenever I have material that I expect may need 
> to be searched for and found within its proper context - and I cannot find 
> a way to "safely" transclude it - I do not separate it into a smaller unit. 
> I keep it within its context no matter how big the tiddler becomes.
>
> I have a feeling this philosophy I am using is inherently wrong. Perhaps 
> one day I will understand a better way of doing it.
>
>
>
> *** Note:
> Automagically keeping track of related tiddlers 
> 
> Handling Changing Relationships Between Tiddlers 
> 
>
>

-- 
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/3062125d-37ee-4d19-a601-b306db345141%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] problem with authenitication on nodejs with 5.1.18

[Jeremy Ruston]

Hi Donald

Thanks, I’m afraid this turns out to be a bug introduced late in v5.1.18:

https://github.com/Jermolene/TiddlyWiki5/issues/3647

I’ll include a fix as part of v5.1.19 shortly,

Best wishes

Jeremy

> On 16 Dec 2018, at 11:39, Donald Coates  wrote:
> 
> Hello all and thank you for all your hard work!
> 
> I am running tiddlywiki 5.1.18 on node inside docker.  when I start the 
> server with 
> tiddlywiki myserver --listen host=0.0.0.0 port=9067 "readers=(anon)" 
> writers=joe username=joe password=joe
> 
> I am taken to the appropriate page without the ability to add a tiddler or 
> make changes.  When I force a login with /login/basic the prompt 
> comes up and validates, however I am never given the ability to make changes.
> 
> When I start the server without the 'readers' parameter I am prompted for 
> authentication and taken to the correct page and am able to add changes which 
> are persistent with restarts.
> 
> Thank you in advance for any advice.  A simple workaround has been to have 
> two servers running off different ports in the same folder; one with the 
> readers parameter and one without.  But it would be nice to know if there is 
> a way to use it as intended.
> 
> -- 
> 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/382c160e-18d7-44f6-b5e0-461178b64c33%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/AC7F47F1-98CA-4D43-BEF6-848F921925E6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Is there a problem using $message="tm-edit-tiddler" in a modal?

[Jan]

Hi Simon,
thanks a lot, what enormous speed...and it works perfect.
It is interesting that now to close the modal with the tm-close-tiddler 
with the same click, this commant has to be outside:


<$button>
<$navigator story="$:/StoryList" history="$:/HistoryList">
<$action-navigate $to={{$:/temp/patternname}}/>
<$action-sendmessage $message="tm-edit-tiddler" 
$param={{$:/temp/patternname}}/>

selber machen

<$action-sendmessage $message="tm-close-tiddler"/>


Thanks again,
Jan




Am 16.12.2018 um 17:09 schrieb BurningTreeC:


|
<$navigator story="$:/StoryList" history="$:/HistoryList">


<$button>
<$action-navigate $to={{$:/temp/patternname}}/>
<$action-sendmessage $message="tm-edit-tiddler"
$param={{$:/temp/patternname}}
/>
<$action-sendmessage $message="tm-close-tiddler"/>
selber machen


|


--
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/5C167FB4.9020003%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Different link actions; when in Story River; within Tabbed Internal Table of Contents; possible?

[S. S.]

Ha! You're right of course. I did not notice! The scrolling out of the ToC 
tiddler threw me. Thank you.
I wonder how a beginner will deal with that. Will it confuse them too? I 
don't know.

I also notice now that EVERY link clicked in tiddlers in theToC's  view 
pane - opens within the view pane.
What effect will that have on a beginner? I don't know.

I will sleep on it.

Cheers.

On Sunday, December 16, 2018 at 10:52:24 PM UTC+7, BurningTreeC wrote:
>
> Coming back again :o)
>
> I believe we've both been mislead by the scrolling behavior of the story 
> river
>
> try closing all tiddlers but the one containing the ToC - I think your 
> links work well! 
>

-- 
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/13220b39-6178-47f6-9919-c640d25f6c4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Is there a problem using $message="tm-edit-tiddler" in a modal?

[BurningTreeC]

Hi Jan, Jeremy recently mentioned that this worked before, without adding 
anything...

but at the moment, you'd need to add a navigator widget pointing to the 
story and history:

<$navigator story="$:/StoryList" history="$:/HistoryList">


<$button> 
<$action-navigate $to={{$:/temp/patternname}}/> 
<$action-sendmessage $message="tm-edit-tiddler" 
$param={{$:/temp/patternname}}
/> 
<$action-sendmessage $message="tm-close-tiddler"/> 
selber machen 
 




Hello, 
> I made a modal with a button which is using the widget message 
> tm-edit-tiddler. 
>
> <$button> 
> <$action-navigate $to={{$:/temp/patternname}}/> 
> <$action-sendmessage $message="tm-edit-tiddler" 
> $param={{$:/temp/patternname}}/> 
> <$action-sendmessage $message="tm-close-tiddler"/> 
> selber machen 
>  
>
> It works in the storyriver but not in the modal. Can anybody tell why 
> this is so? 
>
> Yours Jan 
>

-- 
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/5993eb31-b88f-4d24-b507-e92d026176b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Is there a problem using $message="tm-edit-tiddler" in a modal?

[Jan]

Hello,
I made a modal with a button which is using the widget message 
tm-edit-tiddler.


<$button>
<$action-navigate $to={{$:/temp/patternname}}/>
<$action-sendmessage $message="tm-edit-tiddler" 
$param={{$:/temp/patternname}}/>

<$action-sendmessage $message="tm-close-tiddler"/>
selber machen


It works in the storyriver but not in the modal. Can anybody tell why 
this is so?


Yours Jan

--
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/5C16.3020900%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Different link actions; when in Story River; within Tabbed Internal Table of Contents; possible?

[BurningTreeC]

Coming back again :o)

I believe we've both been mislead by the scrolling behavior of the story 
river

try closing all tiddlers but the one containing the ToC - I think your 
links work well! 

-- 
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/fe983b9b-8f59-45de-9784-fb30011039c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Different link actions; when in Story River; within Tabbed Internal Table of Contents; possible?

[BurningTreeC]

Hi, coming back to this - I've realized it's much easier!

The toc-tabbed-internal-nav macro catches navigation messages so that links 
are opened within the ToC

I changed your Next-link to a button:

<$button class="tc-btn-invisible tc-tiddlylink"actions="""<$action-navigate 
$to="Some of the things you can do with ~TiddlyWiki"/>""">Some of the 
things you can do with TiddlyWiki

... and internal navigation works :)

-- 
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/348048f7-63e2-41b3-9993-79c5c1678e41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Different link actions; when in Story River; within Tabbed Internal Table of Contents; possible?

[BurningTreeC]

Hi S.S.


> Some weeks back, I began working on a tutorial for tiddlywiki.com's 
> documentation to show beginners how to make a Table of Contents. To do this 
> effectively, I realized quite a few other concepts and info need to be 
> presented at a beginners' level. 
>
> I have this feeling that an effective way of presenting this beginner 
> level information is within a *Tabbed Internal Table of Contents* named 
> *Beginners* – that is separate from TW's present *TableOfContents*.
>
> If I have a tiddler tagged *Beginner* being viewed in the normal Story 
> River, a link at the bottom of that tiddler that suggests the next 
> tiddler to read – will properly open the next tiddler in the normal Story 
> River. 
>
> DIFFICULTY: However if that tiddler is viewed *INSIDE* the ToC - that 
> link would cause the next tiddler to open *OUTSIDE* the ToC's view pane, 
> and thus disrupt the flow of reading one tiddler after another in the ToC 
> view pane.
>
> I would like that link to *behave differently* in the ToC or *not appear 
> at all*.
>
> So at the moment I can see two choices.
>
> CHOICE: 1) The link at the bottom should behave differently depending 
> where the tiddler is opened. If in the story river, it behaves normally. If 
> in the ToC, it should have the same action as clicking a ToC link - open 
> that linked-to-tiddler inside the ToC's view panel.
>
> CHOICE:2) The link should not show up at all when the tiddler is displayed 
> within the ToC - navigation purely from the ToC list of links.
>

You can influence navigation behavior using the <$navigator> widget. If you 
wrap your ToC within such a widget, you can decide in which list the 
navigated tiddlers are opened

for example:

<$navigator story="$:/TocStoryList1" history="$:/TocHistoryList1">


your ToC




Now your links won't be opened in the story River anymore, and as you will 
notice, they aren't opened anywhere.

To show them somewhere, you'll need to put a list where you want them to be 
shown. Try the following somewhere, maybe in another tiddler:

<$list filter="[list[$:/TocStoryList1]]" 
template="$:/core/ui/ViewTemplate/body" storyview="classic"/>

The easiest thing would be to put this line above/below your ToC

The ToC could probably be modified to have such a list for each ToC-section 
and subsection and to display the list within that section, but that won't 
be that easy


> You can see what is meant in the first 6 ToC links here: Tabbed Internal 
> Table of Contents for Beginners 
> 
>
> I would appreciate some suggestions and help!
>
>

-- 
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/24ddaa7a-7ab1-4c44-9953-748e625b5868%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Different link actions; when in Story River; within Tabbed Internal Table of Contents; possible?

[S. S.]

Some weeks back, I began working on a tutorial for tiddlywiki.com's 
documentation to show beginner's how to make a Table of Contents. To do 
this effectively, I realized quite a few other concepts and info need to be 
presented at a beginner's level. 

I have this feeling that an effective way of presenting this beginner level 
information is within a *Tabbed Internal Table of Contents* named 
*Beginners* – that is separate from TW's present *TableOfContents*.

If a tiddler tagged *Beginner* is viewed in the normal Story River, a link 
at the bottom of that tiddler that shows which is the next suggested 
tiddler to read – will properly open the next tiddler in the normal Story 
River. 

DIFFICULTY: However if that tiddler is viewed *INSIDE* the ToC - that link 
would cause the next tiddler to open *OUTSIDE* the ToC's view pane, and 
thus disrupt the flow of reading one tiddler after another in the ToC view 
pane.

I would like that link to *behave differently* in the ToC or *not appear at 
all*.

So at the moment I can see two choices.

CHOICE: 1) The link at the bottom should behave differently depending where 
the tiddler is opened. If in the story river, it behaves normally. If in 
the ToC, it should have the same action as clicking a ToC link - open that 
linked to tiddler internally in the ToC's view panel.

CHOICE:2) The link should not show up at all when the tiddler is displayed 
within the ToC - navigation purely from the ToC list of links.

You can see what is meant in the first 6 ToC links here: Tabbed Internal 
Table of Contents for Beginners 


I would appreciate some suggestions and help!

-- 
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/3566d7cb-2cb5-4f81-a1ae-877c0a14644e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tagging --- Organise From Serendipity

[@TiddlyTweeter]

Caro Bimlas

You recent work on "kin" is very interesting for how to emerge local, wiki 
specific workable TAXONOMIES.

In the root space of taggery history was I think a false debate between 
"flat" taggery (the main system used now on web) and "world-order" 
hierarchy taxonomy... dating back to the Renaissance.

TW is very interesting for enabling either.

What is my take-away message? Simply that you can make local functional 
taxonomies very well without having to deal with Grand Theory about the 
teleology of ultimate classifications. It DOES the job.

Josiah

On Saturday, 15 December 2018 20:30:01 UTC+1, bimlas wrote:
>
> I think that kind of logic is in the wrong direction. Two reasons: 
>
> * unnecessary complexities 
> * your brain does not work that way
>
> Unnecessary complexities
>
> The simpler, the more secure it works, the more straightforward, the more 
> usable. For now, you've listed 6 "tag categories", but in time I'm sure 
> more and more would be exists, it would be harder to keep in mind what 
> prefix to use, so before you apply a tag, you have to look at what mark to 
> use: this would not be a natural, obvious solution.
>
> Your brain does not work that way 
>
> What's the TiddlyWiki? Category? Topic? Keyword? According to this, it is 
> "standing over something," but in fact "subordinated to something" as well. 
> I have encountered many of these dilemmas too, so I was glad to get to know 
> the TiddlyWiki, where I can build the hierarchy of data in a number of ways.
> If we look at the "Notes Manager", the TiddlyWiki is subordinate to the 
> tag; if you look at the description of TiddlyWiki, it might be a 
> "category"; if you look at the list of wikis, it might be a "topic", so, in 
> my opinion, our brains do not explicitly differentiate between "words", but 
> look at their relationship. I think it is more appropriate to make a 
> toc-like hierarchy, or just as AlexHough says: group them into additional 
> tags, so a member (eg TiddlyWiki) can belong to several groups.
>

-- 
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/063426ad-9a60-4620-9e6b-f39a3af863e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tagging --- Organise From Serendipity

[@TiddlyTweeter]

Ciao Riz

Some time ago you made for me a neat system (later refined by Mark S.) 
which auto-adds tags based on save on IN-LINE words.

The specific use-case was I post to #Twitter. Any in-line #hastagged word 
would get auto added as a tag to a Tiddler on save. Very neat. For those I 
never need to manually add tags.

And I think that is part of the issue here in this thread. Efficiency of 
use. 

TW is unusual that taggery is (1) about many dimensions of usage; (2) very 
flexible in practical usage.

Best wishes
Josiah

On Sunday, 16 December 2018 10:19:59 UTC+1, Riz wrote:
>
>  S. S. wrote:
>
>>
>> So RANDOMLY - without putting much thought into what symbol to prefix the 
>> tags ...
>>
>> Keywords? How about starting those with : *#my-keyword*
>> Category? How about : *@my-category*
>> Topic? How about: *!topic*
>> Keeping track of excised data?: *^Parent-Tiddler-Name*
>> Groups? perhaps: *%my-group*
>> Styling tags? How about: **my-style*
>>
>> I just started thinking about this recently, so my insights are still in 
>> infancy.
>>
>>
> I like the way this discussion is shaping up. May be a plugin could be 
> written to ignore a set of  characters like "@", "#" etc appearing in the 
> begining of tag pill, so that user can use them safely to denote different 
> branches of their organization system.
>
> sincerely
> Riz
>

-- 
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/6dd30883-c76d-4c8a-bc92-8c85170b1698%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tagging --- Organise From Serendipity

[HansWobbe]

> I like the way this discussion is shaping up. May be a plugin could be 
> written to ignore a set of  characters like "@", "#" etc appearing in the 
> begining of tag pill, so that user can use them safely to denote different 
> branches of their organization system.
>
> sincerely
> Riz
>

It should be possible to use Prefix and Suffix operations to achieve this 
easily.  Effectively this could evolve into a pattern of
https://en.wikipedia.org/wiki/Sigil_(computer_programming) characters that 
might even be embedded in a particular Tag value or the Tittle or Caption, 
or might be given a specific Field.

~Hans

-- 
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/4e9b0062-8744-49a1-88f7-acce75909bf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Bob - Usage of "Save Plugin As Folder"

[Jed Carty]

The save plugin as a folder feature is still pretty experimental. I 
probably shouldn't have actually released it yet. I made that feature when 
I was planning on doing more work on it but then decided to take a break 
from the development instead and since I came back I have been focusing on 
privacy and other server features.

It sounds like you set up everything correctly and the problem is somewhere 
in my code and you are doing things correctly.

The only thing I can think of that may be a problem on your end is to make 
sure that the plugin is properly packaged, but I don't think that would 
cause your trouble.

Once I am finished with the server work I am doing now I can see about the 
other components like this.

-- 
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/721e387c-58e3-4cf4-8ba2-edc3bb0b6e92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Bob - Usage of "Save Plugin As Folder"

[AllanH]

Hi Jed

I'm a lurker that's just surfacing now.  I've recently started using the 
Bob plugin, which I really like - it seems like it will make a lot of 
things more convenient, and some others possible.  Thank you for your hard 
work on this and your willingness to share it.

I have several wikis, so managing the plugin collection across them all has 
been inconvenient.  The Bob plugin management facilities seem like they 
would be a perfect fit.  However, I'm having some problems with the 'Save 
Plugin As Folder' mechanism.

I have arranged my folders so that the various components are sibling 
sub-directories of a single folder (call it the Bob root).  The TiddlyWiki 
git checkout with an embedded git checkout of the Bob plugin forms one of 
these.  I have the IndexWiki folder as another sibling; I point to this as 
an argument to the node startup.  The settings.json file of the IndexWiki 
points to other siblings - the Plugins and Editions directories, and the 
folder that acts as the root for the file server (oluginsPath, editionsPath 
and filePathRoot respectively).  The wikis are held in the last sibling 
directory; these are pointed to by entries in the wikis section of 
settings.json.

I have set the value for the pluginLibrary key in the API section of 
settings.json to "yes".

When I attempt to use the 'Save Plugin As Folder' button from a wiki served 
by Bob, the expected structure for that plugin is created in my Plugins 
folder - i.e. a folder for the author, with a sub-directory for the 
particular plugin.  In the leaf folder, the expected files are created - a 
.info file for the plugin, and .tid files for the tiddlers of the plugin.  
The .info file has the expected contents.  The .tid files do not - they are 
all a single byte in length - a single linefeed (0x0a) character.

Could you give me some guidance as to what I may be doing wrong?

Thanks
Allan




-- 
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/2e7e80d2-4488-462b-8a75-5b2c21d7e480%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] problem with authenitication on nodejs with 5.1.18

[Donald Coates]

Hello all and thank you for all your hard work!

I am running tiddlywiki 5.1.18 on node inside docker.  when I start the 
server with 
tiddlywiki myserver --listen host=0.0.0.0 port=9067 "readers=(anon)" writers
=joe username=joe password=joe

I am taken to the appropriate page without the ability to add a tiddler or 
make changes.  When I force a login with /login/basic the prompt 
comes up and validates, however I am never given the ability to make 
changes.

When I start the server without the 'readers' parameter I am prompted for 
authentication and taken to the correct page and am able to add changes 
which are persistent with restarts.

Thank you in advance for any advice.  A simple workaround has been to have 
two servers running off different ports in the same folder; one with the 
readers parameter and one without.  But it would be nice to know if there 
is a way to use it as intended.

-- 
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/382c160e-18d7-44f6-b5e0-461178b64c33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Tagging --- Organise From Serendipity

[Riz]

 S. S. wrote:

>
> So RANDOMLY - without putting much thought into what symbol to prefix the 
> tags ...
>
> Keywords? How about starting those with : *#my-keyword*
> Category? How about : *@my-category*
> Topic? How about: *!topic*
> Keeping track of excised data?: *^Parent-Tiddler-Name*
> Groups? perhaps: *%my-group*
> Styling tags? How about: **my-style*
>
> I just started thinking about this recently, so my insights are still in 
> infancy.
>
>
I like the way this discussion is shaping up. May be a plugin could be 
written to ignore a set of  characters like "@", "#" etc appearing in the 
begining of tag pill, so that user can use them safely to denote different 
branches of their organization system.

sincerely
Riz

-- 
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/f11cd274-34b0-4720-8a2d-e833bd3b9426%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.