Re: [tw5] How to do plugin translations

2019-05-13 Thread Flibbles
So that looks like an interesting macro which addresses the problem of 
localization for now. Except it doesn't seem to answer the question of what 
the ultimate standard would become. Your macro encourages a "
*$:/i18n/language/title*" naming convention. That means language tiddlers 
inside my plugin would be named something like:

*$:/i18n/en-EN/plugin_vendor/plugin_name/Button/MyButton/Hint*

which not only doesn't conform with the 
*$:/plugins/plugin_vendor/plugin_name* convention, but steers farther away 
from what an ultimate convention would be.

Don't get me wrong. Your macro is definitely a solution to the problem. I'm 
just inquiring about what the ultimate solution will end up becoming.

-Flibbles

On Monday, May 13, 2019 at 12:44:54 AM UTC-4, SylvainComte wrote:
>
> Hello,
>
> You may find this thread on tiddlywikidev useful:
>
> https://groups.google.com/forum/#!topic/tiddlywikidev/fu0QFcs9O_U
>
> Cheers
>
> Sylvain
> @sycom
>
>

-- 
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/2378fd37-62a8-42d9-9761-5955c2dd99e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [tw5] How to do plugin translations

2019-05-14 Thread Flibbles
All right. So i18n can support whatever domain I configure it to, but then 
that brings me back to my original question. What would be the most 
appropriate domain to use.

*$:/plugins/vendor_name/plugin_name/...*

or

*$:/language/vendor_name/plugin_name/...*

Convention suggests the first, but the second makes more sense if you 
consider that plugin translations would be separate from the plugins, and 
it seems like it may be more appropriate for a final solution.

-Flibbles

On Tuesday, May 14, 2019 at 10:49:40 AM UTC-4, SylvainComte wrote:
>
> Just to be complete about this, see usage for Feather Icons Plugin 
> <http://sycom.gitlab.io/TiddlyWiki-Plugins/#Feather%20icons%20plugin>, 
> i18n tiddlers are
>
>- ...
>- $:/plugins/sycom/feather-icons/i18n/en-GB
>- $:/plugins/sycom/feather-icons/i18n/en-GB/macrosIntro
>- $:/plugins/sycom/feather-icons/i18n/en-GB/readme
>- $:/plugins/sycom/feather-icons/i18n/en-GB/usage
>- $:/plugins/sycom/feather-icons/i18n/fr-FR
>- $:/plugins/sycom/feather-icons/i18n/fr-FR/macrosIntro
>- $:/plugins/sycom/feather-icons/i18n/fr-FR/readme
>- $:/plugins/sycom/feather-icons/i18n/fr-FR/usage
>- ...
>
> cheers
>
> Sylvain
> @sycom
>
> Le mardi 14 mai 2019 11:00:44 UTC+2, SylvainComte a écrit :
>>
>> Hello,
>>
>> The behaviour is somewhat different with the domain parameter : your 
>> translations will be in 
>>
>> domain/i18n/lg-LG
>>
>> Default value is $:/ but it's up to you and might be 
>> $:/plugins/plugin_vendor/plugin_name and your translations will be in
>>
>> $:/plugins/plugin_vendor/plugin_name/i18n/lg-LG
>>
>> So it seems there's no conflict with your philosophy. But I guess 
>> documentation should be more explicit.
>>
>> Cheers
>>
>> Sylvain
>> @sycom
>>
>>

-- 
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/d78b838d-8594-442e-b5bc-d42b7259f884%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [tw5] How to do plugin translations

2019-05-12 Thread Flibbles
Hi Jeremy,

I'm looking into this too. While your response make good sense to me, I do 
have one question:

Given the mechanism of the $tw.Language module, and how plugin language 
translations could theoretically be separate from the plugins they're 
translating, wouldn't the most appropriate naming convention be:

*$:/language/plugin_vendor/plugin_name/...*

as opposed to: *$:/plugins/plugin_vendor/plugin_name/language/...*

I know it doesn't make a difference while plugin translations aren't 
supported, but I'd hate to have to redo my plugins after the fact, and it 
seems to me that the plugin translations would likely install in the "
*/languages*". Maybe for example: "
*/languages/plugin_vendor/plugin_name/fr-FR*"

or at least somewhere other than the plugins directory.

Feel free to tell me it doesn't matter. I'm one of those people who's 
pedantic to sticking to coding conventions perfectly.

Thanks,
-Flibbles





On Tuesday, November 20, 2018 at 4:36:35 AM UTC-5, Jeremy Ruston wrote:
>
> Hi Ilya
>
> I am completely lost with plugin translations.
>
>
> The core doesn’t currently support translations for plugins, I’m afraid. 
> That doesn’t stop you making a plugin that has multiple translations, but 
> it means that you have to roll your own, including building an equivalent 
> of the `lingo` macro.
>
> Therefore I need to find another way to achieve my goal (bundle plugin 
> with multiple translations). I think I should rely on the value returned by 
> `$:/language/`, but I don't know how to write a macro which would 
> concatenate the result returned by `$:/language/` with path to namespace of 
> the plugin. I thought to store translation tiddlers under either:
> - `$:/language/ru_RU/plugins/plugin_vendor/plugin_name/Note.multids`
> - `$:/plugins/plugin_vendor/plugin_name/languages/ru-RU/Note.multids`
>
>
> Here’s one approach:
>
> <$set name="myLingoBase" value={{{ 
> [[$:/plugins/plugin_vendor/plugin_name/]addsuffix{$:/language}]  }}}>
>
> Translated, wikified string: <$transclude tiddler={{{ 
> [addsuffix[/MyTranslatedString]] }}}/>
>
> Alternatively, without wikification: <$text text={{{ 
> [addsuffix[/MyTranslatedString]get[text]] }}}/>
>
> 
>
> Here we construct a variable “myLingoBase” that will end up containing a 
> string such as "$:/plugins/plugin_vendor/plugin_name/$:/languages/en-GB”. 
> Then when we want to access a particular translatable string we just 
> concatenate the final portion of the tiddler name and transclude it.
>
> Best wishes
>
> Jeremy
>
>
>
> Macro is a simple text substitution so it doesn't get the value of 
> `$:/language/`. Do I need:
> - a nested transclusion syntax
> - use of macrocall
> - use set or vars widget
>
> Best regards,
> iilyak
>
> -- 
> 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 tiddl...@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/CAP2DrbT0d1J4kkzzTZ%2BuDUurk4ns4JFAr21VM_Sa2xbozch7RQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/CAP2DrbT0d1J4kkzzTZ%2BuDUurk4ns4JFAr21VM_Sa2xbozch7RQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/ae5a8b37-3d6e-4950-a0c5-adb16998555c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Tiddlers starting with '+' or '-' might as well be illegal.

2019-07-09 Thread Flibbles
I'm writing plugins, and for a while, I was working under the assumption 
that lists are just a subset of filters, which is super convenient in many 
cases.

tiddlerA tidderB [[tiddler with spaces]]

can be interpreted as either.

However, it's not actually true. If you have a tiddler that starts with a 
'+' or a '-'. It breaks down.

tiddlerA -tiddler-with-dashes

produces different results. You have to have:

tiddlerA [[-tiddler-with-dashes]]

and I guess that's fine, but it looks like this case has never been 
considered.

Either

$tw.utils.stringifyList needs to properly wrap such tiddlers in brackets, 
which it currently doesn't, OR tiddlers starting with '+' or '-' need to be 
prohibited. I'm actually leaning toward prohibiting it, because otherwise 
this can cause confusion for users who want to do something like have 
"--Homepage--" be their Default tiddler, but when they put that in the 
setting, it doesn't work, because the instructions don't mention that 
dashes would need to be wrapped. Tiddlywiki already prohibits brackets. Why 
not this too?

-Flibbles

-- 
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/b74dce5d-1bce-46cf-9f76-e4efc0163353%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Tiddlers starting with '+' or '-' might as well be illegal.

2019-07-09 Thread Flibbles
That's understandable. Another solution would be requiring tiddlers 
starting with + - ~ to be wrapped in brackets in stringified lists.

Illegal: tiddlerA [[tiddler with spaces]] --My-Dashboard--
Legal: tiddlerA [[tiddler with spaces]] [[--My-Dashboard--]]

On Tuesday, July 9, 2019 at 3:45:30 AM UTC-4, TonyM wrote:
>
> Fibbles
>
> I think as a rule we try and keep the available characters we can use in 
> tittles as broad as possible.
>
> Any way, I will leave it to the developers to comment.
>
> Regards
> Tony
>
> On Tuesday, July 9, 2019 at 5:37:12 PM UTC+10, Flibbles wrote:
>>
>> Right. That's correct. That's why they're not equivalent. Filter syntax 
>> has special use cases for when filter runs start with + - ~, but lists 
>> don't care about that. A word starting with + - ~ in a list is just 
>> interpreted as part of the tiddler title. I think the list parser should 
>> treat them as special cases, just as the filter parser does.
>>
>> On Tuesday, July 9, 2019 at 3:33:31 AM UTC-4, TonyM wrote:
>>>
>>> See this documentation for the use of + - ~ tiddler name, perhaps this 
>>> is where this is coming from
>>>
>>> https://tiddlywiki.com/#Filter%20Expression
>>>
>>> Tony
>>>
>>> On Tuesday, July 9, 2019 at 4:03:27 PM UTC+10, Flibbles wrote:
>>>>
>>>> I'm writing plugins, and for a while, I was working under the 
>>>> assumption that lists are just a subset of filters, which is super 
>>>> convenient in many cases.
>>>>
>>>> tiddlerA tidderB [[tiddler with spaces]]
>>>>
>>>> can be interpreted as either.
>>>>
>>>> However, it's not actually true. If you have a tiddler that starts with 
>>>> a '+' or a '-'. It breaks down.
>>>>
>>>> tiddlerA -tiddler-with-dashes
>>>>
>>>> produces different results. You have to have:
>>>>
>>>> tiddlerA [[-tiddler-with-dashes]]
>>>>
>>>> and I guess that's fine, but it looks like this case has never been 
>>>> considered.
>>>>
>>>> Either
>>>>
>>>> $tw.utils.stringifyList needs to properly wrap such tiddlers in 
>>>> brackets, which it currently doesn't, OR tiddlers starting with '+' or '-' 
>>>> need to be prohibited. I'm actually leaning toward prohibiting it, because 
>>>> otherwise this can cause confusion for users who want to do something like 
>>>> have "--Homepage--" be their Default tiddler, but when they put that in 
>>>> the 
>>>> setting, it doesn't work, because the instructions don't mention that 
>>>> dashes would need to be wrapped. Tiddlywiki already prohibits brackets. 
>>>> Why 
>>>> not this too?
>>>>
>>>> -Flibbles
>>>>
>>>

-- 
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/dde165dc-496f-4987-a8e0-30eafdc0ae51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Tiddlers starting with '+' or '-' might as well be illegal.

2019-07-09 Thread Flibbles
Right. That's correct. That's why they're not equivalent. Filter syntax has 
special use cases for when filter runs start with + - ~, but lists don't 
care about that. A word starting with + - ~ in a list is just interpreted 
as part of the tiddler title. I think the list parser should treat them as 
special cases, just as the filter parser does.

On Tuesday, July 9, 2019 at 3:33:31 AM UTC-4, TonyM wrote:
>
> See this documentation for the use of + - ~ tiddler name, perhaps this is 
> where this is coming from
>
> https://tiddlywiki.com/#Filter%20Expression
>
> Tony
>
> On Tuesday, July 9, 2019 at 4:03:27 PM UTC+10, Flibbles wrote:
>>
>> I'm writing plugins, and for a while, I was working under the assumption 
>> that lists are just a subset of filters, which is super convenient in many 
>> cases.
>>
>> tiddlerA tidderB [[tiddler with spaces]]
>>
>> can be interpreted as either.
>>
>> However, it's not actually true. If you have a tiddler that starts with a 
>> '+' or a '-'. It breaks down.
>>
>> tiddlerA -tiddler-with-dashes
>>
>> produces different results. You have to have:
>>
>> tiddlerA [[-tiddler-with-dashes]]
>>
>> and I guess that's fine, but it looks like this case has never been 
>> considered.
>>
>> Either
>>
>> $tw.utils.stringifyList needs to properly wrap such tiddlers in brackets, 
>> which it currently doesn't, OR tiddlers starting with '+' or '-' need to be 
>> prohibited. I'm actually leaning toward prohibiting it, because otherwise 
>> this can cause confusion for users who want to do something like have 
>> "--Homepage--" be their Default tiddler, but when they put that in the 
>> setting, it doesn't work, because the instructions don't mention that 
>> dashes would need to be wrapped. Tiddlywiki already prohibits brackets. Why 
>> not this too?
>>
>> -Flibbles
>>
>

-- 
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/c9243467-2958-4db8-a0eb-510e1295f8e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: [TW5] Improving tiddler renaming behaviour

2019-08-22 Thread Flibbles
@TonyM, I'm not sure what you mean for having a plugin for deleting 
tiddlers.

If I have a tiddler with text:
```
Welcome to my project. Please be sure to visit the [[gift shop|Giftshop]].
```

If I remove the tiddler "Giftshop", What does this become?

On Wednesday, August 21, 2019 at 6:01:49 PM UTC-4, TonyM wrote:
>
> Cobbles
>
> I will check this out as its a critical feature for wikis.
>
> Given the centrality of the tiddler name in tiddlywiki perhaps the ability 
> to delete a tiddler and remove its name rather than rename would be helpful.
>
> Perhaps you could consider a desperate delete plugin which could be based 
> on your current plugin.
>
> Regards
> Tony
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/856d20da-88b9-4731-b48e-22fe2887f470%40googlegroups.com.


[tw5] Re: Multi-value fields

2019-08-25 Thread Flibbles
What @TonyM said. Just store colors in a field as space separated, like: 
"red black brown". List and enlist can separate them out just fine.
```
<$list filter="[list[Cardinal!!colour]]" />
<$list filter="[enlist{Cardinal!!colour}]" />
```
both output
```
red
black
brown
```
Values with a space are handled with brackets. e.g. `yellow brown [[sky 
blue]]`

You can also search that color field with `[contains:colour[brown]]` for 
all tiddlers with brown as one of its list items.

You can collect all the colors of all North American birds with `[tag[North 
American]each:list-item[colour]]`

One last thing. Don't use the field color. It's reserved by tiddlywiki for 
stuff, and you'll get a color wheel as an input field.

-- 
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/0ddac792-c77b-473a-a3c4-e320ec47415e%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-03 Thread Flibbles


@David Gifford: That's the kind of thing I like to hear. I'm glad it's made 
your life easier.

@PMario: So there's already a filter operator `[relink:references[]]` which 
shows which tiddlers would be changed by an update. Also, such a list is 
also presented in the TiddlerInfo tab *Relink References.* The only pause I 
have is what design would be best. As it is, I still reserve the space 
below the rename checkbox to notify the user about impossible renames 
(these are either from complex titles I don't support yet, or *super* 
complex situations where it literally is impossible, such as changing a 
list field title to `*title ]] with brackets*`). I'm concerned with making 
that space too crowded. But it may still be worth while.

-Flibbles

-- 
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/829c22aa-59fb-4514-8d5b-d932b28ee2f4%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-03 Thread Flibbles
You mean syntax like:

{{MyTiddler!!field}}

or

<$widget attribute={{MyTiddler}} />

Because those cases are both already covered. The only syntax that's not 
managed yet are macrocalls, and that'll only take me another couple of days 
to finish.

On Tuesday, September 3, 2019 at 5:34:57 PM UTC-4, Mark S. wrote:
>
> Looks great!
>
> I pretty much don't use links any more, because of the relinking problem. 
> But I do use transclusions.
> Would it be possible to apply your plugin to change transclusions that use 
> standard TW markup?
>
> Thanks!
>
> On Sunday, September 1, 2019 at 7:27:19 PM UTC-7, Flibbles wrote:
>>
>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>
>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>> filters. It's highly customizable, but it will also work out of the box. 
>> It's robust, and can handle bizarre name changes. It works through 
>> whitelisting, so it doesn't change plaintext instances of a title, or other 
>> instances where an updated would be undesirable. It's also well tested (but 
>> still really new!!). It should be comprehensive. The only thing it doesn't 
>> manage is macro arguments. If there's a lot of interest in that, I'll 
>> figure out how to get that working.
>>
>> Otherwise, I really hope everyone gets good use out of this. Having 
>> written it, I completely understand why this isn't a core feature. It was 
>> *hard 
>> as crap*! There are so many edge cases! I'm sure more will still crop up.
>>
>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>
>> Source code here <https://github.com/flibbles/tw5-relink>.
>>
>> I would absolutely love to get some feedback. I really hope this helps 
>> people.
>>
>> -Flibbles
>>
>

-- 
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/02c2eb08-17a0-454c-8bc3-0c46581effaa%40googlegroups.com.


[tw5] Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-01 Thread Flibbles
I present Relink <https://flibbles.github.io/tw5-relink/>!

It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
filters. It's highly customizable, but it will also work out of the box. 
It's robust, and can handle bizarre name changes. It's well tested (but 
still really new!!). It should be comprehensive. The only thing it doesn't 
manage is macro arguments. If there's a lot of interest in that, I'll 
figure out how to get that working.

Otherwise, I really hope everyone gets good use out of this. Having written 
it, I completely understand why this isn't a core feature. It was *hard as 
crap*! There are so many edge cases! I'm sure more will still crop up.

Demo page here <https://flibbles.github.io/tw5-relink/>.

Source code here <https://github.com/flibbles/tw5-relink>.

I would absolutely love to get some feedback. I really hope this helps 
people.

-Flibbles

-- 
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/32d77d15-9e87-4856-a42b-a0ffbb507e2f%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-02 Thread Flibbles

I hope Relink works out for you. Let me know if you have any problems with 
it, and you should change your name. There aren't enough toy dogs in 
programming.

-Flibbles

On Monday, September 2, 2019 at 10:19:35 AM UTC-4, David Gifford wrote:
>
> I don't know what I like more, the awesome plugin, or the cute nickname 
> 'Flibbles'. The former is amazing. The latter makes me want to rename my 
> Pomeranian. 
>
> Dave
>
> On Sunday, September 1, 2019 at 9:27:19 PM UTC-5, Flibbles wrote:
>>
>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>
>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>> filters. It's highly customizable, but it will also work out of the box. 
>> It's robust, and can handle bizarre name changes. It works through 
>> whitelisting, so it doesn't change plaintext instances of a title, or other 
>> instances where an updated would be undesirable. It's also well tested (but 
>> still really new!!). It should be comprehensive. The only thing it doesn't 
>> manage is macro arguments. If there's a lot of interest in that, I'll 
>> figure out how to get that working.
>>
>> Otherwise, I really hope everyone gets good use out of this. Having 
>> written it, I completely understand why this isn't a core feature. It was 
>> *hard 
>> as crap*! There are so many edge cases! I'm sure more will still crop up.
>>
>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>
>> Source code here <https://github.com/flibbles/tw5-relink>.
>>
>> I would absolutely love to get some feedback. I really hope this helps 
>> people.
>>
>> -Flibbles
>>
>

-- 
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/fee543dd-cae4-4474-85fe-1c2e9b6e58ff%40googlegroups.com.


[tw5] Re: [TW5] Improving tiddler renaming behaviour

2019-08-21 Thread Flibbles
For anyone who's interested in a more comprehensive way of renaming, I've 
published a plugin here:

https://github.com/flibbles/tw5-relink

This allows updating of specific syntax patterns in text, filters, as well 
as custom fields. And whether those fields are lists, filters, or singular 
tiddler titles.

-Flibbles

On Thursday, December 15, 2016 at 4:36:07 PM UTC-5, Jeremy Ruston wrote:
>
> I’ve had some time to work on TiddlyWiki in the last few days, but as 
> sometimes happens, it was while travelling, and without access to wifi. 
> Prompted by some recent user feedback, I decided to focus on improvements 
> to the mechanism for renaming tiddlers: renaming an existing tiddler shows 
> a checkbox in the edit template prompting “Update foofoo to barbar in the 
> tags and list fields of other tiddlers”.
>
> If the checkbox is checked when confirming the tiddler, then any 
> references to the old tiddler title in tags or list fields of other 
> tiddlers are relinked to point to the new title. (See screenshot below).
>
> Note that at this point there is no attempt to perform search and replace 
> within the “text” field, because of the potential for unintended results, 
> but this is something that would be worth exploring for the future. Even as 
> things stand, it makes renaming entries in a table of contents much easier.
>
> You can try out the new feature by renaming an existing tiddler at:
>
> http://tiddlywiki.com/prerelease
>
> Please let me know if you run into any problems or edge cases,
>
> Best wishes
>
> Jeremy
>
>
>

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


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-16 Thread Flibbles
Hey @TonyM

So, I'm a little confused. It sounds like you you might be proposing two 
possibilities:

   1. Have a filter which can be used to exclude tiddlers from being 
   touched by Relink. Currently all non-shadow tiddlers are touched. But a 
   filter would be feasible.
   2. Propose having different relink configuration profiles for different 
   categories of tiddlers. This sounds very complicated, not so much to 
   design, but to present to the end-user.

I'm also a little confused by your mention of the text field, I assume you 
mean a tiddler's text field, which refers to the body. Your example of text 
content was a note '"Old name" was renamed to "new name"'. But plain text 
like that wouldn't be touched anyway. Relink only targets reference-related 
instances of a renamed title.

As to the dangers of renaming a dangerous system tiddler, I think I'd need 
to see an example. Since Relink doesn't touch shadow tiddlers, I'm not sure 
what harm could be done. The only tiddlers referencing shadow tiddlers are 
other shadow tiddlers, I believe. And I don't know of any system tiddlers 
that would break anything down if they were touched.

Avoiding tiddlers like $:/backup or $:/trashbin might be examples. I guess 
they have some plugin or module that's creating and maintaining that. The 
solution to that ties into the first proposal I think you're putting 
forward: reasonable, though I would do something a bit more intricate than 
just a filter the user edits, so that plugins could introduce their own 
tiddlers to be exempt from relinking.

Am I understanding you correctly?
-Flibbles


On Sunday, September 15, 2019 at 11:58:48 PM UTC-4, TonyM wrote:
>
> Fibbles,
>
> I was impressed with the potential of relink and received a request by a 
> client who uses a large Tiddlywiki database to allow them to change 
> someones name to their married name. The persons name a tiddler title 
> itself, is recorded in a range of fields and relink seems to detect them 
> all. However I have names mentioned in text fields such as a note saying 
> "Old name" was renamed to "new name" which I would like to exclude. Of 
> course I assume I can change the configuration to stop this. However 
> changing office names is also needed and these reside in another set of 
> fields. I assume just whitelisting all the list fields for all the tiddlers 
> I may wish to rename would work fine. 
>
> However I am just wondering, I could in this case delete all the rules 
> that impact widgets, macro and filters because none of these should contain 
> something the user has any reason to rename. In some ways making it less 
> "pervasive" is possibly a wise design strategy, or is it?, what if they 
> rename a critical system tiddler? Would I prefer this to be relinked or 
> would it be best to prohibit relinking on system tiddlers?
>
> I am not sure there is a way for us to selectively filter to what relink 
> applies to?
>
> One idea may be to place a filter such that the relink action (when 
> renaming) does not appear, or take place on tiddlers that do not match the 
> filter. This would allow me to set a filter like 
> [all[current]object-type[office]] [all[current]object-type-person]]
> which would use relink on the resulting tiddlers and any other tiddler not 
> in this filter would not permit relinking. Then as a designer I could 
> change this filter so relink will work for me when I am undertaking 
> designer activity and become active on say system tiddlers macros etc...
>
> I am yet to work through the extensive details of your wonderful plugin 
> and determine how it can best be used in a range of scenarios. It seems to 
> me this is not only a great tool to use to support end users, but to assist 
> in the development process. 
>
> if I do not understand enough yet let me know, It would or could it be 
> desirable to have different relink configurations for different cases for 
> example for office and person do not relink items found in the text field, 
> but for tiddlers tagged $:/tags/Macro update all occurrences except in 
> tiddlers with the prefix $:/backup or $:/trashbin
>
> This is only food for thought, so please do not feel any pressure for a 
> refactor or re-write. I would be interested in your view.
>
> Thanks In advance
> 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/06ab81d2-92a5-405d-845c-a6621df706b8%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-16 Thread Flibbles
First, a question:

What is this $:/trashbin stuff? Is this a tiddlywiki feature I'm unaware 
of, or is it something to do with an unrelated plugin? Depending on which 
it is, it takes a different approach. If this is some core features, then 
Relink should ignore it by default. If it's a plugin something, then the 
plugin should have a way to integrate with Relink and exclude $:/trashbin 
without the user needing to input anything.

Next. I'm having a little trouble following your use-case, but sounds like 
not just the ability to select which tiddlers are eligible for relinking, 
but to make it possible for the eligible tiddlers to vary *depending on the 
tiddler being renamed*.

And I'm unclear, but it sounds like not only that, but you want to be able 
to configure which fields, macros, widgets, and operators get updated per 
tiddler. So a `person-office` list field might get updated on tiddler A, 
but not tiddler B.

I'll be honest with you, TonyM. These sounds like super advanced use cases. 
I'm very concerned that encoding Relink to handle all this will detract 
from Relink's elegance. It already has four whitelists which I'm worried 
daunt casual users.

But how about this. Let's say Relink had one "General" configuration page 
which allowed you to input an ignore filter. Tiddlers that pass through 
that filter will not be updated. But here's the cool part. The 
currentTiddler variable for that filter is set to the name of the tiddler 
being renamed (or maybe it'll be set to fromTiddler, and there'll be 
toTiddler). That way, a user can make the filter sensitive to the tiddler 
being renamed, and adjust what tiddlers would pass through the filter. 
Would this be a solution for your problem?

And if you still need more sophistication than that, I'd more likely say 
the solution would be to improve Relink's hackability, so we can make a mod 
for your specific case, but your case does sound super specific. (Or maybe 
it isn't. I haven't gotten much feedback from anyone yet.)

-Flibbles

-- 
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/06a3974a-81e2-4f1d-b746-17e7343b77d0%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-17 Thread Flibbles
In my defense, core vanilla Tiddlywiki will relink system tiddlers on a 
rename, and I decided to keep vanilla behavior as much as possible. If 
automatically changing system tiddlers is a problem, then perhaps it should 
also be submitted as an undesirable behavior to the Tiddlywiki bug tracker.

Otherwise, it sounds like all you need is a relink filter on Relink's 
general settings page. This filter specifies which tiddlers get touched 
during a rename. And it's default value would be `[all[]]` or 
`[all[]!is[system]]`

As for disabling Relink when the user is editing system tiddlers, I'm 
inclined to let them just uncheck the checkbox, particularly since a 
working solution for that would actually involve altering the underlying 
javascript). If someone's comfortable enough to edit a system tiddler, then 
surely they're comfortable enough to decide whether Relink should or 
shouldn't work its magic.

Although it does sound like you're working with a case where there are 
multiple users, and authorization schemes. If that's the case, I'll make 
sure Relink is hackable enough that your desired behavior is obtainable 
with a single system tiddler or so.

-Flibbles

On Monday, September 16, 2019 at 11:37:16 PM UTC-4, TonyM wrote:
>
> Flibbles,
>
> I will try and express myself better. I do not think these are special or 
> advanced features, I think they may be essential.
>
> But yes, All I am asking for is a little increased hackability. 
>
> First your solution is so good already, that its only because it is so 
> close to a universal solution, I feel I need to point this out. And perhaps 
> I have missed something about its current behaviour and I am happy to be 
> corrected.
>
> Your question re trashbin, The trashbin is just a plugin, and like other 
> plugins it stores things behind the $:/ prefix. The fact that relink can 
> reach into these tiddlers and modify them is new to tiddlwiki and sometimes 
> will be illogical. If I delete a tiddler it goes into the trash bin and I 
> may want it to remain there and not have relink touch it, otherwise it will 
> no longer contain what it contained when I deleted it.
>
> With all due respect every other plugin should not need to be designed to 
> deal with any other "Specific" plugin so Mohamad's Trashbin plugin should 
> not need to know about the relink plugin. Even if it did, how does it 
> exclude itself from relink?. However there is immense value of providing 
> some simple filter configurations so relink can accommodate any or all 
> future plugins by being able to reduce or limit the scope of what it 
> changes if necessary.
>
> There are two issues and I believe are general in nature and may be an 
> issue for many;
>
> Currently
>
>1. On which tiddlers does relink occur?
>Presently any tiddler you attempt to rename (Except shadow tiddlers)
>2. Which tiddlers are changed by relink?
>Any for which a complex set of search conditions are true
>
> 1. I would like to disable or enable the relink feature by filter setting. 
> Until I have provided the appropriate additional fields for relink to 
> operate with - in Plugin > Configuration > Fields,  any relink will be 
> incomplete. 
> In a published wiki, not in development It may be better not to permit 
> users to edit and relink system tiddlers AttributesMacrosOperators
>
> Although its wonderful that relink can help keep a database or tiddler 
> valid with relinking.
>
> 2. I would love to be able to simply exclude some tiddlers from update by 
> relink according to a filter. For example I may want a log, a trashbin a 
> set of test data or anything not be updated. Relink already lets me see 
> what It will affect when relinking inside the info tab. If I discover the 
> rules will impact some tiddlers I do not want it to, a "rename filter" 
> could allow me to exclude them. 
>
> Personally I build a range of solutions in system tiddlers that are not 
> delivered by plugin thus have do not have a shadow tiddler, they will be 
> effected by relink even when I do not want them to. If import a bundle of 
> tiddlers built elsewhere there is a chance they may contain something that 
> relink will change inappropriately, A project I am starting now actually 
> generates additional wikis, so I have tiddlers in my wiki that are not part 
> of the current wiki but provide input to the wiki generation process. There 
> is a danger that these will inadvertently have code "relinked" within them 
> if I can't exclude them. This is even more likely to occur if I use good 
> naming conventions in my code. There are also circumstances where a local 
> variable is set to override a global setting and we may be happy for relink 
> to impact the global but no

Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-07 Thread Flibbles
@Mohammad

I looked into total commander and I see why they don't integrate. 
Unfortunately, I think the change would have to be on Total Commander's 
side. Their tiddler renaming stuff is done like,

 <$action-setfield  $tiddler=<> title=<> />
 <$action-deletetiddler $tiddler=<> />

Which is technically just making a new tiddler, and deleting another. 
Action-setfield doesn't call the renaming hooks. If it were instead,

<$action-sendmessage $message="tm-rename-tiddler" from=<> 
to=<> />

Then it should all work together.

-Flibbles

On Saturday, September 7, 2019 at 7:01:40 AM UTC-4, Mohammad wrote:
>
> Hi Mario,
>  Because when I rename a tiddler using Tiddler commander, it does not 
> update links and etc.
> I have to connect these two some how!
>
>
> Best wishes
> Mohammad
>
>
> On Sat, Sep 7, 2019 at 1:17 PM PMario > 
> wrote:
>
>> On Saturday, September 7, 2019 at 6:14:45 AM UTC+2, Mohammad wrote:
>>>
>>> This is great!
>>> I am thinking how can I merge this into Tiddler Commander plugin!
>>>
>>
>> Why do you want to merge it. ... Try to use it as a plugin, and let the 
>> users decide if they want to install both plugins. 
>>
>> -m
>>
>> -- 
>> 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 tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/2aa85d7f-ddf5-4db4-b860-2c597904ecba%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/2aa85d7f-ddf5-4db4-b860-2c597904ecba%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/1ffadd14-7df5-4b82-be30-bdfb12e70363%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-06 Thread Flibbles
Version 1.5 released. Macro parameter relinking is now supported. It comes 
with its own whitelist.

(e.g. <> or <$macrocall $name=myMacro 
param="tiddlerNameToRelink" />)

Now Relink can rename any kind of WikiText pattern.

Also, bugfixes.

-Flibbles

On Sunday, September 1, 2019 at 10:27:19 PM UTC-4, Flibbles wrote:
>
> I present Relink <https://flibbles.github.io/tw5-relink/>!
>
> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
> filters. It's highly customizable, but it will also work out of the box. 
> It's robust, and can handle bizarre name changes. It works through 
> whitelisting, so it doesn't change plaintext instances of a title, or other 
> instances where an updated would be undesirable. It's also well tested (but 
> still really new!!). It should be comprehensive.
>
> Otherwise, I really hope everyone gets good use out of this. Having 
> written it, I completely understand why this isn't a core feature. It was 
> *hard 
> as crap*! There are so many edge cases! I'm sure more will still crop up.
>
> *Edit**: It now also supports macros, making it a fully comprehensive 
> relinking plugin.*
>
> Demo page here <https://flibbles.github.io/tw5-relink/>.
>
> Source code here <https://github.com/flibbles/tw5-relink>.
>
> I would absolutely love to get some feedback. I really hope this helps 
> people.
>
> -Flibbles
>

-- 
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/23b2529d-f9da-49e0-aee8-4061f9eaa6e2%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-07 Thread Flibbles
...I don't follow.

It sounds like you're saying Relink should be the one to bridge the gap 
because it uses JS, but I can't.

I get that Tiddler Commander is pure TW script, but it's still possible for 
it to do legit renaming. Tiddlywiki.com has the means to rename tiddlers 
rather than just create and delete them. The change I've outlined above 
would adjust Tiddler Commander to properly rename tiddlers, and it'd only 
take about 5 minutes to do. I'd do it myself, except the Tiddler Commander 
source only contains the compiled plugin for some odd reason. If you want 
integration, I'd suggest making an issue in Kookma github page 
<https://github.com/kookma/TW-Commander> and copy and paste my last two 
posts.

-Flibbles

On Saturday, September 7, 2019 at 9:19:01 AM UTC-4, Mohammad wrote:
>
> Hi Flibbles
> Thank you for update!
> Yes, Tiddler Commander is a pure TW script and does not use any JS. 
> So, the current technology at tiddlywiki.com is to create a new tiddler!
>
> By the way it is tracking of a relink seems to be much more complicated to 
> be done using Tiddler Commander or pure TW scripts.
>
> Best wishes
> Mohammad
>
>
> On Sat, Sep 7, 2019 at 4:27 PM Flibbles  > wrote:
>
>> @Mohammad
>>
>> I looked into total commander and I see why they don't integrate. 
>> Unfortunately, I think the change would have to be on Total Commander's 
>> side. Their tiddler renaming stuff is done like,
>>
>>  <$action-setfield  $tiddler=<> title=<> />
>>  <$action-deletetiddler $tiddler=<> />
>>
>> Which is technically just making a new tiddler, and deleting another. 
>> Action-setfield doesn't call the renaming hooks. If it were instead,
>>
>> <$action-sendmessage $message="tm-rename-tiddler" from=<> 
>> to=<> />
>>
>> Then it should all work together.
>>
>> -Flibbles
>>
>> On Saturday, September 7, 2019 at 7:01:40 AM UTC-4, Mohammad wrote:
>>>
>>> Hi Mario,
>>>  Because when I rename a tiddler using Tiddler commander, it does not 
>>> update links and etc.
>>> I have to connect these two some how!
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sat, Sep 7, 2019 at 1:17 PM PMario  wrote:
>>>
>>>> On Saturday, September 7, 2019 at 6:14:45 AM UTC+2, Mohammad wrote:
>>>>>
>>>>> This is great!
>>>>> I am thinking how can I merge this into Tiddler Commander plugin!
>>>>>
>>>>
>>>> Why do you want to merge it. ... Try to use it as a plugin, and let the 
>>>> users decide if they want to install both plugins. 
>>>>
>>>> -m
>>>>
>>>> -- 
>>>> 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 tiddl...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/tiddlywiki/2aa85d7f-ddf5-4db4-b860-2c597904ecba%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/tiddlywiki/2aa85d7f-ddf5-4db4-b860-2c597904ecba%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>> 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 tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/1ffadd14-7df5-4b82-be30-bdfb12e70363%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/1ffadd14-7df5-4b82-be30-bdfb12e70363%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/6bdc2848-32a8-448d-843a-e0a7ac24b480%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-07 Thread Flibbles
Hey @Mohammad, didn't realize you were Kookma.

Does this not work?

<$action-sendmessage $message="tm-rename-tiddler" from=<> 
to=<> />

This works for me. I posted that previously in the same response where I 
posted what lines would need to be changed. Perhaps you missed it?

-Flibbles

On Saturday, September 7, 2019 at 10:50:33 AM UTC-4, Mohammad wrote:
>
> Hi Flibbles,
>  No, I did not said this should be done on Relink side! Yes, it is on 
> Tiddler Commander side!
> By the way, I appreciate if you explain me how to do this using pure TW 
> script!
>
> As you mentioned in your previous post Tiddler Commander uses
>
>  <$action-setfield  $tiddler=<> title=<> />
>  <$action-deletetiddler $tiddler=<> /> 
>
> That's true! but if I want to do this without create-delete actions how it 
> is possible
>
> *Tiddlywiki.com has the means to rename tiddlers rather than just create 
> and delete them.  *
>
>
>
> Best wishes
> Mohammad
>
>
> On Sat, Sep 7, 2019 at 6:59 PM Flibbles  > wrote:
>
>> ...I don't follow.
>>
>> It sounds like you're saying Relink should be the one to bridge the gap 
>> because it uses JS, but I can't.
>>
>> I get that Tiddler Commander is pure TW script, but it's still possible 
>> for it to do legit renaming. Tiddlywiki.com has the means to rename 
>> tiddlers rather than just create and delete them. The change I've outlined 
>> above would adjust Tiddler Commander to properly rename tiddlers, and it'd 
>> only take about 5 minutes to do. I'd do it myself, except the Tiddler 
>> Commander source only contains the compiled plugin for some odd reason. If 
>> you want integration, I'd suggest making an issue in Kookma github page 
>> <https://github.com/kookma/TW-Commander> and copy and paste my last two 
>> posts.
>>
>> -Flibbles
>>
>> On Saturday, September 7, 2019 at 9:19:01 AM UTC-4, Mohammad wrote:
>>>
>>> Hi Flibbles
>>> Thank you for update!
>>> Yes, Tiddler Commander is a pure TW script and does not use any JS. 
>>> So, the current technology at tiddlywiki.com is to create a new tiddler!
>>>
>>> By the way it is tracking of a relink seems to be much more complicated 
>>> to be done using Tiddler Commander or pure TW scripts.
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sat, Sep 7, 2019 at 4:27 PM Flibbles  wrote:
>>>
>>>> @Mohammad
>>>>
>>>> I looked into total commander and I see why they don't integrate. 
>>>> Unfortunately, I think the change would have to be on Total Commander's 
>>>> side. Their tiddler renaming stuff is done like,
>>>>
>>>>  <$action-setfield  $tiddler=<> title=<> 
>>>> />
>>>>  <$action-deletetiddler $tiddler=<> />
>>>>
>>>> Which is technically just making a new tiddler, and deleting another. 
>>>> Action-setfield doesn't call the renaming hooks. If it were instead,
>>>>
>>>> <$action-sendmessage $message="tm-rename-tiddler" from=<
>>>> > to=<> />
>>>>
>>>> Then it should all work together.
>>>>
>>>> -Flibbles
>>>>
>>>> On Saturday, September 7, 2019 at 7:01:40 AM UTC-4, Mohammad wrote:
>>>>>
>>>>> Hi Mario,
>>>>>  Because when I rename a tiddler using Tiddler commander, it does not 
>>>>> update links and etc.
>>>>> I have to connect these two some how!
>>>>>
>>>>>
>>>>> Best wishes
>>>>> Mohammad
>>>>>
>>>>>
>>>>> On Sat, Sep 7, 2019 at 1:17 PM PMario  wrote:
>>>>>
>>>>>> On Saturday, September 7, 2019 at 6:14:45 AM UTC+2, Mohammad wrote:
>>>>>>>
>>>>>>> This is great!
>>>>>>> I am thinking how can I merge this into Tiddler Commander plugin!
>>>>>>>
>>>>>>
>>>>>> Why do you want to merge it. ... Try to use it as a plugin, and let 
>>>>>> the users decide if they want to install both plugins. 
>>>>>>
>>>>>> -m
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "TiddlyWiki" group.
>>>>>> To unsubscribe from this group and stop 

Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-07 Thread Flibbles
No, it doesn't. It's a core feature 
<https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Fwidgets%2Fnavigator.js>.

-Flibbles

On Saturday, September 7, 2019 at 11:03:39 AM UTC-4, Mohammad wrote:
>
> Hey Flibbles,
>
>  No problem :-)
>
> So, does this new *tm-rename-tiddler *need Relink plugin?
>
>
> Best wishes
> Mohammad
>
>
> On Sat, Sep 7, 2019 at 7:24 PM Flibbles  > wrote:
>
>> Hey @Mohammad, didn't realize you were Kookma.
>>
>> Does this not work?
>>
>> <$action-sendmessage $message="tm-rename-tiddler" from=<> 
>> to=<> />
>>
>> This works for me. I posted that previously in the same response where I 
>> posted what lines would need to be changed. Perhaps you missed it?
>>
>> -Flibbles
>>
>> On Saturday, September 7, 2019 at 10:50:33 AM UTC-4, Mohammad wrote:
>>>
>>> Hi Flibbles,
>>>  No, I did not said this should be done on Relink side! Yes, it is on 
>>> Tiddler Commander side!
>>> By the way, I appreciate if you explain me how to do this using pure TW 
>>> script!
>>>
>>> As you mentioned in your previous post Tiddler Commander uses
>>>
>>>  <$action-setfield  $tiddler=<> title=<> 
>>> />
>>>  <$action-deletetiddler $tiddler=<> /> 
>>>
>>> That's true! but if I want to do this without create-delete actions how 
>>> it is possible
>>>
>>> *Tiddlywiki.com has the means to rename tiddlers rather than just create 
>>> and delete them.  *
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sat, Sep 7, 2019 at 6:59 PM Flibbles  wrote:
>>>
>>>> ...I don't follow.
>>>>
>>>> It sounds like you're saying Relink should be the one to bridge the gap 
>>>> because it uses JS, but I can't.
>>>>
>>>> I get that Tiddler Commander is pure TW script, but it's still possible 
>>>> for it to do legit renaming. Tiddlywiki.com has the means to rename 
>>>> tiddlers rather than just create and delete them. The change I've outlined 
>>>> above would adjust Tiddler Commander to properly rename tiddlers, and it'd 
>>>> only take about 5 minutes to do. I'd do it myself, except the Tiddler 
>>>> Commander source only contains the compiled plugin for some odd reason. If 
>>>> you want integration, I'd suggest making an issue in Kookma github page 
>>>> <https://github.com/kookma/TW-Commander> and copy and paste my last 
>>>> two posts.
>>>>
>>>> -Flibbles
>>>>
>>>> On Saturday, September 7, 2019 at 9:19:01 AM UTC-4, Mohammad wrote:
>>>>>
>>>>> Hi Flibbles
>>>>> Thank you for update!
>>>>> Yes, Tiddler Commander is a pure TW script and does not use any JS. 
>>>>> So, the current technology at tiddlywiki.com is to create a new 
>>>>> tiddler!
>>>>>
>>>>> By the way it is tracking of a relink seems to be much more 
>>>>> complicated to be done using Tiddler Commander or pure TW scripts.
>>>>>
>>>>> Best wishes
>>>>> Mohammad
>>>>>
>>>>>
>>>>> On Sat, Sep 7, 2019 at 4:27 PM Flibbles  wrote:
>>>>>
>>>>>> @Mohammad
>>>>>>
>>>>>> I looked into total commander and I see why they don't integrate. 
>>>>>> Unfortunately, I think the change would have to be on Total Commander's 
>>>>>> side. Their tiddler renaming stuff is done like,
>>>>>>
>>>>>>  <$action-setfield  $tiddler=<> title=<> 
>>>>>> />
>>>>>>  <$action-deletetiddler $tiddler=<> />
>>>>>>
>>>>>> Which is technically just making a new tiddler, and deleting another. 
>>>>>> Action-setfield doesn't call the renaming hooks. If it were instead,
>>>>>>
>>>>>> <$action-sendmessage $message="tm-rename-tiddler" from=<
>>>>>> > to=<> />
>>>>>>
>>>>>> Then it should all work together.
>>>>>>
>>>>>> -Flibbles
>>>>>>
>>>>>> On Saturday, September 7, 2019 at 7:01:40 AM UTC-4, Mohammad wrote:
>>>>>>>
>>>>>>> Hi Mario,
>&

[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-20 Thread Flibbles
Yes. This problem is coming from Relink. I was unaware that IE11 doesn't 
allow backtick syntax. I will have that fixed tomorrow. Too much to do 
tonight.

Thank you for reporting this issue. I've created a bug report for it here 
<https://github.com/flibbles/tw5-relink/issues/9>. I'll be posting any 
further developments on the issues, such as when a fix is pushed, there.

-Flibbles

On Friday, September 20, 2019 at 7:23:53 PM UTC-4, CJ Veniot wrote:
>
> G'day Flibbles,
>
> I've got an internal javascript error with my TiddlyWiki which happens 
> consistently in IE 11, but never on my Chromebook.
>
> The problem goes away when Relink is disabled.
>
> Please find details in this other thread:  
> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/tiddlywiki/6RnrQLYG4QY/Ul_tm2o0BwAJ
>
> On Sunday, September 1, 2019 at 11:27:19 PM UTC-3, Flibbles wrote:
>>
>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>
>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>> filters. It's highly customizable, but it will also work out of the box. 
>> It's robust, and can handle bizarre name changes. It works through 
>> whitelisting, so it doesn't change plaintext instances of a title, or other 
>> instances where an updated would be undesirable. It's also well tested (but 
>> still really new!!). It should be comprehensive.
>>
>> Otherwise, I really hope everyone gets good use out of this. Having 
>> written it, I completely understand why this isn't a core feature. It was 
>> *hard 
>> as crap*! There are so many edge cases! I'm sure more will still crop up.
>>
>> *Edit**: It now also supports macros, making it a fully comprehensive 
>> relinking plugin.*
>>
>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>
>> Source code here <https://github.com/flibbles/tw5-relink>.
>>
>> I would absolutely love to get some feedback. I really hope this helps 
>> people.
>>
>> -Flibbles
>>
>

-- 
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/ba284261-8249-4a50-8a9e-0fc89e1094da%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2019-09-21 Thread Flibbles
@CJ Veniot: I think Relink supports IE11 now 
<https://github.com/flibbles/tw5-relink/issues/9>. I wasn't able to get it 
to crash anymore while using that browser (but there may be something 
hidden you'll encounter some day. If you do, let me know)

@TonyM: I've got basic support for changing which tiddlers get updated 
<https://github.com/flibbles/tw5-relink/issues/10>. It's got more work to 
do, but it's at a state where you can use it, and let me know if it's not 
what you need.

On Saturday, September 21, 2019 at 8:32:38 AM UTC-4, CJ Veniot wrote:
>
> As we would say back home: "pas de panic".  In the meantime, really easy 
> to disable Relink just before "deploying" my tiddlywiki instance.
>
> On Friday, September 20, 2019 at 11:22:57 PM UTC-3, Flibbles wrote:
>>
>> Yes. This problem is coming from Relink. I was unaware that IE11 doesn't 
>> allow backtick syntax. I will have that fixed tomorrow. Too much to do 
>> tonight.
>>
>> Thank you for reporting this issue. I've created a bug report for it here 
>> <https://github.com/flibbles/tw5-relink/issues/9>. I'll be posting any 
>> further developments on the issues, such as when a fix is pushed, there.
>>
>> -Flibbles
>>
>> On Friday, September 20, 2019 at 7:23:53 PM UTC-4, CJ Veniot wrote:
>>>
>>> G'day Flibbles,
>>>
>>> I've got an internal javascript error with my TiddlyWiki which happens 
>>> consistently in IE 11, but never on my Chromebook.
>>>
>>> The problem goes away when Relink is disabled.
>>>
>>> Please find details in this other thread:  
>>> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/tiddlywiki/6RnrQLYG4QY/Ul_tm2o0BwAJ
>>>
>>> On Sunday, September 1, 2019 at 11:27:19 PM UTC-3, Flibbles wrote:
>>>>
>>>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>>>
>>>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>>>> filters. It's highly customizable, but it will also work out of the box. 
>>>> It's robust, and can handle bizarre name changes. It works through 
>>>> whitelisting, so it doesn't change plaintext instances of a title, or 
>>>> other 
>>>> instances where an updated would be undesirable. It's also well tested 
>>>> (but 
>>>> still really new!!). It should be comprehensive.
>>>>
>>>> Otherwise, I really hope everyone gets good use out of this. Having 
>>>> written it, I completely understand why this isn't a core feature. It was 
>>>> *hard 
>>>> as crap*! There are so many edge cases! I'm sure more will still crop 
>>>> up.
>>>>
>>>> *Edit**: It now also supports macros, making it a fully comprehensive 
>>>> relinking plugin.*
>>>>
>>>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>>>
>>>> Source code here <https://github.com/flibbles/tw5-relink>.
>>>>
>>>> I would absolutely love to get some feedback. I really hope this helps 
>>>> people.
>>>>
>>>> -Flibbles
>>>>
>>>

-- 
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/c29d41ec-a04f-4d63-bb44-35221c62236e%40googlegroups.com.


[tw5] Re: Advanced search - filter expressions: how do I force a particular tiddler to appear at the top when exporting to a static page?

2019-10-04 Thread Flibbles
Sounds like you want something like

[!is[system]!tag[$:/tags/Stylesheet]!tag[$:/tags/Macro]sort[title]] [[
Program Tips]] +[putfirst[]] [[In conclusion]]

To put an item in last place, all you have to do is list it at the end. 
Extra filter expressions dominantly append. So if an item shows up twice, 
it'll take the last one. Thus [[In conclusion]] will now be the last. 
There's no need to do any [putlast[]] stuff (which is designed to put the 
first listItem last).

Though this assumes [[In conclusion]] (or whatever you use) exists. If 
there's a chance it doesn't, then end with [[In conclusion]is[tiddler]] 
instead, which just prevents the filter from appending a non-existent title.

-Flibbles

On Friday, October 4, 2019 at 1:38:12 AM UTC-4, Suzanne McHale wrote:
>
> The first one seems to work, thanks! It also avoids the issue of that 
> tiddler being repeated in the [!is[system]sort[title]] list.
>
> Is there also a way of 
>
>
>1. putting a particular tiddler last (I tried *+[putlast[]]* for a 
>different tiddler, but it conflicted with the first + command) and 
>2. excluding my own created *$:/tags/Stylesheet* and *$:/tags/Macro* 
>tiddlers? (The latter appear in the tiddlers to be exported.)
>
> (Filter expressions are very useful but seem to be very difficult to get 
> to work the way one wants!)
>
> On Thursday, October 3, 2019 at 9:52:42 PM UTC+10, Flibbles wrote:
>>
>> Maybe I'm late to the party, but the following seem to work too:
>>
>> [!is[system]sort[title]] [[Program Tips]] +[putfirst[]]
>>
>> or this goofy one:
>>
>> [!is[system]sort[title]move:-100[Program Tips]]
>>
>> I'd go with the first.
>>
>> On Wednesday, October 2, 2019 at 12:25:11 AM UTC-4, Suzanne McHale wrote:
>>>
>>> I have tried this filter for one of my Tiddlywikis: *[title[Program 
>>> tips]][!is[system]sort[title]][tags[]!is[system]sort[title]]*. "Program 
>>> tips" is the home/index page and I want it to appear at the top of the 
>>> static HTML page export, followed by all other pages 
>>> (alphabetically-sorted) then tags pages. However, "Program tips" only 
>>> appears in the alphabetically-sorted list of pages in the second 
>>> expression, and I can't think of the right syntax to force it to appear 
>>> first. (I have also tried *[name[Home]]* which I put in one of the 
>>> fields of "Program tips", but this did not work either.)
>>>
>>> Oddly, if I write the filter as *[!is[system]sort[title]][title[Program 
>>> tips]][tags[]!is[system]sort[title]]*, "Program tips" will then appear 
>>> after the alphabetically-sorted page titles. There seems to be something in 
>>> the *[!is[system]sort[title]]* filter that overrrides other commands. 
>>> Hope that all makes sense! What am I doing wrong?
>>>
>>

-- 
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/18a26969-4b7c-43da-94af-e030088ea046%40googlegroups.com.


[tw5] Re: Advanced search - filter expressions: how do I force a particular tiddler to appear at the top when exporting to a static page?

2019-10-05 Thread Flibbles
Sounds good. Glad it works for you.

For my own amusement, I was actually curious if there'd be a way to filter 
out all system tagged tiddlers without having to specify 
$:/tags/Stylesheet, $:/tags/Macro, and any others you may use

[!is[system]] -[tags[]is[system]tagging[]] +[sort[title]] [[Program tips]] 
+[putfirst[]] [tags[]!is[system]sort[title]] [[contents]]

If what you already have works, then it works. I just did this mostly for 
my own amusement, and thought I'd share.

-Flibbles

On Saturday, October 5, 2019 at 1:00:49 AM UTC-4, Suzanne McHale wrote:
>
> Hi, that did have the result I wanted, thanks! The expression is now: 
>
> *[!is[system]!tag[$:/tags/Stylesheet]!tag[$:/tags/Macro]!tag[$:/tags/SideBar]sort[title]]
>  
> [[Program tips]] +[putfirst[]] [tags[]!is[system]sort[title]] [[contents]]* - 
> exclude some pages tagged with $:/tags/, *then* sort other tiddlers by 
> title, but put the Home page at the top, *then* follow this with tags 
> contents pages, *then* the contents page (which lists all tags with their 
> contents - a sort of meta page) last (at the bottom of the single page). 
>
> On Friday, October 4, 2019 at 8:52:09 PM UTC+10, Flibbles wrote:
>>
>> Sounds like you want something like
>>
>> [!is[system]!tag[$:/tags/Stylesheet]!tag[$:/tags/Macro]sort[title]] [[
>> Program Tips]] +[putfirst[]] [[In conclusion]]
>>
>> To put an item in last place, all you have to do is list it at the end. 
>> Extra filter expressions dominantly append. So if an item shows up twice, 
>> it'll take the last one. Thus [[In conclusion]] will now be the last. 
>> There's no need to do any [putlast[]] stuff (which is designed to put the 
>> first listItem last).
>>
>> Though this assumes [[In conclusion]] (or whatever you use) exists. If 
>> there's a chance it doesn't, then end with [[In conclusion]is[tiddler]] 
>> instead, which just prevents the filter from appending a non-existent title.
>>
>> -Flibbles
>>
>

-- 
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/6bcb84a0-e364-4b43-9e0a-99d131187f8f%40googlegroups.com.


[tw5] Re: Query: Would it be possible to make a "filter builder?"

2019-10-05 Thread Flibbles
In response to your message in that other thread, I'm having trouble 
visualizing how a dialog or a wizard could help in building filters. Like, 
maybe something with arrows, or something that provides interactive 
completion, like as you type in an operand, it gives operand documentation.

That's about all I can see that wouldn't be a humongous endeavor.

On Sunday, September 1, 2019 at 3:56:14 AM UTC-4, @TiddlyTweeter wrote:
>
> Just wondering, given the range of Operators now, whether a tool would be 
> possible that can "build a filter".
>
> 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/38091e1d-3352-4f84-aad6-1972472d53f8%40googlegroups.com.


[tw5] Re: Advanced search - filter expressions: how do I force a particular tiddler to appear at the top when exporting to a static page?

2019-10-03 Thread Flibbles
Maybe I'm late to the party, but the following seem to work too:

[!is[system]sort[title]] [[Program Tips]] +[putfirst[]]

or this goofy one:

[!is[system]sort[title]move:-100[Program Tips]]

I'd go with the first.

On Wednesday, October 2, 2019 at 12:25:11 AM UTC-4, Suzanne McHale wrote:
>
> I have tried this filter for one of my Tiddlywikis: *[title[Program 
> tips]][!is[system]sort[title]][tags[]!is[system]sort[title]]*. "Program 
> tips" is the home/index page and I want it to appear at the top of the 
> static HTML page export, followed by all other pages 
> (alphabetically-sorted) then tags pages. However, "Program tips" only 
> appears in the alphabetically-sorted list of pages in the second 
> expression, and I can't think of the right syntax to force it to appear 
> first. (I have also tried *[name[Home]]* which I put in one of the fields 
> of "Program tips", but this did not work either.)
>
> Oddly, if I write the filter as *[!is[system]sort[title]][title[Program 
> tips]][tags[]!is[system]sort[title]]*, "Program tips" will then appear 
> after the alphabetically-sorted page titles. There seems to be something in 
> the *[!is[system]sort[title]]* filter that overrrides other commands. 
> Hope that all makes sense! What am I doing wrong?
>

-- 
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/ca0b0dc6-780d-4921-bd4a-4aa2f1af3df6%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-03-14 Thread Flibbles
Sooo, this is a strange case. What's happening with your macro call is that 
the string "[[ tiddler_name ]]" is being transplanted directly into a chunk 
of text which is then being interpreted as wikitext. And it's only *then* 
that tiddlywiki recognizes it as a link. The parameters sum and src are 
otherwise treated as plaintext since those parameters aren't specified as 
being links OR references. And it wouldn't be possible to configure Relink 
to view them as such since they're valid as either, or neither. I really 
wish Relink were completely a "It just works" plugin, but this is one case 
where you'll need to do something so Relink will recognize what to do.

1.
\define link-to-tiddler() [[ tiddler_name ]]


<$macrocall $name="details" sum=<> />




2.
<$macrocall $name="details" src={{ tiddler_name }} />





I guess your full solution may be:
\define link-to-tiddler() [[ tiddler_name ]]


<$macrocall $name="details" sum=<> src={{ tiddler_name }} 
/>

Hope this helps.
Flibbles

On Saturday, March 14, 2020 at 9:16:35 PM UTC-4, Rahul Kashyap wrote:
>
> Dear Flibbles,
>
> Thanks a lot for this plugin. This gives another reason to stick with TW 
> as I've been developing tons of materials here. 
> However, I was trying to understand how to provide my own custom list for 
> any particular macro. 
>
> For example, I use < tiddler_name }}" >> macro (from https://kookma.github.io/TW-Shiraz/) a 
> lot in order to maintain a heirarchy of material for graduate materials and 
> research work for my work (in Physics). 
> Relink wasn't updating the links and transclusions in the parameters, sum, 
> and src. How should I make Relink recognize that?  
>
> Thanks again,  
> -Rahul
>
> On Friday, September 6, 2019 at 8:26:47 PM UTC-4, Flibbles wrote:
>>
>> Version 1.5 released. Macro parameter relinking is now supported. It 
>> comes with its own whitelist.
>>
>> (e.g. <> or <$macrocall $name=myMacro 
>> param="tiddlerNameToRelink" />)
>>
>> Now Relink can rename any kind of WikiText pattern.
>>
>> Also, bugfixes.
>>
>> -Flibbles
>>
>> On Sunday, September 1, 2019 at 10:27:19 PM UTC-4, Flibbles wrote:
>>>
>>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>>
>>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>>> filters. It's highly customizable, but it will also work out of the box. 
>>> It's robust, and can handle bizarre name changes. It works through 
>>> whitelisting, so it doesn't change plaintext instances of a title, or other 
>>> instances where an updated would be undesirable. It's also well tested (but 
>>> still really new!!). It should be comprehensive.
>>>
>>> Otherwise, I really hope everyone gets good use out of this. Having 
>>> written it, I completely understand why this isn't a core feature. It was 
>>> *hard 
>>> as crap*! There are so many edge cases! I'm sure more will still crop 
>>> up.
>>>
>>> *Edit**: It now also supports macros, making it a fully comprehensive 
>>> relinking plugin.*
>>>
>>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>>
>>> Source code here <https://github.com/flibbles/tw5-relink>.
>>>
>>> I would absolutely love to get some feedback. I really hope this helps 
>>> people.
>>>
>>> -Flibbles
>>>
>>

-- 
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/f71f2953-c46e-4269-95d4-5401815cb926%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-03-14 Thread Flibbles
Hold up. If you find yourself making this exact pattern a lot: 
<>

Then you could wrap it in another macro to keep it neat.

\define details_for_tiddler(tiddler) <$macrocall $name="details" sum="[[ 
$tiddler$ ]]" src="{{ $tiddler$ }}" />

Then you could configure Relink to relink the "tiddler" parameter of 
"details_for_tiddler" quite simply, since it would always be a title 
parameter. You'd go to the Relink configuration page, then to "Macros", and 
you'd "Add a new macro parameter" where "macro"="details_for_tiddler" and 
"parameter"="tiddler". After you add, the type would default to "title", 
which is what you want.

-Flibbles

On Saturday, March 14, 2020 at 9:52:51 PM UTC-4, Flibbles wrote:
>
> Sooo, this is a strange case. What's happening with your macro call is 
> that the string "[[ tiddler_name ]]" is being transplanted directly into a 
> chunk of text which is then being interpreted as wikitext. And it's only 
> *then* that tiddlywiki recognizes it as a link. The parameters sum and 
> src are otherwise treated as plaintext since those parameters aren't 
> specified as being links OR references. And it wouldn't be possible to 
> configure Relink to view them as such since they're valid as either, or 
> neither. I really wish Relink were completely a "It just works" plugin, but 
> this is one case where you'll need to do something so Relink will recognize 
> what to do.
>
> 1.
> \define link-to-tiddler() [[ tiddler_name ]]
>
>
> <$macrocall $name="details" sum=<> />
>
> 
>
>
> 2.
> <$macrocall $name="details" src={{ tiddler_name }} />
>
>
> 
>
>
> I guess your full solution may be:
> \define link-to-tiddler() [[ tiddler_name ]]
>
>
> <$macrocall $name="details" sum=<> src={{ tiddler_name }} 
> />
>
> Hope this helps.
> Flibbles
>
> On Saturday, March 14, 2020 at 9:16:35 PM UTC-4, Rahul Kashyap wrote:
>>
>> Dear Flibbles,
>>
>> Thanks a lot for this plugin. This gives another reason to stick with TW 
>> as I've been developing tons of materials here. 
>> However, I was trying to understand how to provide my own custom list for 
>> any particular macro. 
>>
>> For example, I use <> tiddler_name }}" >> macro (from https://kookma.github.io/TW-Shiraz/) a 
>> lot in order to maintain a heirarchy of material for graduate materials and 
>> research work for my work (in Physics). 
>> Relink wasn't updating the links and transclusions in the parameters, 
>> sum, and src. How should I make Relink recognize that?  
>>
>> Thanks again,  
>> -Rahul
>>
>> On Friday, September 6, 2019 at 8:26:47 PM UTC-4, Flibbles wrote:
>>>
>>> Version 1.5 released. Macro parameter relinking is now supported. It 
>>> comes with its own whitelist.
>>>
>>> (e.g. <> or <$macrocall $name=myMacro 
>>> param="tiddlerNameToRelink" />)
>>>
>>> Now Relink can rename any kind of WikiText pattern.
>>>
>>> Also, bugfixes.
>>>
>>> -Flibbles
>>>
>>> On Sunday, September 1, 2019 at 10:27:19 PM UTC-4, Flibbles wrote:
>>>>
>>>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>>>
>>>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>>>> filters. It's highly customizable, but it will also work out of the box. 
>>>> It's robust, and can handle bizarre name changes. It works through 
>>>> whitelisting, so it doesn't change plaintext instances of a title, or 
>>>> other 
>>>> instances where an updated would be undesirable. It's also well tested 
>>>> (but 
>>>> still really new!!). It should be comprehensive.
>>>>
>>>> Otherwise, I really hope everyone gets good use out of this. Having 
>>>> written it, I completely understand why this isn't a core feature. It was 
>>>> *hard 
>>>> as crap*! There are so many edge cases! I'm sure more will still crop 
>>>> up.
>>>>
>>>> *Edit**: It now also supports macros, making it a fully comprehensive 
>>>> relinking plugin.*
>>>>
>>>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>>>
>>>> Source code here <https://github.com/flibbles/tw5-relink>.
>>>>
>>>> I would absolutely love to get some feedback. I really hope this helps 
>>>> people.
>>>>
>>>> -Flibbles
>>>>
>>>

-- 
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/5224093b-7a8b-49a5-8595-48801778be05%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-03-14 Thread Flibbles
Actually, scratch everything I said. It should be possible for Relink to 
recognize the sum and src parameters. I just need to introduce another 
fieldType. Currently, there is "title", "list", "reference", and "filter". 
If there is a fifth, "wikitext", then macro parameters can be treated as 
such, as well as fields, widget attributes, and list operators.

This'll take me a several days to properly code. My workarounds will work 
in the meantime.

On Saturday, March 14, 2020 at 9:59:02 PM UTC-4, Flibbles wrote:
>
> Hold up. If you find yourself making this exact pattern a lot: 
> <>
>
> Then you could wrap it in another macro to keep it neat.
>
> \define details_for_tiddler(tiddler) <$macrocall $name="details" sum="[[ 
> $tiddler$ ]]" src="{{ $tiddler$ }}" />
>
> Then you could configure Relink to relink the "tiddler" parameter of 
> "details_for_tiddler" quite simply, since it would always be a title 
> parameter. You'd go to the Relink configuration page, then to "Macros", and 
> you'd "Add a new macro parameter" where "macro"="details_for_tiddler" and 
> "parameter"="tiddler". After you add, the type would default to "title", 
> which is what you want.
>
> -Flibbles
>
> On Saturday, March 14, 2020 at 9:52:51 PM UTC-4, Flibbles wrote:
>>
>> Sooo, this is a strange case. What's happening with your macro call is 
>> that the string "[[ tiddler_name ]]" is being transplanted directly into a 
>> chunk of text which is then being interpreted as wikitext. And it's only 
>> *then* that tiddlywiki recognizes it as a link. The parameters sum and 
>> src are otherwise treated as plaintext since those parameters aren't 
>> specified as being links OR references. And it wouldn't be possible to 
>> configure Relink to view them as such since they're valid as either, or 
>> neither. I really wish Relink were completely a "It just works" plugin, but 
>> this is one case where you'll need to do something so Relink will recognize 
>> what to do.
>>
>> 1.
>> \define link-to-tiddler() [[ tiddler_name ]]
>>
>>
>> <$macrocall $name="details" sum=<> />
>>
>> 
>>
>>
>> 2.
>> <$macrocall $name="details" src={{ tiddler_name }} />
>>
>>
>> 
>>
>>
>> I guess your full solution may be:
>> \define link-to-tiddler() [[ tiddler_name ]]
>>
>>
>> <$macrocall $name="details" sum=<> src={{ tiddler_name 
>> }} />
>>
>> Hope this helps.
>> Flibbles
>>
>> On Saturday, March 14, 2020 at 9:16:35 PM UTC-4, Rahul Kashyap wrote:
>>>
>>> Dear Flibbles,
>>>
>>> Thanks a lot for this plugin. This gives another reason to stick with TW 
>>> as I've been developing tons of materials here. 
>>> However, I was trying to understand how to provide my own custom list 
>>> for any particular macro. 
>>>
>>> For example, I use <>> tiddler_name }}" >> macro (from https://kookma.github.io/TW-Shiraz/) a 
>>> lot in order to maintain a heirarchy of material for graduate materials and 
>>> research work for my work (in Physics). 
>>> Relink wasn't updating the links and transclusions in the parameters, 
>>> sum, and src. How should I make Relink recognize that?  
>>>
>>> Thanks again,  
>>> -Rahul
>>>
>>> On Friday, September 6, 2019 at 8:26:47 PM UTC-4, Flibbles wrote:
>>>>
>>>> Version 1.5 released. Macro parameter relinking is now supported. It 
>>>> comes with its own whitelist.
>>>>
>>>> (e.g. <> or <$macrocall $name=myMacro 
>>>> param="tiddlerNameToRelink" />)
>>>>
>>>> Now Relink can rename any kind of WikiText pattern.
>>>>
>>>> Also, bugfixes.
>>>>
>>>> -Flibbles
>>>>
>>>> On Sunday, September 1, 2019 at 10:27:19 PM UTC-4, Flibbles wrote:
>>>>>
>>>>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>>>>
>>>>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, 
>>>>> and filters. It's highly customizable, but it will also work out of the 
>>>>> box. It's robust, and can handle bizarre name changes. It works through 
>>>>> whitelisting, so it doesn't change plaintext instances of a title, or 
>>>

Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-04-13 Thread Flibbles
@Peter Buyze: I'm glad! It definitely is a needed feature for large 
projects. I built it out of need.

@Lin Onetwo: I think this was probably meant for Kookma? Other people are 
welcome into include Relink in bundles, but I haven't the ability to do so 
myself.

-Flibbles

On Sunday, April 12, 2020 at 4:08:48 AM UTC-4, Peter Buyze wrote:
>
> Fibbles, I am new to TW, so here's my 2 cents worth.
>
> This is a feature that I have missed in many a note-taking app. Even in 
> what I currently consider my default, beloved note-taking apps, this 
> feature is absent.
>
> I came across it in Tomboy, but that is such a simple, basic app that I 
> did not bother. Maybe there are other, more feature rich apps, but I have 
> not encountered any.
>
> From what I have seen so far your plug-in works well and one of the 
> features to persuade me to go on with TW.
>
> -- 
> Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
> https://tutanota.com
>
>
> 12 Apr 2020, 09:45 by lindo...@gmail.com :
>
> Why not upload to a plugin library like main library or 
> Kookma Plugin Library 
> <http://127.0.0.1:11012/#%24%3A%2Fconfig%2FKookmaPluginLibrary>?
>
> 在 2019年9月2日星期一 UTC+8上午10:27:19,Flibbles写道:
>
> I present Relink <https://flibbles.github.io/tw5-relink/>!
>
> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
> filters. It's highly customizable, but it will also work out of the box. 
> It's robust, and can handle bizarre name changes. It works through 
> whitelisting, so it doesn't change plaintext instances of a title, or other 
> instances where an updated would be undesirable. It's also well tested (but 
> still really new!!). It should be comprehensive.
>
> Otherwise, I really hope everyone gets good use out of this. Having 
> written it, I completely understand why this isn't a core feature. It was 
> *hard 
> as crap*! There are so many edge cases! I'm sure more will still crop up.
>
> *Edit**: It now also supports macros, making it a fully comprehensive 
> relinking plugin.*
>
> Demo page here <https://flibbles.github.io/tw5-relink/>.
>
> Source code here <https://github.com/flibbles/tw5-relink>.
>
> I would absolutely love to get some feedback. I really hope this helps 
> people.
>
> -Flibbles
>
>
> --
> 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 tiddl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/20c7abd8-5f86-45d1-a07a-c47190f3290c%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywiki/20c7abd8-5f86-45d1-a07a-c47190f3290c%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
>

-- 
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/13f3d971-ab9e-4b01-9bef-d3ad594f3117%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-04-10 Thread Flibbles
Rahul Kashyap & Kalcifer Kandari,

Macro parameters can now be configured to relink as wikitext as of v1.8.0, 
released tonight.

Enjoy!
Flibbles


On Saturday, March 14, 2020 at 9:16:35 PM UTC-4, Rahul Kashyap wrote:
>
> Dear Flibbles,
>
> Thanks a lot for this plugin. This gives another reason to stick with TW 
> as I've been developing tons of materials here. 
> However, I was trying to understand how to provide my own custom list for 
> any particular macro. 
>
> For example, I use < tiddler_name }}" >> macro (from https://kookma.github.io/TW-Shiraz/) a 
> lot in order to maintain a heirarchy of material for graduate materials and 
> research work for my work (in Physics). 
> Relink wasn't updating the links and transclusions in the parameters, sum, 
> and src. How should I make Relink recognize that?  
>
> Thanks again,  
> -Rahul
>
> On Friday, September 6, 2019 at 8:26:47 PM UTC-4, Flibbles wrote:
>>
>> Version 1.5 released. Macro parameter relinking is now supported. It 
>> comes with its own whitelist.
>>
>> (e.g. <> or <$macrocall $name=myMacro 
>> param="tiddlerNameToRelink" />)
>>
>> Now Relink can rename any kind of WikiText pattern.
>>
>> Also, bugfixes.
>>
>> -Flibbles
>>
>> On Sunday, September 1, 2019 at 10:27:19 PM UTC-4, Flibbles wrote:
>>>
>>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>>
>>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>>> filters. It's highly customizable, but it will also work out of the box. 
>>> It's robust, and can handle bizarre name changes. It works through 
>>> whitelisting, so it doesn't change plaintext instances of a title, or other 
>>> instances where an updated would be undesirable. It's also well tested (but 
>>> still really new!!). It should be comprehensive.
>>>
>>> Otherwise, I really hope everyone gets good use out of this. Having 
>>> written it, I completely understand why this isn't a core feature. It was 
>>> *hard 
>>> as crap*! There are so many edge cases! I'm sure more will still crop 
>>> up.
>>>
>>> *Edit**: It now also supports macros, making it a fully comprehensive 
>>> relinking plugin.*
>>>
>>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>>
>>> Source code here <https://github.com/flibbles/tw5-relink>.
>>>
>>> I would absolutely love to get some feedback. I really hope this helps 
>>> people.
>>>
>>> -Flibbles
>>>
>>

-- 
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/4e93e052-9d04-4d46-8f1a-2d57897cffa5%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-04-23 Thread Flibbles
*New Feature!*

The \relink pragma! You can use it to locally declare macro parameters for 
relinking. For example:

\relink myMacro filter:filter template:wikitext
> \define say-list(filter, template)
> ...
> \end
>

You no longer have to add entries to the configuration whitelist for all 
the little macros you've got laying around. (But your \pragma declarations 
will still show up there.) I've got it all documented right here. 


Let me know what you think. This is probably the last major for Relink 
<https://flibbles.github.io/tw5-relink/>. It seems to me it accomplishes 
everything it could accomplish.

-Flibbles


On Monday, April 13, 2020 at 6:06:57 PM UTC-4, Flibbles wrote:
>
> @Peter Buyze: I'm glad! It definitely is a needed feature for large 
> projects. I built it out of need.
>
> @Lin Onetwo: I think this was probably meant for Kookma? Other people are 
> welcome into include Relink in bundles, but I haven't the ability to do so 
> myself.
>
> -Flibbles
>
> On Sunday, April 12, 2020 at 4:08:48 AM UTC-4, Peter Buyze wrote:
>>
>> Fibbles, I am new to TW, so here's my 2 cents worth.
>>
>> This is a feature that I have missed in many a note-taking app. Even in 
>> what I currently consider my default, beloved note-taking apps, this 
>> feature is absent.
>>
>> I came across it in Tomboy, but that is such a simple, basic app that I 
>> did not bother. Maybe there are other, more feature rich apps, but I have 
>> not encountered any.
>>
>> From what I have seen so far your plug-in works well and one of the 
>> features to persuade me to go on with TW.
>>
>> -- 
>> Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
>> https://tutanota.com
>>
>>
>> 12 Apr 2020, 09:45 by lindo...@gmail.com:
>>
>> Why not upload to a plugin library like main library or 
>> Kookma Plugin Library 
>> <http://127.0.0.1:11012/#%24%3A%2Fconfig%2FKookmaPluginLibrary>?
>>
>> 在 2019年9月2日星期一 UTC+8上午10:27:19,Flibbles写道:
>>
>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>
>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>> filters. It's highly customizable, but it will also work out of the box. 
>> It's robust, and can handle bizarre name changes. It works through 
>> whitelisting, so it doesn't change plaintext instances of a title, or other 
>> instances where an updated would be undesirable. It's also well tested (but 
>> still really new!!). It should be comprehensive.
>>
>> Otherwise, I really hope everyone gets good use out of this. Having 
>> written it, I completely understand why this isn't a core feature. It was 
>> *hard 
>> as crap*! There are so many edge cases! I'm sure more will still crop up.
>>
>> *Edit**: It now also supports macros, making it a fully comprehensive 
>> relinking plugin.*
>>
>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>
>> Source code here <https://github.com/flibbles/tw5-relink>.
>>
>> I would absolutely love to get some feedback. I really hope this helps 
>> people.
>>
>> -Flibbles
>>
>>
>> --
>> 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 tiddl...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/20c7abd8-5f86-45d1-a07a-c47190f3290c%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/20c7abd8-5f86-45d1-a07a-c47190f3290c%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>>

-- 
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/4e6c40b4-1130-4e45-bc83-2fcefa4efb1a%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-04-24 Thread Flibbles
Wow. Yeah. looks like it is. Looks like it's up from 143K. Guess I was a 
little liberal about it, separating out all the language strings and such. 
Turns out Relinking was a fair bit more complicated than I expected. Hope 
that's not a problem.

On Friday, April 24, 2020 at 4:34:43 AM UTC-4, Mohammad wrote:
>
> Hi Filbbles,
>  Thank you for update. A minor comment: the plugin size seems  +150kB
>   is this the minimum size?
>
> --Mohammad
>
> On Friday, April 24, 2020 at 8:30:37 AM UTC+4:30, Flibbles wrote:
>>
>> *New Feature!*
>>
>> The \relink pragma! You can use it to locally declare macro parameters 
>> for relinking. For example:
>>
>> \relink myMacro filter:filter template:wikitext
>>> \define myMacro(filter, template)
>>> ...
>>> \end
>>>
>>
>> You no longer have to add entries to the configuration whitelist for all 
>> the little macros you've got laying around. (But your \pragma declarations 
>> will still show up there.) I've got it all documented right here. 
>> <http://goog_1536791232>
>>
>> Let me know what you think. This is probably the last major for Relink 
>> <https://flibbles.github.io/tw5-relink/>. It seems to me it accomplishes 
>> everything it could accomplish.
>>
>> -Flibbles
>>
>>
>> On Monday, April 13, 2020 at 6:06:57 PM UTC-4, Flibbles wrote:
>>>
>>> @Peter Buyze: I'm glad! It definitely is a needed feature for large 
>>> projects. I built it out of need.
>>>
>>> @Lin Onetwo: I think this was probably meant for Kookma? Other people 
>>> are welcome into include Relink in bundles, but I haven't the ability to do 
>>> so myself.
>>>
>>> -Flibbles
>>>
>>> On Sunday, April 12, 2020 at 4:08:48 AM UTC-4, Peter Buyze wrote:
>>>>
>>>> Fibbles, I am new to TW, so here's my 2 cents worth.
>>>>
>>>> This is a feature that I have missed in many a note-taking app. Even in 
>>>> what I currently consider my default, beloved note-taking apps, this 
>>>> feature is absent.
>>>>
>>>> I came across it in Tomboy, but that is such a simple, basic app that I 
>>>> did not bother. Maybe there are other, more feature rich apps, but I have 
>>>> not encountered any.
>>>>
>>>> From what I have seen so far your plug-in works well and one of the 
>>>> features to persuade me to go on with TW.
>>>>
>>>> -- 
>>>> Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
>>>> https://tutanota.com
>>>>
>>>>
>>>> 12 Apr 2020, 09:45 by lindo...@gmail.com:
>>>>
>>>> Why not upload to a plugin library like main library or 
>>>> Kookma Plugin Library 
>>>> <http://127.0.0.1:11012/#%24%3A%2Fconfig%2FKookmaPluginLibrary>?
>>>>
>>>> 在 2019年9月2日星期一 UTC+8上午10:27:19,Flibbles写道:
>>>>
>>>> I present Relink <https://flibbles.github.io/tw5-relink/>!
>>>>
>>>> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
>>>> filters. It's highly customizable, but it will also work out of the box. 
>>>> It's robust, and can handle bizarre name changes. It works through 
>>>> whitelisting, so it doesn't change plaintext instances of a title, or 
>>>> other 
>>>> instances where an updated would be undesirable. It's also well tested 
>>>> (but 
>>>> still really new!!). It should be comprehensive.
>>>>
>>>> Otherwise, I really hope everyone gets good use out of this. Having 
>>>> written it, I completely understand why this isn't a core feature. It was 
>>>> *hard 
>>>> as crap*! There are so many edge cases! I'm sure more will still crop 
>>>> up.
>>>>
>>>> *Edit**: It now also supports macros, making it a fully comprehensive 
>>>> relinking plugin.*
>>>>
>>>> Demo page here <https://flibbles.github.io/tw5-relink/>.
>>>>
>>>> Source code here <https://github.com/flibbles/tw5-relink>.
>>>>
>>>> I would absolutely love to get some feedback. I really hope this helps 
>>>> people.
>>>>
>>>> -Flibbles
>>>>
>>>>
>>>> --
>>>> 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 tiddl...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/tiddlywiki/20c7abd8-5f86-45d1-a07a-c47190f3290c%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/tiddlywiki/20c7abd8-5f86-45d1-a07a-c47190f3290c%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>>
>>>>

-- 
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/e8cfde68-261d-4274-ac33-06963ff35185%40googlegroups.com.


Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-04-30 Thread Flibbles
So I've decided to make such a plugin, and I'd like feedback.

Here it is: https://flibbles.github.io/tw5-xml/
It demonstrates the features as they are right now.

It uses an <$xsl> widget to iterate through XML tiddlers using xpath. It's 
nifty, though I'm not sure of the name. Maybe it should be <$xml> or 
<$xpath>, because it's only vaguely similar to xslt. I looked into 
literally using xslt, but it really didn't fit well with tiddlywiki. And 
using a widget like this lets you mix and match wikitext and xpath however 
you want, and I think it's just as powerful.

Besides the attribute <$xsl for-each>, I'm considering <$xsl value-of>, 
which will behave just like its xslt equivalent. Because otherwise, users 
will have to do stuff like <$xsl for-each="./@oneAttribute" 
variable="attr"><> just to spit out one value. You can see 
what I mean in the "nested" tab of the transform demo. It's *cumbersome*.

I'm also planning to add a filter operator. I'm thinking [xpath[]] or 
[xml[]] to navigate input titles by the xpath operand. Again, still haven't 
settled on a name.

I'd like to have something like, {{myFile##xpath/indexer}} be a thing, but 
I'd need to work with Jermolene about making the textReferences more 
extensible first.

I'm really looking for any feedback at all, from anyone. I'd like this to 
gel as much as possible to Tiddlywiki methods.

-Flibbles

On Tuesday, April 28, 2020 at 2:33:30 AM UTC-4, Xavier wrote:
>
> Hi Flibbles,
>
> I'd certainly use such a plugin! The perspective of retrieving data and 
> document chunks from XML with such powerful xpath-like filters is quite 
> exciting. Also I don't forget that XHTML is an XML instance...
>
> Don't hesitate to ask if you want early feeback!
>
> Cheers,
> Xavier.
> Le mar. 28 avr. 2020 à 04:22, Flibbles  > a écrit :
>
>> Thanks for the reply, TonyM.
>>
>> Looks like I'll continue with my plugin. Maybe I'll clean it up and 
>> publish it--just a simple plugin that has some xml tools.
>>
>> I was also thinking about xpath filter operators or reference indexes. ( 
>> {{MyXmlRecipe##food[name="French Toast"]/price}} ), or something like that. 
>> Dunno who'd use it.
>>
>> On Monday, April 27, 2020 at 9:02:59 PM UTC-4, TonyM wrote:
>>>
>>> Flibbles,
>>>
>>> Given xml tags act like custom html tags I would think it may be 
>>> possible to use css and the display but it appears the correct way is xslt
>>>
>>>
>>> https://www.w3schools.com/xml/tryxslt.asp?xmlfile=cdcatalog=cdcatalog
>>>
>>>
>>> 
>>> 
>>> Belgian Waffles
>>> $5.95
>>> 
>>>Two of our famous Belgian Waffles with plenty of real maple syrup
>>>
>>> 650
>>> 
>>> 
>>> Strawberry Belgian Waffles
>>> $7.95
>>> 
>>> Light Belgian waffles covered with strawberries and whipped cream
>>> 
>>> 900
>>> 
>>> 
>>> Berry-Berry Belgian Waffles
>>> $8.95
>>> 
>>> Belgian waffles covered with assorted fresh berries and whipped cream
>>> 
>>> 900
>>> 
>>> 
>>> French Toast
>>> $4.50
>>> 
>>> Thick slices made from our homemade sourdough bread
>>> 
>>> 600
>>> 
>>> 
>>> Homestyle Breakfast
>>> $6.95
>>> 
>>> Two eggs, bacon or sausage, toast, and our ever-popular hash browns
>>> 
>>> 950
>>> 
>>> 
>>> source https://www.w3schools.com/xml/default.asp
>>>
>>> Also there is some codemirror or highlight support for XML
>>>
>>> Regards
>>> Tony
>>>
>>> On Tuesday, April 28, 2020 at 10:54:33 AM UTC+10, TonyM wrote:
>>>>
>>>> Flibbles,
>>>>
>>>> It really depends on what features and functions you want to achieve 
>>>> with XML. The closest comprehensive solution is 
>>>> https://joshuafontany.github.io/TW5-JsonMangler/ but this is for JSON.
>>>>
>>>>- There has also being work on pulling tags and tag values from 
>>>>html which would be very similar to some XML cases.
>>>>- I think there may even have being an XML editor written but I 
>>>>cant find it.
>>>>- There is also a level of support already through html tag 
>>>>mechanisms.
>>>>- We would benefit from some widgets and filter opera

[tw5] XML plugin for Tiddlywiki??

2020-04-27 Thread Flibbles
 Hey all,

I need some basic support for XML in tiddlywiki. And I can’t find any.

I just wrote a simple xml importer/exporter plugin. Like:


 
  MyTitle
  Text…
  …
 



And I’m also looking into having *text/xml* as a tiddler type, and display 
it. And maybe apply xslt to it. I’m already about 40% towards having my own 
plugin, but I’m really surprised that this kind of stuff doesn’t already 
exist.

I’ve searched. Am I overlooking something?

-Flibbles

-- 
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/25651174-6385-4d85-92f0-15ba3ee1447c%40googlegroups.com.


Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-05-01 Thread Flibbles
Huh. Wrapping it in <$tiddler> should have worked. This does:

<$tiddler tiddler="myRecipe.xml">
<$xsl for-each="/recipe/ingredients/ingredient">

<>




But the plugin isn't very robust yet since it's just a proof-of-concept. 
Could you send me what you have?

Also, I think I'll probably change the widget to <$xpath> too. Not many 
Tiddlywiki users know what xpath is, but it's more apropos than <$xml>.

-Flibbles

Are you able to send me what you have?

On Friday, May 1, 2020 at 5:57:12 AM UTC-4, Xavier Cazin wrote:
>
> Hi Flibbles,
>
> Thanks a lot for sharing! Having dealt with much XSLT in a previous life, 
> I planned to make useful comments, but now that I've seen your approach, 
> I've only this one: this is brilliant! 
>
> If you eventually make a filter (I vote for [xpath[]]) then, would the 
> current behaviour of <$xsl variable=mynode foreach="/mypath/to/a/node"> be 
> different from <$list filter=[xpath["/mypath/to/a/node"]] variable=mynode > 
> ?
>
> By the way, it seems that I would use instructions on how to test the 
> widget with a custom XML file, aside Demo.xml: I tried to surround a 
> transform with <$tiddler tiddler="mycustomxml"> to no avail.
>
> Cheers,
> -- Xavier.
>
>
> On Fri, May 1, 2020 at 2:50 AM Flibbles  > wrote:
>
>> So I've decided to make such a plugin, and I'd like feedback.
>>
>> Here it is: https://flibbles.github.io/tw5-xml/
>> It demonstrates the features as they are right now.
>>
>> It uses an <$xsl> widget to iterate through XML tiddlers using xpath. 
>> It's nifty, though I'm not sure of the name. Maybe it should be <$xml> 
>> or <$xpath>, because it's only vaguely similar to xslt. I looked into 
>> literally using xslt, but it really didn't fit well with tiddlywiki. And 
>> using a widget like this lets you mix and match wikitext and xpath however 
>> you want, and I think it's just as powerful.
>>
>> Besides the attribute <$xsl for-each>, I'm considering <$xsl value-of>, 
>> which will behave just like its xslt equivalent. Because otherwise, users 
>> will have to do stuff like <$xsl for-each="./@oneAttribute" 
>> variable="attr"><> just to spit out one value. You can see 
>> what I mean in the "nested" tab of the transform demo. It's *cumbersome*.
>>
>> I'm also planning to add a filter operator. I'm thinking [xpath[]] or 
>> [xml[]] to navigate input titles by the xpath operand. Again, still 
>> haven't settled on a name.
>>
>> I'd like to have something like, {{myFile##xpath/indexer}} be a thing, 
>> but I'd need to work with Jermolene about making the textReferences more 
>> extensible first.
>>
>> I'm really looking for any feedback at all, from anyone. I'd like this to 
>> gel as much as possible to Tiddlywiki methods.
>>
>> -Flibbles
>>
>> On Tuesday, April 28, 2020 at 2:33:30 AM UTC-4, Xavier wrote:
>>>
>>> Hi Flibbles,
>>>
>>> I'd certainly use such a plugin! The perspective of retrieving data and 
>>> document chunks from XML with such powerful xpath-like filters is quite 
>>> exciting. Also I don't forget that XHTML is an XML instance...
>>>
>>> Don't hesitate to ask if you want early feeback!
>>>
>>> Cheers,
>>> Xavier.
>>> Le mar. 28 avr. 2020 à 04:22, Flibbles  a écrit :
>>>
>>>> Thanks for the reply, TonyM.
>>>>
>>>> Looks like I'll continue with my plugin. Maybe I'll clean it up and 
>>>> publish it--just a simple plugin that has some xml tools.
>>>>
>>>> I was also thinking about xpath filter operators or reference indexes. 
>>>> ( {{MyXmlRecipe##food[name="French Toast"]/price}} ), or something like 
>>>> that. Dunno who'd use it.
>>>>
>>>> On Monday, April 27, 2020 at 9:02:59 PM UTC-4, TonyM wrote:
>>>>>
>>>>> Flibbles,
>>>>>
>>>>> Given xml tags act like custom html tags I would think it may be 
>>>>> possible to use css and the display but it appears the correct way is xslt
>>>>>
>>>>>
>>>>> https://www.w3schools.com/xml/tryxslt.asp?xmlfile=cdcatalog=cdcatalog
>>>>>
>>>>>
>>>>> 
>>>>> 
>>>>> Belgian Waffles
>>>>> $5.95
>>>>> 
>>>>>Two of our famous Belgian Waffles with plenty of real maple syrup
>>>>>   

Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-05-01 Thread Flibbles
I'm trying to add namespace support now, and I have a question for you, 
Xavier, since you seem to have more experience with them.

Are they actually this awful?

Named namespaces aren't too bad. Just tie the prefix to the url, (like nm 
to http://namespace.com) and you can 
/nm:call/nm:elements/nm:all/nm:the/nm:way/nm:down.

But if you use default namespaces, the standard XPath practice is to /
[local-name()='make']/[local-name()='your']/[local-name()='paths']/
[local-name()='like']/[local-name()='this'].

Is this for real? Is it really that bad? It looks like the best alternative 
I can do is make it so any undeclared prefix can act as the default 
namespace, but I get the sense that's not an expected practice.

-Flibbles

-- 
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/41ba7ea9-0477-4409-86fe-35f7b2167a6b%40googlegroups.com.


Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-05-03 Thread Flibbles
Xavier, I totally agree. Having to prefix those default namespaces in your 
queries is not optimal.

My last message may have given the impression that my current solution was 
my choice, but it was a choice the same way saying you quit right after 
your boss fires you is a choice. The browsers are all limited to XPath 1.0, 
and this is taken straight from the MDN documentation:

XPath defines QNames without a prefix to match only elements in the null 
> namespace. There is no way in XPath to pick up the default namespace as 
> applied to a regular element reference (e.g., p[@id='_myid'] for 
> xmlns='http://www.w3.org/1999/xhtml'). To match default elements in a 
> non-null namespace, you either have to refer to a particular element using 
> a form such as ['namespace-uri()='http://www.w3.org/1999/xhtml' and 
> name()='p' and @id='_myid'] (this approach 
> <https://developer.mozilla.org/en-US/docs/Web/XPath/Introduction_to_using_XPath_in_JavaScript#Using_XPath_functions_to_reference_elements_with_a_default_namespace>
>  
> works well for dynamic XPath's where the namespaces might not be known) or 
> use prefixed name tests, and create a namespace resolver mapping the prefix 
> to the namespace.
>

If I wanted to allow implied default namespaces in the queries possible, 
I'd either need to dynamically remove namespaces from the XML document (my 
first few attempts at this didn't work). Or dynamically add the namespace 
prefixes to the queries (I... I really don't want to do this. This is one 
step below reimplementing XPath for myself.)

I'll continue to look into ways to improve default namespace support; I'll 
try scrubbing namespaces from the DOM again, but for now, the current 
implementation may be what we get.

-Flibbles

-- 
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/b74da421-a4ff-45b6-8258-dd3c31d1e10f%40googlegroups.com.


Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-05-02 Thread Flibbles

Okay. I think I found the proper solution. I have examples and short 
documentation here <https://flibbles.github.io/tw5-xml/>. Basically, when 
elements have namespaces, whether explicit or default, the xpath wants a 
prefix to go with it. In your use-case, you'd do this:


<$xpath xmlns:onix="http://ns.editeur.org/onix/3.0/reference;
xmlns:ns4="http://www.w3.org/1999/xhtml;
for-each="/onix:ONIXMessage/onix:Product/*/onix:Text/ns4:p/text()"
variable="foo">
  <>




It's a little more verbose than what you were proposing, but the upside is 
that this will never suffer from ambiguous namespaces if multiple default 
namespaces are used within one document. Also, you don't have to add onix: 
prefixes throughout your own documents.

I do have one neat trick though. That xmlns:onix attribute will be 
available in all nested <$xpath> widgets. You could even define xmlns:onix 
using <$set> or <$vars>. Or you can globally define it with \define 
xmlns:onix() in a global macro tiddler. That should help trim down 
verbosity.

Unless you see a flaw with this, I *think* is is probably the way to go. 
Now that I better understand namespaces, being explicit with all namespaces 
in an XPath query actually makes sense to me. No ambiguity. Queries can 
traverse documents with a litany of changing namespace scopes.

-Flibbles

-- 
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/dd7264cc-7dd6-4a3f-8417-ef1367042404%40googlegroups.com.


[tw5] Re: XML plugin for Tiddlywiki??

2020-05-02 Thread Flibbles
Tony: That'd be great. I built this so XML could act like 
super-data-tiddlers. So that's what it's mostly good at solving right now. 
But I'd love it if this plugin became the answer for other problem, though  
I may need more feedback on such use-cases to determine how to elaborate 
tw5-xml.

Damon: You're welcome to go ahead. I think the importer and the <$xpath> 
are locked down. Though I'm still in "rapid prototyping" mode. It's all 
pretty slow and buggy at the moment. If you do go ahead, let me know in 
what ways tw5-xml doesn't address your needs. I'd like it to be *the* XML 
solution for Tiddlywiki5.

-- 
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/e0580ea6-da98-456d-8457-f143c6c2b096%40googlegroups.com.


[tw5] Re: XML plugin for Tiddlywiki??

2020-04-27 Thread Flibbles
Thanks for the reply, TonyM.

Looks like I'll continue with my plugin. Maybe I'll clean it up and publish 
it--just a simple plugin that has some xml tools.

I was also thinking about xpath filter operators or reference indexes. ( 
{{MyXmlRecipe##food[name="French Toast"]/price}} ), or something like that. 
Dunno who'd use it.

On Monday, April 27, 2020 at 9:02:59 PM UTC-4, TonyM wrote:
>
> Flibbles,
>
> Given xml tags act like custom html tags I would think it may be possible 
> to use css and the display but it appears the correct way is xslt
>
>
> https://www.w3schools.com/xml/tryxslt.asp?xmlfile=cdcatalog=cdcatalog
>
>
> 
> 
> Belgian Waffles
> $5.95
> 
>Two of our famous Belgian Waffles with plenty of real maple syrup
>
> 650
> 
> 
> Strawberry Belgian Waffles
> $7.95
> 
> Light Belgian waffles covered with strawberries and whipped cream
> 
> 900
> 
> 
> Berry-Berry Belgian Waffles
> $8.95
> 
> Belgian waffles covered with assorted fresh berries and whipped cream
> 
> 900
> 
> 
> French Toast
> $4.50
> 
> Thick slices made from our homemade sourdough bread
> 
> 600
> 
> 
> Homestyle Breakfast
> $6.95
> 
> Two eggs, bacon or sausage, toast, and our ever-popular hash browns
> 
> 950
> 
> 
> source https://www.w3schools.com/xml/default.asp
>
> Also there is some codemirror or highlight support for XML
>
> Regards
> Tony
>
> On Tuesday, April 28, 2020 at 10:54:33 AM UTC+10, TonyM wrote:
>>
>> Flibbles,
>>
>> It really depends on what features and functions you want to achieve with 
>> XML. The closest comprehensive solution is 
>> https://joshuafontany.github.io/TW5-JsonMangler/ but this is for JSON.
>>
>>- There has also being work on pulling tags and tag values from html 
>>which would be very similar to some XML cases.
>>- I think there may even have being an XML editor written but I cant 
>>find it.
>>- There is also a level of support already through html tag 
>>mechanisms.
>>- We would benefit from some widgets and filter operators to 
>>interrogate and write XML but this would be good if it were more general 
>>allowing us to manipulate any htm/xml in 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8201341d-59b4-4b7c-9d0b-77d7b6a85177%40googlegroups.com.


Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-05-10 Thread Flibbles

Hey everyone!

I'm working hard on the release version of tw5-xml, but I was hoping for 
some final feedback on one last thing.

On top of an <$xpath> widget, which parses XML with XPAath, I made another 
widget which parses XML/HTML with css queries, like "div .classname". 
Currently, it's called <$css>, but I'm not sure that's the right name. 
(Maybe <$query>, or <$cssquery>, or <$selector>. Not sure yet. Would love 
your feedback).

Does this widget seem useful? Parsing through HTML is not as needed as 
parsing XML, but there are some neat uses for it. For one, you can use 
<$css> on XML, and <$xpath> on html. And you can use them both at one time. 
i.e.

<$xpath for-each="/document/text">


!!Document


<$css for=each=".classname > p" variable="paragraph">

<>





Other than xhtml embedded in XML, or for SVG, there isn't much need to use 
both at once, but I thought it was nifty.

It was only about 20 lines of extra code once I got everything organized 
right, but I'm concerned this is outside the scope, or no one would need 
this. Are there any of you who could use a widget/filter like this?

The demo site is better filled out, and has examples of this new widget. 
<https://flibbles.github.io/tw5-xml/>

-Flibbles

-- 
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/edadce0a-49cd-4563-9f6c-34adb8fd0e9d%40googlegroups.com.


[tw5] Re: Personal News

2020-05-18 Thread Flibbles
Look forward to hearing from you after you're through it. Good luck.

-Flibbles

-- 
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/c57cd519-2c02-4895-be13-862dee1f825d%40googlegroups.com.


[tw5] Re: [Plugin] XML for Tiddlywiki!! Import, parse, render, and more!

2020-05-14 Thread Flibbles
Eshka, I found some projects suffering similar problems, and I think I may 
have fixed it. Go head and try again.

-Flibbles

On Thursday, May 14, 2020 at 8:11:51 AM UTC-4, Flibbles wrote:
>
> Eshka, could you please tell me what browser you're using?
>
> Unfortunately, due to the nature of this plugin, there will be some 
> cross-platform issues I need to resolve. Every browser implements xmldom 
> it's own way.
>
> -Flibbles
>
> On Thursday, May 14, 2020 at 7:59:50 AM UTC-4, Eskha wrote:
>>
>> Hello Fibbles,
>>
>> While your plugin looks very promising, I have the following error when 
>> landing on your demo site:
>>
>> "TypeError: Argument 1 of DOMParser.constructor does not implement 
>> interface Principal."
>> (Inside the red box "Internal JavaScript Error")
>>
>> Best regard,
>>
>> Eskha
>>
>>

-- 
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/44f9e106-1cae-4050-8ab0-ce1bec7ab4b9%40googlegroups.com.


[tw5] Re: [Plugin] XML for Tiddlywiki!! Import, parse, render, and more!

2020-05-14 Thread Flibbles
Eshka, could you please tell me what browser you're using?

Unfortunately, due to the nature of this plugin, there will be some 
cross-platform issues I need to resolve. Every browser implements xmldom 
it's own way.

-Flibbles

On Thursday, May 14, 2020 at 7:59:50 AM UTC-4, Eskha wrote:
>
> Hello Fibbles,
>
> While your plugin looks very promising, I have the following error when 
> landing on your demo site:
>
> "TypeError: Argument 1 of DOMParser.constructor does not implement 
> interface Principal."
> (Inside the red box "Internal JavaScript Error")
>
> Best regard,
>
> Eskha
>
>

-- 
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/b6d93fb2-a721-4cf3-be35-06e9a0385409%40googlegroups.com.


Re: [tw5] Re: XML plugin for Tiddlywiki??

2020-05-13 Thread Flibbles

Thanks everybody for your help and feedback. I'll be making the official 
release announcement right after this.

PMario: Actually, <$xselect> makes a lot of sense on multiple levels. I 
went with that. Thank you.

TonyM: Yes. CSS Selectors can be used to select elements by tagName. You 
can definitely slurp up all the  tags under some given . All your 
use cases are things my tools will help with, though for some of them, 
you'd still need to write some fancy wikitext. Screen scraping a URL might 
require a little more though... But still! This plugin would be helpful for 
parsing scraped HTML.

-Flibbles

-- 
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/cb001293-35e8-491b-a4ef-cf8669e63aef%40googlegroups.com.


[tw5] [Plugin] XML for Tiddlywiki!! Import, parse, render, and more!

2020-05-13 Thread Flibbles
Name:* tw5-xml*
Version: *1.0.0*
Demo: https://flibbles.github.io/tw5-xml/
Source: https://github.com/flibbles/tw5-xml

Check it out! <https://flibbles.github.io/tw5-xml/> It lets you:

   - Import and export XML, including bundled XML archives including 
   multiple tiddlers.
   - It renders XML tiddlers, and integrates with the tiddlywiki syntax 
   highlighting plugin. It can also render through templates instead using XML 
   processing instructions.
   - Lets you parse XML, HTML, and SVG using the <$xpath> and <$xselect> 
   widgets, which use XPath and CSS selectors to navigate your tiddlers
   - Also comes with the [xpath[]] and [xselect[]] filter operators.


You can use it to:

   - Extract data from your SVG images, or HTML tiddlers, or any kind of 
   XML-related documents
   - Use XML for super-data tiddlers. Step aside, dictionary tiddlers. Your 
   days are over.
   - Auto-transform XML into user-readable data just like with XSLT, but 
   without all the horrors of using XSLT!!


Let me know your thoughts. This is the first release version of tw5-xml, 
but don't let that scare you. It's well tested. If do encounter any 
problems, please let me know.

I'd like this to be the go-to comprehensive XML solution, so if there are 
XML tricks you want Tiddlywiki to do, and this doesn't really help, let me 
know.

-Flibbles

-- 
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/b79c0d8a-6de0-41de-87a8-a04dec619586%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-03-23 Thread Flibbles
So Relink already can relink macro parameters if they're titles, lists, or 
filters. I'm just working on a modification so macro parameters can be 
generalized wikitext as a fourth option. Are you saying that particular 
option is what you need as well?

On Monday, March 23, 2020 at 12:37:13 AM UTC-4, Kalcifer Kandari wrote:
>
> Looking forward to this. Once macro parameters are recognised, renaming a 
> tiddler will go from taking me 10 minutes to taking 0 minutes.
>
> Kalcifer
>
> On Sunday, March 15, 2020 at 2:13:51 AM UTC, Flibbles wrote:
>>
>> Actually, scratch everything I said. It should be possible for Relink to 
>> recognize the sum and src parameters. I just need to introduce another 
>> fieldType. Currently, there is "title", "list", "reference", and "filter". 
>> If there is a fifth, "wikitext", then macro parameters can be treated as 
>> such, as well as fields, widget attributes, and list operators.
>>
>> This'll take me a several days to properly code. My workarounds will work 
>> in the meantime.
>>
>> On Saturday, March 14, 2020 at 9:59:02 PM UTC-4, Flibbles wrote:
>>>
>>> Hold up. If you find yourself making this exact pattern a lot: 
>>> <>
>>>
>>> Then you could wrap it in another macro to keep it neat.
>>>
>>> \define details_for_tiddler(tiddler) <$macrocall $name="details" sum="[[ 
>>> $tiddler$ ]]" src="{{ $tiddler$ }}" />
>>>
>>> Then you could configure Relink to relink the "tiddler" parameter of 
>>> "details_for_tiddler" quite simply, since it would always be a title 
>>> parameter. You'd go to the Relink configuration page, then to "Macros", and 
>>> you'd "Add a new macro parameter" where "macro"="details_for_tiddler" and 
>>> "parameter"="tiddler". After you add, the type would default to "title", 
>>> which is what you want.
>>>
>>> -Flibbles
>>>
>>> On Saturday, March 14, 2020 at 9:52:51 PM UTC-4, Flibbles wrote:
>>>>
>>>> Sooo, this is a strange case. What's happening with your macro call is 
>>>> that the string "[[ tiddler_name ]]" is being transplanted directly into a 
>>>> chunk of text which is then being interpreted as wikitext. And it's only 
>>>> *then* that tiddlywiki recognizes it as a link. The parameters sum and 
>>>> src are otherwise treated as plaintext since those parameters aren't 
>>>> specified as being links OR references. And it wouldn't be possible to 
>>>> configure Relink to view them as such since they're valid as either, or 
>>>> neither. I really wish Relink were completely a "It just works" plugin, 
>>>> but 
>>>> this is one case where you'll need to do something so Relink will 
>>>> recognize 
>>>> what to do.
>>>>
>>>> 1.
>>>> \define link-to-tiddler() [[ tiddler_name ]]
>>>>
>>>>
>>>> <$macrocall $name="details" sum=<> />
>>>>
>>>> 
>>>>
>>>>
>>>> 2.
>>>> <$macrocall $name="details" src={{ tiddler_name }} />
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> I guess your full solution may be:
>>>> \define link-to-tiddler() [[ tiddler_name ]]
>>>>
>>>>
>>>> <$macrocall $name="details" sum=<> src={{ 
>>>> tiddler_name }} />
>>>>
>>>> Hope this helps.
>>>> Flibbles
>>>>
>>>> On Saturday, March 14, 2020 at 9:16:35 PM UTC-4, Rahul Kashyap wrote:
>>>>>
>>>>> Dear Flibbles,
>>>>>
>>>>> Thanks a lot for this plugin. This gives another reason to stick with 
>>>>> TW as I've been developing tons of materials here. 
>>>>> However, I was trying to understand how to provide my own custom list 
>>>>> for any particular macro. 
>>>>>
>>>>> For example, I use <>>>> tiddler_name }}" >> macro (from https://kookma.github.io/TW-Shiraz/) 
>>>>> a lot in order to maintain a heirarchy of material for graduate materials 
>>>>> and research work for my work (in Physics). 
>>>>> Relink wasn't updating the links and transclusions in the parameters, 
>>>>> sum, an

[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-03-23 Thread Flibbles
So that sounds like dangerous territory which would make Relink prone to 
make unwanted changes to people's tiddlers. Are you in a situation where 
you're defining a ton of macros for yourself, and you're tired of going 
into the Relink configuration menu to add its parameters? Because one 
feature I have considered adding is a macro which you can call right after 
defining macros which would declare its parameters right then and there: 
Kinda like:

\define myMacro(tiddler, myFilter, class) ...


<>
<>


That way, you could keep your Relink macro configuration with your macro 
definition.

On Monday, March 23, 2020 at 7:36:57 AM UTC-4, Kalcifer Kandari wrote:
>
> Thinking about it, could there be an option to make all macro parameters 
> recognised as WikiText even if they aren't added to the whitelist, which 
> could then be overridden by whitelist entries? I suppose that would also 
> mean there would need to be an additional 'None' type as well. That would 
> be more intuitive in my mind.
>
> Kalcifer
>
> On Monday, March 23, 2020 at 4:37:13 AM UTC, Kalcifer Kandari wrote:
>>
>> Looking forward to this. Once macro parameters are recognised, renaming a 
>> tiddler will go from taking me 10 minutes to taking 0 minutes.
>>
>> Kalcifer
>>
>> On Sunday, March 15, 2020 at 2:13:51 AM UTC, Flibbles wrote:
>>>
>>> Actually, scratch everything I said. It should be possible for Relink to 
>>> recognize the sum and src parameters. I just need to introduce another 
>>> fieldType. Currently, there is "title", "list", "reference", and "filter". 
>>> If there is a fifth, "wikitext", then macro parameters can be treated as 
>>> such, as well as fields, widget attributes, and list operators.
>>>
>>> This'll take me a several days to properly code. My workarounds will 
>>> work in the meantime.
>>>
>>> On Saturday, March 14, 2020 at 9:59:02 PM UTC-4, Flibbles wrote:
>>>>
>>>> Hold up. If you find yourself making this exact pattern a lot: 
>>>> <>
>>>>
>>>> Then you could wrap it in another macro to keep it neat.
>>>>
>>>> \define details_for_tiddler(tiddler) <$macrocall $name="details" 
>>>> sum="[[ $tiddler$ ]]" src="{{ $tiddler$ }}" />
>>>>
>>>> Then you could configure Relink to relink the "tiddler" parameter of 
>>>> "details_for_tiddler" quite simply, since it would always be a title 
>>>> parameter. You'd go to the Relink configuration page, then to "Macros", 
>>>> and 
>>>> you'd "Add a new macro parameter" where "macro"="details_for_tiddler" and 
>>>> "parameter"="tiddler". After you add, the type would default to "title", 
>>>> which is what you want.
>>>>
>>>> -Flibbles
>>>>
>>>> On Saturday, March 14, 2020 at 9:52:51 PM UTC-4, Flibbles wrote:
>>>>>
>>>>> Sooo, this is a strange case. What's happening with your macro call is 
>>>>> that the string "[[ tiddler_name ]]" is being transplanted directly into 
>>>>> a 
>>>>> chunk of text which is then being interpreted as wikitext. And it's only 
>>>>> *then* that tiddlywiki recognizes it as a link. The parameters sum 
>>>>> and src are otherwise treated as plaintext since those parameters aren't 
>>>>> specified as being links OR references. And it wouldn't be possible to 
>>>>> configure Relink to view them as such since they're valid as either, or 
>>>>> neither. I really wish Relink were completely a "It just works" plugin, 
>>>>> but 
>>>>> this is one case where you'll need to do something so Relink will 
>>>>> recognize 
>>>>> what to do.
>>>>>
>>>>> 1.
>>>>> \define link-to-tiddler() [[ tiddler_name ]]
>>>>>
>>>>>
>>>>> <$macrocall $name="details" sum=<> />
>>>>>
>>>>> 
>>>>>
>>>>>
>>>>> 2.
>>>>> <$macrocall $name="details" src={{ tiddler_name }} />
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>>
>>>>> I guess your full solution may be:
>>>>> \define link-to-tiddler() [[ tiddler_name ]]
>>>>>
>>>>>
>>

[tw5] Re: Creating tiddlers and programmatically modifying them?

2020-03-23 Thread Flibbles
This would be outside the scope of Relink, but  there are ways to 
programmatically fill out a generated tiddler.

\define body()
Dear $(name)$,

I write to inform you that your pet, $(pet)$ has filed for emancipation.
\end

\define createButton()
<$button tooltip="Create new letter" aria-label="new version" class=<>>
<$action-sendmessage $message="tm-new-tiddler" title=<> text=<> 
/>
<$list filter="[prefix[yes]]">
{{$:/core/images/new-button}}

<$list filter="[prefix[yes]]">
<$text text="new letter" />


\end


<$set name="title" value="New Letter">
<$set name="name" value="Wilson">
<$set name="pet" value="snuffles">
<>




This will create a new tiddler. with a variable title, name, and pet.

-Flibbles

On Monday, March 23, 2020 at 9:20:52 PM UTC-4, TonyM wrote:
>
> Folks,
>
> I have a little project where it would be helpful if I could create a 
> tiddler from a template (for its body) but then replace various content 
> within the text or fields with different values.
>
> For example what if the template included ##name## then I had a macro that 
> would replace in the body of the new tiddler
>
>- ##name## with Tony
>- ##icon## with {{<>||$:/core/images/info-button}}
>- etc...
>
> I imagine if a set of such changes could be triggered by a button and an 
> action widget all the better.
>
> I have other ways to achieve this but it would surprise me if the code was 
> not already available somewhere.
>
> Any leads would be appreciated
>
> Regards
> Tony
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8171d33a-54a0-483a-8f44-ebff137b0364%40googlegroups.com.


[tw5] Re: Creating tiddlers and programmatically modifying them?

2020-03-24 Thread Flibbles
Why doesn't it work?

I'm unsure whether you want $(name)$ to be replaced during creation, or if 
you want to copy `\define code-tiddler() $(name)$` exactly as is, but 
either way, you can include pragma inside the body macro.

\define body()
\define code-tiddler() $(value)$

Dear $(name)$,

I write to inform you that your pet, $(pet)$ has filed for emancipation.
\end


$(value)$ here will remain as-is unless `value` is defined. If it IS 
defined, it'll replace, so you can get either way you want it, I'd think.

On Tuesday, March 24, 2020 at 8:35:19 AM UTC-4, TonyM wrote:
>
> Fibbles,
>
> I have just realized this won't work in the tiddler I create needs to 
> contain a define
> \define code-tiddler() $(name)$
>
> There are many applications it will, but perhaps not this one.
>
> Regards
> Tony
>
>
> On Tuesday, March 24, 2020 at 1:19:05 PM UTC+11, Flibbles wrote:
>>
>> This would be outside the scope of Relink, but  there are ways to 
>> programmatically fill out a generated tiddler.
>>
>> \define body()
>> Dear $(name)$,
>>
>> I write to inform you that your pet, $(pet)$ has filed for emancipation.
>> \end
>>
>> \define createButton()
>> <$button tooltip="Create new letter" aria-label="new letter" class=<> config-toolbar-class>>>
>> <$action-sendmessage $message="tm-new-tiddler" title=<> text=<<
>> body>> />
>> <$list filter="[prefix[yes]]">
>> {{$:/core/images/new-button}}
>> 
>> <$list filter="[prefix[yes]]">
>> <$text text="new letter" />
>> 
>> 
>> \end
>>
>>
>> <$set name="title" value="New Letter">
>> <$set name="name" value="Wilson">
>> <$set name="pet" value="snuffles">
>> <>
>>
>> 
>>
>>
>> This will create a new tiddler. with a variable title, name, and pet.
>>
>> -Flibbles
>>
>> On Monday, March 23, 2020 at 9:20:52 PM UTC-4, TonyM wrote:
>>>
>>> Folks,
>>>
>>> I have a little project where it would be helpful if I could create a 
>>> tiddler from a template (for its body) but then replace various content 
>>> within the text or fields with different values.
>>>
>>> For example what if the template included ##name## then I had a macro 
>>> that would replace in the body of the new tiddler
>>>
>>>- ##name## with Tony
>>>- ##icon## with {{<>||$:/core/images/info-button}}
>>>- etc...
>>>
>>> I imagine if a set of such changes could be triggered by a button and an 
>>> action widget all the better.
>>>
>>> I have other ways to achieve this but it would surprise me if the code 
>>> was not already available somewhere.
>>>
>>> Any leads would be appreciated
>>>
>>> Regards
>>> Tony
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3fb99955-f59c-4aae-97d1-15c4c474dfe1%40googlegroups.com.


[tw5] Re: [Plugin] XML for Tiddlywiki!! Import, parse, render, and more!

2020-05-19 Thread Flibbles
Please let me know if there are any tool or abilities you feel this plugin 
is lacking for working with xml. I'd like this plugin to have all the basic 
tools someone would need.

For one, I'm thinking of adding an <> macro which will 
behave like XSLT's apply-templates, only tiddlywiki style.

-- 
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/446fc3c4-537e-420a-8117-b392dbb26631%40googlegroups.com.


[tw5] Re: Relink doesn't always work

2020-05-26 Thread Flibbles
I'm going through and addressing all discussions about Relink.

This is fixed now in latest versions.

I'm 80% sure you're the person who submitted the bug report.

-Flibbles

On Thursday, April 16, 2020 at 4:02:47 AM UTC-4, Peter Buyze wrote:
>
> I love this plug-in, and have had good experience thus far.
>
> Today I found a flwa/bug, I think.
>
> I have a tiddler entitled *ToC*.
> In the text box there is the following only:
>
> 
> <>
> 
>
> All tids that I want to occur in the list have a tag ToC. I wanted to 
> change the title of the ToC tid to *ToC-zettels*. Sure enough the Relink 
> message showed up telling me all links would be amended. But after making 
> the change and going to the Read mode, there was no more list of all the 
> tids tagged with ToC.
>
> In fact, what happened is that the ToC tag was removed from all the tids. 
> In other words, Relink cannot change tags. Is that right or am doing 
> something wrong?
>
>
> -- 
> Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
> https://tutanota.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/a43823ea-bfe8-45c6-a59b-1332ecf6f80f%40googlegroups.com.


[tw5] Re: freelinks and relink??

2020-05-26 Thread Flibbles
The way I'd do it is to create a child-plugin which users can optionally 
install. I just finished creating very nifty child-plugin support for 
Relink in order to optionally support Markdown, and I've been sifting 
through the discussions looking for places to use it. It's my new favorite 
toy about Relink.

If you had Freelink and Relink, you could choose whether or not to add the 
child-plugin.

-- 
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/0c3aaeaf-a842-48c5-a95b-2b9b3814cceb%40googlegroups.com.


[tw5] Re: Relink, and setting up button widgets for modals

2020-05-26 Thread Flibbles
I'm going back and addressing all discussions about Relink.

<$Button param /> is something Relink won't handle by default, because 
param could be anything, not just a title. However, if you only ever use it 
as a title, you can add <$button param> to the Relink whitelist as a title, 
and then Relink will handle it. If not, {{MyTiddler!!title}} works in most 
cases.

@CJ Veniot: I don't know what <$tidgraph/> is, but you can add <$tidgraph 
start> to your whitelist, and Relink will handle it for you without the 
transclusion trick.

-- 
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/12f2ff9b-fffc-4bf8-8925-9c46da34b2a4%40googlegroups.com.


[tw5] Re: freelinks and relink??

2020-05-26 Thread Flibbles
Sorry, I completely missed this. I don't normally sift through this group 
unless I want something.

This integration actually wouldn't be that hard. I might make it in a week 
or so. Currently, I'm really burned out after having added markdown support.

On Monday, April 20, 2020 at 5:49:31 AM UTC-4, HC Haase wrote:
>
> The freelink  plugin is realy 
> great and it has been a wish of mine for a long time. 
>
> However, if you use the great Relink 
>  plugin, and rely on all links to 
> be renamed if you edit the title of a tiddler, alas there is a shortcoming. 
> The freelink link is not a hard link and will not be edited by Relink. 
>
> I wonder if re-link could support the freelink "links" somehow??
>

-- 
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/994e92c1-a225-4b1a-8559-a452cada0676%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
@Saq Imtiaz: I think we just experienced a race condition with responding 
to Kleinfelter. Same answer asynchronously.

@Kleinfelter: As for the paragraph break, turns out that's actually how 
Remarkable rolls. It treats all the content in  as a block. BUT, I got 
good results by adding the following CSS to my project:

.tc-tiddler-body ul li p::first-child, .tc-tiddler-body ol li p::first-child 
{
  display: inline
}


You might want to make sure that solution is working in all cases though 
before moving forward with it.

-- 
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/2a2c046d-bda9-4712-bfc3-34290e4b6c25%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
Sorry. Make that this:

.tc-tiddler-preview li > :first-child, .tc-tiddler-body li > :first-child
{
  display: inline
}

If you do anything like

* list items
  With multiple lines
  Like this
* Or even
  * Multiple list

Just make sure it's producing what you expect.

-- 
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/5aa1b73d-04b5-4f97-bab6-c698a0f78975%40googlegroups.com.


[tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
I'm not able to replicate this problem. The only file trying to load 
tw5-markdown/highlight.js is tw5-markdown/wrapper.js. If you remove the 
plugin altogether, it should allow your server to boot.

(Just a quick note though. If migrating becomes too much of an issue, 
relink-markdown will work with anastosa. I just reached my own opinion that 
the core markdown plugin is better after peering under both their hoods.)

On Wednesday, May 27, 2020 at 10:46:51 AM UTC-4, Kevin Kleinfelter wrote:
>
> I'm trying to convert from using anstosa/tw5-markdown to the markdown 
> plugin in the TW plugin library.
>
> I'm running a node.js Tiddlywiki.  I have anstosa/tw5-markdown installed 
> "in the browser".  I went to TW Control Panel and pressed the Disable 
> button for $:/plugins/anstosa/tw5-markdown.  That disabled it, as expected.
>
> But when I restart node.js, my TW fails to start due to "Cannot find 
> module '$:/plugins/anstosa/tw5-markdown/highlight.js'".  In order to work 
> around it, I have to delete 
> $__config_Plugins_Disabled_$__plugins_anstosa_tw5-markdown.tid
>
> I need to disable (or delete) tw5-markdown without making my wiki 
> un-startable.  
>
> It looks like I'm going to need to manually tell it not to try and load 
> $:/plugins/anstosa/tw5-markdown/highlight.js.  That *is* a shadow tiddler 
> provided by the plugin.  It looks like disabling the plugin hides the 
> shadow tiddler, but something is still trying to load it.
>
> Any suggestions as to how I might find/disable that attempt to load 
> $:/plugins/anstosa/tw5-markdown/highlight.js? 
>

-- 
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/a4c00432-e54c-4d5f-b743-27b548760570%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
You can configure it to accept [[links like this]]. tiddlywiki/markdown 
disables a lot of wikipatterns, but you can reenable what you want. Just 
change $:/config/markdown/renderWikiTextPragma from

\rules only html image macrocallinline syslink transcludeinline wikilink 
filteredtranscludeblock macrocallblock transcludeblock 

to

\rules only html image macrocallinline syslink transcludeinline wikilink 
filteredtranscludeblock macrocallblock transcludeblock prettylink

As for the bullets lists. I know exactly why it's doing that. tiddlywiki 
markdown is enterpretting that list content as wikitext, but it's 
forgetting to consider it as inline only. Let me look into it a second.

You're on your own with the stylesheet though. I never even glanced at that 
while working.

On Wednesday, May 27, 2020 at 1:03:41 PM UTC-4, Kevin Kleinfelter wrote:
>
> Re: the quick note
>
> Thanks. I appreciate your work on relink-markdown.  I'm just trialing the 
> official Markdown based on you suggestion and I've run into a few issues 
> with anstona.  The issues I'm seeing with converting to the official 
> plugin  include:
>
>- Gotta change all my internal links from [[tiddler name]] to [tiddler 
>name](#tiddler%20name).  That's going to be an interesting project with 
>sed, and it will mess up a few items because sed won't really parse 
>Markdown.  I have ~1400 tiddlers, so a manual approach is infeasible. 
>Do-able.
>- List of bullets requires a blank line before it in order to be 
>recognized as a list, where anstosa didn't.  More work with grep and sed.  
>Do-able.
>- Much 'heavier weight' stylesheet.   Gonna have to brush up on CSS.  
>Do-able.
>- It makes a mess of bullet lists. Each bullet *should* be "text 
>here" but it is "text here".   This makes bullet 
> lists 
>take up too much space.  Could be a deal-killer.
>
>
> On Wed, May 27, 2020 at 12:09 PM Flibbles  > wrote:
>
>> I'm not able to replicate this problem. The only file trying to load 
>> tw5-markdown/highlight.js is tw5-markdown/wrapper.js. If you remove the 
>> plugin altogether, it should allow your server to boot.
>>
>> (Just a quick note though. If migrating becomes too much of an issue, 
>> relink-markdown will work with anastosa. I just reached my own opinion that 
>> the core markdown plugin is better after peering under both their hoods.)
>>
>> On Wednesday, May 27, 2020 at 10:46:51 AM UTC-4, Kevin Kleinfelter wrote:
>>>
>>> I'm trying to convert from using anstosa/tw5-markdown to the markdown 
>>> plugin in the TW plugin library.
>>>
>>> I'm running a node.js Tiddlywiki.  I have anstosa/tw5-markdown installed 
>>> "in the browser".  I went to TW Control Panel and pressed the Disable 
>>> button for $:/plugins/anstosa/tw5-markdown.  That disabled it, as expected.
>>>
>>> But when I restart node.js, my TW fails to start due to "Cannot find 
>>> module '$:/plugins/anstosa/tw5-markdown/highlight.js'".  In order to work 
>>> around it, I have to delete 
>>> $__config_Plugins_Disabled_$__plugins_anstosa_tw5-markdown.tid
>>>
>>> I need to disable (or delete) tw5-markdown without making my wiki 
>>> un-startable.  
>>>
>>> It looks like I'm going to need to manually tell it not to try and load 
>>> $:/plugins/anstosa/tw5-markdown/highlight.js.  That *is* a shadow tiddler 
>>> provided by the plugin.  It looks like disabling the plugin hides the 
>>> shadow tiddler, but something is still trying to load it.
>>>
>>> Any suggestions as to how I might find/disable that attempt to load 
>>> $:/plugins/anstosa/tw5-markdown/highlight.js? 
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/2I1U1tHWb9g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/a4c00432-e54c-4d5f-b743-27b548760570%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/a4c00432-e54c-4d5f-b743-27b548760570%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/eff11d60-8e5b-47e6-8c39-ac25f5d247fe%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
\rules is pretty poorly documented, but here's the best I can give you 
.
 
That's what documenation exists, the list of rules, and the relevant source.

I glanced at katex, and the wikirule's name is "latex-parser", so just add 
that to the end of the renderWikTextPragma string.

-- 
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/9c7f4f61-9170-4bef-8318-66abbcd8b8f3%40googlegroups.com.


[tw5] Re: Understanding "Installing custom plugins on Node.js"

2020-05-27 Thread Flibbles
For the second method, your project directory will have stuff laid out like 
this:

```
tiddlywiki.info
tiddlers/{all my tiddlers}
plugins/pluginName/plugin.info
plugins/pluginName/(other plugin stuff}
```

If you have your project set up like this, then your tiddlywiki server will 
have "pluginName" as a plugin. No need to edit the tiddlywiki.info file.

I hope this helps? If not, let me know.

-- 
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/32c55f2f-1344-4ebe-b741-9ab7cb736487%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
No problem. I was the one who convinced you to move to 
tiddlywiki/markdown.I might as well make sure it works for you.

-- 
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/29a16349-59a5-49cf-b61c-24183d5acf1c%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
That would do it. I'm glad it's working out for you now. :)

-- 
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/3846bf27-b39d-45f2-bc30-7cb5bb7771a8%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
Odd. It's working for me.

Are you certain you actually removed the .txt file extension? My operating 
system only pretended to when I first tried it just now. If you search for 
"wrapper" in your tiddlywiki, and you get a tiddler with a title that has a 
filepath relative to your operating system, then it's still txt.

-- 
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/4a719c65-7660-4b18-bcd6-0917c851ce3c%40googlegroups.com.


Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
Also, I've put more effort into it and have created the version of wrapper 
which is better tested, and supports hardbreak (putting spaces at the end 
of lines to force a linebreak). This is the one I'll be submitting in my PR.

-- 
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/770bae46-5e84-4c13-94a3-378e26e1366f%40googlegroups.com.
module-type: parser
title: $:/plugins/tiddlywiki/markdown/wrapper.js
type: application/javascript

/*\
title: $:/plugins/tiddlywiki/markdown/wrapper.js
type: application/javascript
module-type: parser

Wraps up the remarkable parser for use as a Parser in TiddlyWiki

\*/
(function(){

/*jslint node: true, browser: true */
/*global $tw: false */
"use strict";

var r = require("$:/plugins/tiddlywiki/markdown/remarkable.js");

var Remarkable = r.Remarkable,
linkify = r.linkify,
utils = r.utils;

/ Set up configuration options /
function parseAsBoolean(tiddlerName) {
return $tw.wiki.getTiddlerText(tiddlerName).toLowerCase() === "true";
}
var pluginOpts = {
linkNewWindow: parseAsBoolean("$:/config/markdown/linkNewWindow"),
renderWikiText: parseAsBoolean("$:/config/markdown/renderWikiText"),
renderWikiTextPragma: 
$tw.wiki.getTiddlerText("$:/config/markdown/renderWikiTextPragma").trim()
};
var remarkableOpts = {
breaks: parseAsBoolean("$:/config/markdown/breaks"),
quotes: $tw.wiki.getTiddlerText("$:/config/markdown/quotes"),
typographer: parseAsBoolean("$:/config/markdown/typographer")
};

var md = new Remarkable(remarkableOpts);

if (parseAsBoolean("$:/config/markdown/linkify")) {
md = md.use(linkify);
}

function findTagWithType(nodes, startPoint, type, level) {
for (var i = startPoint; i < nodes.length; i++) {
if (nodes[i].type === type && nodes[i].level === level) {
return i;
}
}
return false;
}

/**
 * Remarkable creates nodes that look like:
 * [
 *   { type: 'paragraph_open'},
 *   { type: 'inline', content: 'Hello World', children:[{type: 'text', 
content: 'Hello World'}]},
 *   { type: 'paragraph_close'}
 * ]
 *
 * But TiddlyWiki wants the Parser 
(https://tiddlywiki.com/dev/static/Parser.html) to emit nodes like:
 *
 * [
 *   { type: 'element', tag: 'p', children: [{type: 'text', text: 'Hello 
World'}]}
 * ]
 */
function convertNodes(remarkableTree, isStartOfInline) {
let out = [];
var accumulatedText = '';
function wrappedElement(elementTag, currentIndex, currentLevel, 
closingType, nodes) {
var j = findTagWithType(nodes, currentIndex + 1, closingType, 
currentLevel);
if (j === false) {
console.error("Failed to find a " + closingType + " 
node after position " + currentIndex);
console.log(nodes);
return currentIndex + 1;
}
let children = convertNodes(nodes.slice(currentIndex + 1, j));

out.push({
type: "element",
tag: elementTag,
children: children
});
return j;
}

for (var i = 0; i < remarkableTree.length; i++) {
var currentNode = remarkableTree[i];
if (currentNode.type === "paragraph_open") {
i = wrappedElement("p", i, currentNode.level, 
"paragraph_close", remarkableTree);
} else if (currentNode.type === "heading_open") {
i = wrappedElement("h" + currentNode.hLevel, i, 
currentNode.level, "heading_close", remarkableTree);
} else if (currentNode.type === "bullet_list_open") {
i = wrappedElement("ul", i, currentNode.level, 
"bullet_list_close", remarkableTree);
} else if (currentNode.type == 'ordered_list_open') {
i = wrappedElement('ol', i, 
currentNode.level,'ordered_list_close', remarkableTree);
} else if (currentNode.type === "list_item_open") {
i = wrappedElement("li", i, currentNode.level, 
"list_item_close", remarkableTree);
} else if (currentNode.type === "link_open") {
var j = findTagWithType(remarkableTree, i + 1, 
"link_close", currentNode.level);

if (currentNode.href[0] !== "#") {
// External link
var attributes = {
href: { type: "string", value: 
currentNode.href }
};
if (pluginOpts.linkNewWindow) {
   

Re: [tw5] Re: Plugin Hotel California - Can't Disable Plugin

2020-05-27 Thread Flibbles
This is because there's a bug in tiddlywiki/markdown where it's not 
properly respecting the *$:/config/markdown/breaks* tiddler. I'll submit a 
PR later today, but it'll probably take a while before it gets into master. 
Jermolene is still recovering.

In the meantime, attached is a shadow-override you can drop in that has my 
"5 minutes of testing" guarantee.

(Google Groups won't let me upload anything but a text file, so you need to 
remove the ".txt" from the end before putting it into your project.)

-- 
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/c2a4b9eb-742f-4e4c-b165-4e44162237d6%40googlegroups.com.
module-type: parser
title: $:/plugins/tiddlywiki/markdown/wrapper.js
type: application/javascript

/*\
title: $:/plugins/tiddlywiki/markdown/wrapper.js
type: application/javascript
module-type: parser

Wraps up the remarkable parser for use as a Parser in TiddlyWiki

\*/
(function(){

/*jslint node: true, browser: true */
/*global $tw: false */
"use strict";

var r = require("$:/plugins/tiddlywiki/markdown/remarkable.js");

var Remarkable = r.Remarkable,
linkify = r.linkify,
utils = r.utils;

/ Set up configuration options /
function parseAsBoolean(tiddlerName) {
return $tw.wiki.getTiddlerText(tiddlerName).toLowerCase() === "true";
}
var pluginOpts = {
linkNewWindow: parseAsBoolean("$:/config/markdown/linkNewWindow"),
renderWikiText: parseAsBoolean("$:/config/markdown/renderWikiText"),
renderWikiTextPragma: 
$tw.wiki.getTiddlerText("$:/config/markdown/renderWikiTextPragma").trim()
};
var remarkableOpts = {
breaks: parseAsBoolean("$:/config/markdown/breaks"),
quotes: $tw.wiki.getTiddlerText("$:/config/markdown/quotes"),
typographer: parseAsBoolean("$:/config/markdown/typographer")
};

var md = new Remarkable(remarkableOpts);

if (parseAsBoolean("$:/config/markdown/linkify")) {
md = md.use(linkify);
}

function findTagWithType(nodes, startPoint, type, level) {
for (var i = startPoint; i < nodes.length; i++) {
if (nodes[i].type === type && nodes[i].level === level) {
return i;
}
}
return false;
}

/**
 * Remarkable creates nodes that look like:
 * [
 *   { type: 'paragraph_open'},
 *   { type: 'inline', content: 'Hello World', children:[{type: 'text', 
content: 'Hello World'}]},
 *   { type: 'paragraph_close'}
 * ]
 *
 * But TiddlyWiki wants the Parser 
(https://tiddlywiki.com/dev/static/Parser.html) to emit nodes like:
 *
 * [
 *   { type: 'element', tag: 'p', children: [{type: 'text', text: 'Hello 
World'}]}
 * ]
 */
function convertNodes(remarkableTree, isStartOfInline) {
let out = [];
var accumulatedText = '';
function wrappedElement(elementTag, currentIndex, currentLevel, 
closingType, nodes) {
var j = findTagWithType(nodes, currentIndex + 1, closingType, 
currentLevel);
if (j === false) {
console.error("Failed to find a " + closingType + " 
node after position " + currentIndex);
console.log(nodes);
return currentIndex + 1;
}
let children = convertNodes(nodes.slice(currentIndex + 1, j));

out.push({
type: "element",
tag: elementTag,
children: children
});
return j;
}

for (var i = 0; i < remarkableTree.length; i++) {
var currentNode = remarkableTree[i];
if (currentNode.type === "paragraph_open") {
i = wrappedElement("p", i, currentNode.level, 
"paragraph_close", remarkableTree);
} else if (currentNode.type === "heading_open") {
i = wrappedElement("h" + currentNode.hLevel, i, 
currentNode.level, "heading_close", remarkableTree);
} else if (currentNode.type === "bullet_list_open") {
i = wrappedElement("ul", i, currentNode.level, 
"bullet_list_close", remarkableTree);
} else if (currentNode.type == 'ordered_list_open') {
i = wrappedElement('ol', i, 
currentNode.level,'ordered_list_close', remarkableTree);
} else if (currentNode.type === "list_item_open") {
i = wrappedElement("li", i, currentNode.level, 
"list_item_close", remarkableTree);
} else if (currentNode.type === "link_open") {
var j = findTagWithType(remarkableTree, i + 1, 
"link_close", currentNode.level);

if (currentNode.href[0] !== "#") {
  

[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-05-25 Thread Flibbles
*Now with Markdown support!*

...in the form of a supplemental plugin.

But I integrated Relink v1.10 with Tiddlywiki's PluginLibrary wizard, so 
now when you go to "Get More Plugins", Relink has it's own tab where you 
can easily see all Relink sub-plugins (installed or not installed), what 
needs updating, and then update with a single click. It's super slick, 
guys. For real!

But probably not worth all the work it took.

-Flibbles

-- 
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/ee2c96e6-203a-497c-b307-0b65bed7ffea%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
[enlist{!!list}] does work.

...also

[list[]]

Surprised nobody mentioned that.

For your linking to a file, make sure you can open 
"file:///d:\моясукапапка\" directly in your browser, such as by dragging 
that file onto a new tab. The link supplied from that is the href you 
should be using for the link. But If you're still having trouble, maybe you 
have to encode the uri.

Link

Though honestly, I'm not sure that's the answer. If you can open it 
directly in the browser, you should be able to open it in Tiddlywiki just 
fine.

-- 
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/6eff6136-21a3-4e1b-b783-1fec636b8e06%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
[list[]] works replacing [enlist{!!list}] in everyone else's examples. So 
the easiest way to print the list of the current tiddler is:

{{{ [list[]] }}}

As for your unicode directory name, I don't know what to tell you. I can't 
replicate the issue. Every single combination of escaped, unescaped, 
encoded, and decoded that I use on my windows machine all work using the 
directory name you passed me. The only time I could get it *not* to work 
was when I was trying to follow a link made in a tiddler that wasn't local 
to my own machine.

-- 
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/f84c3091-9245-495d-ab6b-6efb19aa94b5%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
Like link: ...??? I don't get what you're asking for. If you have 
your macro separated the way you say you do, then it should already be 
wrapped in  elements. Maybe if you show me what you have?

-- 
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/506cd123-c4ca-49f9-9095-7027c593ebe2%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
Like... this...?

\define mylinks()
links: <$list filter="[list[]]"><$link/>, 
\end

This is my content

<>

Just including a space between the macro and your body would start a new 
paragraph. Or are you saying you want that macro to automatically render at 
the bottom of every tiddler or something?

-- 
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/13bc959e-5f32-402c-a975-9c234bd611d6%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
Oh. So this:

\define mylinks()

links:<$list filter="[list[]]"><$link/>, 
\end

This is my content
<>

-- 
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/14507485-98b2-4211-b569-8ae393d25417%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
O... okay. But it already should have been...
I guess I'm glad you've got something working for you though. Good luck!

-- 
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/ca93a7ac-e920-4d7c-8e72-d1df227c67fa%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles


[image: newline needed.png]

-- 
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/676fbbaa-1014-4730-ac09-7ecd2702623f%40googlegroups.com.


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
Or this?

\define mylinks()

links:<$list filter="[list[]]"><$link/>, 
\end

On Thursday, May 28, 2020 at 4:08:06 PM UTC-4, Flibbles wrote:
>
> Oh. So this?:
>
> links:<$list filter="[list[]]"><$link/>, 
>

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


[tw5] Re: Show items added in the list field of the current tiddler

2020-05-28 Thread Flibbles
Not quite sure what you mean. You want the last item in the list to be 
displayed separately? So...

\define mylinks()
links: <$list filter="[list[]butlast[]]"><$link/>, 

<$list filter="[list[]last[]]">and <$link/>
\end


What kind of output are you trying to get?

-- 
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/b246aa0e-5406-48f7-91f1-bbe2afb14b16%40googlegroups.com.


[tw5] Re: Rename tiddlers to datetime IDs (unique identifier)

2020-12-15 Thread Flibbles
I don't normally hang around in the Google group, so I didn't see this 
until now. I read what you wrote several times but I'm still not clear on 
what Relink is doing wrong, or what it's supposed to be doing but isn't.

You don't still need help, do you? 

-Flibbles
On Thursday, October 22, 2020 at 3:46:47 AM UTC-4 bimlas wrote:

> You can also create IDs based on a counter, so you can be sure to avoid 
> name conflicts, and each tiddler will be given a unique ID (even one that 
> does not have a created field). In this case, also modify the body of the 
> generateID function and the filterAlreadyRenamed filter.
>
> var filterAlreadyRenamed = "!regexp[^ZK\\d{8}$]";
>
> // ...
>
> var lastId = 
> (parseInt($tw.wiki.filterTiddlers("[regexp[^ZK\\d{8}$]nsort[]last[]removeprefix[ZK]]")[0])
>  
> + 1) || 1;
> function generateId(fields) {
>   var idLength = 8;
>   var idPrefix = "ZK";
>   var id = lastId.toString();
>   lastId += 1;
>   while (id.length < idLength) id = "0" + id;
>   return idPrefix + id;
> }
>

-- 
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/7ef4fcaa-baa7-4d02-983c-9f0634e88e4dn%40googlegroups.com.


[tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-12-15 Thread Flibbles
For those who may be interested, many people requested that Relink be able 
to handle renaming titles of nested directory tiddlers associated with a 
renamed tiddler.

Here it is. Relink-titles, the supplemental plugin 
<https://flibbles.github.io/tw5-relink/#Plugins%2FTitles>.

It also allows for custom rename rules based on filters, as well as rules 
introduced by 3rd party plugins.

Currently, the only built in rule is the directory tree one. I couldn't 
think of any others that people would generally want. If you know of any, 
let me know.

-Flibbles
On Monday, May 25, 2020 at 11:06:03 PM UTC-4 joshua@gmail.com wrote:

> Actually, that's really cool. I have that on my ToDo list, but have put it 
> off while I tinker with UI stuff.
>
> Best,
> Joshua F
>
>
> On Monday, May 25, 2020 at 6:54:16 PM UTC-7, Flibbles wrote:
>>
>> *Now with Markdown support!*
>>
>> ...in the form of a supplemental plugin.
>>
>> But I integrated Relink v1.10 with Tiddlywiki's PluginLibrary wizard, so 
>> now when you go to "Get More Plugins", Relink has it's own tab where you 
>> can easily see all Relink sub-plugins (installed or not installed), what 
>> needs updating, and then update with a single click. It's super slick, 
>> guys. For real!
>>
>> But probably not worth all the work it took.
>>
>> -Flibbles
>>
>

-- 
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/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com.


[tw5] Re: Query: Plugin Libraries? Who has them?

2020-12-15 Thread Flibbles


On Friday, July 31, 2020 at 3:24:13 PM UTC-4 TiddlyTweeter wrote:

> Ciao PMario
>
> Fibbles plugin Library has dependencies as it invokes language tiddlers 
> you need RELINK for already to show. If you try invoke it without that 
> you'll get blanks.
> Knowing that you can install the plugin library without Relink installed 
> IF you also install the two invoked language tiddlers too.
>

I see that I do use language tiddlers in my pluginLibrary tiddler. If that 
is preventing Relink from being included in other plugin libraries somehow, 
then I'm absolutely prepared to inline those strings and captions. The 
entire point of creating my relink plugin library was to increase exposure.

Would removing those language invocations benefit the community?

-- 
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/72d955da-058b-4d5b-8388-63efe52ad0c8n%40googlegroups.com.


[tw5] Re: Use Relink to rename similar tiddlers

2020-12-15 Thread Flibbles
I am here to say that Relink can now handle this very case.

Introducing Relink-Titles 


It's a supplemental Relink plugin that allows for title updating of any 
directory-nested tiddlers. And also any custom filter rules, or rules 
introduced by third-party plugins.

I'm only 4 months late!
On Wednesday, August 19, 2020 at 3:01:44 AM UTC-4 Mat wrote:

> If you only want the occasional correction, the way to do it is to open 
> your wiki in an editor e.g Notepad++ and do a search/replace. Obviously the 
> usual caveats; careful, backup.
>
> <:-)
>

-- 
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/9813b62f-e4bb-418d-ba11-6f545914b083n%40googlegroups.com.


[tw5] Re: Noteself - Tiddlers disappearing on other devices. What am I missing?

2020-12-15 Thread Flibbles
I know I'm late to the party here, but are you using lazy tiddler loading? 
It has a few issues that can cause tiddler bodies be deleted.
On Thursday, July 2, 2020 at 9:49:11 AM UTC-4 Sean Carter wrote:

> I'm using Tiddlywiki with Noteself for automatic saving in addition to a 
> few other plugins. When I save the wiki's HTML file to a USB and use it to 
> open the HTML on a different device, some of the tiddlers act strangely. 
> When opening these tiddlers, a pop-up window appears with the title:
>
> syncer-browser- 18:37:48 1 7 2020
>
> and with text that says
>
> Sync error while processing 
> 'foo':{"status":404,"name":"not_found","message":"missing","reason":"missing"}
>
> All the tiddler's body text is gone, but its title and tags are still 
> there. This also happens when I save the HTML file to Dropbox and try to 
> download and open it on the other device.
>
> The pop-up only appears when trying to open the affected tiddler for the 
> first time on the new device. One every subsequent time, the tiddler just 
> opens with no body text.
>
> I believe the problem is caused by Noteself because the pop-up window 
> mentions syncing, but I'm not certain. Here is a list of the plugins I'm 
> using:
>
>- 
>
>Context search - provides visual highlight of search results
>- 
>
>Editor with some on-line completion capabilities
>- 
>
>Fullscreen Editor
>- 
>
>Highlight.js syntax highlighting
>- 
>
>Plugin containing specific configurations for the online version of 
>NoteSelf
>- 
>
>Relink - flexibility when relinking renamed tiddlers
>- 
>
>Stories - Add a second column to a TiddlyWiki layout using the default 
>layout
>- 
>
>The Pounchdb library as a TW5 plugin.
>- 
>
>tiddlypounch for TiddlyWiki
>
> I tried disabling the plugins one by one, but doing this doesn't seem to 
> actually change anything about the wiki.
>
> I've also encrypted the wiki with TiddlyWiki's built-in encryption.
>
> I use Tiddlywiki version 5.1.22
>
> This happened while attempting to transfer my wiki from a desktop running 
> Windows 10 to a laptop running Windows 7. I am using Chrome.
>
> Why is this happening, and what is the solution? Any help would be greatly 
> appreciated.
>

-- 
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/c62048c4-fa79-4e08-9f07-0255c10b1060n%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-12-15 Thread Flibbles
Really? I would have thought Tiddler Commander could handle that just fine.

If somebody wanted to rename a non-existent tag using Relink, I'd tell them 
to make the tag, rename it, and then delete it.

On Tuesday, December 15, 2020 at 11:36:22 PM UTC-5 Mohammad wrote:

> Hi Flibless,
>
> This is a great move specially for those who work with Node.js version of 
> Tiddlywiki.
> Thank you for sharing.  
>
> One question: there is an edge case for when tiddlers are not physically 
> existed but you like to rename them!
> Example is tags, you may have several tags for example asian/country, 
> asian/city, asian/culture and you gonna to
> change the asian to european! How can relink be used in this case? This 
> question was originally asked by Mark S on Tiddler Commander.
> Tiddler commander in current form cannot work on non-existing tiddler as 
> it is a confusing concept.
>
>
> Best wishes
> Mohammad
>
>
> On Wed, Dec 16, 2020 at 4:24 AM Flibbles  wrote:
>
>> For those who may be interested, many people requested that Relink be 
>> able to handle renaming titles of nested directory tiddlers associated with 
>> a renamed tiddler.
>>
>> Here it is. Relink-titles, the supplemental plugin 
>> <https://flibbles.github.io/tw5-relink/#Plugins%2FTitles>.
>>
>> It also allows for custom rename rules based on filters, as well as rules 
>> introduced by 3rd party plugins.
>>
>> Currently, the only built in rule is the directory tree one. I couldn't 
>> think of any others that people would generally want. If you know of any, 
>> let me know.
>>
>> -Flibbles
>> On Monday, May 25, 2020 at 11:06:03 PM UTC-4 joshua@gmail.com wrote:
>>
>>> Actually, that's really cool. I have that on my ToDo list, but have put 
>>> it off while I tinker with UI stuff.
>>>
>>> Best,
>>> Joshua F
>>>
>>>
>>> On Monday, May 25, 2020 at 6:54:16 PM UTC-7, Flibbles wrote:
>>>>
>>>> *Now with Markdown support!*
>>>>
>>>> ...in the form of a supplemental plugin.
>>>>
>>>> But I integrated Relink v1.10 with Tiddlywiki's PluginLibrary wizard, 
>>>> so now when you go to "Get More Plugins", Relink has it's own tab where 
>>>> you 
>>>> can easily see all Relink sub-plugins (installed or not installed), what 
>>>> needs updating, and then update with a single click. It's super slick, 
>>>> guys. For real!
>>>>
>>>> But probably not worth all the work it took.
>>>>
>>>> -Flibbles
>>>>
>>> -- 
>>
> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/1467fcd4-dad8-4f0e-bf23-cfdfb1395005n%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2020-12-16 Thread Flibbles
Yes. The parent-plugin field is present on both of Relink's supplemental 
plugins.

On Thursday, December 17, 2020 at 12:45:13 AM UTC-5 Mohammad wrote:

> Flibbles,
>  Have you tried the parent-plugin field  to distribute subplugin of relink 
> as its children?
> Take a look in  https://tiddlywiki.com/prerelease/#PluginMechanism 
> presented in 5.1.23
>
>
> Best wishes
> Mohammad
>
>
> On Wed, Dec 16, 2020 at 4:24 AM Flibbles  wrote:
>
>> For those who may be interested, many people requested that Relink be 
>> able to handle renaming titles of nested directory tiddlers associated with 
>> a renamed tiddler.
>>
>> Here it is. Relink-titles, the supplemental plugin 
>> <https://flibbles.github.io/tw5-relink/#Plugins%2FTitles>.
>>
>> It also allows for custom rename rules based on filters, as well as rules 
>> introduced by 3rd party plugins.
>>
>> Currently, the only built in rule is the directory tree one. I couldn't 
>> think of any others that people would generally want. If you know of any, 
>> let me know.
>>
>> -Flibbles
>> On Monday, May 25, 2020 at 11:06:03 PM UTC-4 joshua@gmail.com wrote:
>>
>>> Actually, that's really cool. I have that on my ToDo list, but have put 
>>> it off while I tinker with UI stuff.
>>>
>>> Best,
>>> Joshua F
>>>
>>>
>>> On Monday, May 25, 2020 at 6:54:16 PM UTC-7, Flibbles wrote:
>>>>
>>>> *Now with Markdown support!*
>>>>
>>>> ...in the form of a supplemental plugin.
>>>>
>>>> But I integrated Relink v1.10 with Tiddlywiki's PluginLibrary wizard, 
>>>> so now when you go to "Get More Plugins", Relink has it's own tab where 
>>>> you 
>>>> can easily see all Relink sub-plugins (installed or not installed), what 
>>>> needs updating, and then update with a single click. It's super slick, 
>>>> guys. For real!
>>>>
>>>> But probably not worth all the work it took.
>>>>
>>>> -Flibbles
>>>>
>>> -- 
>>
> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/3616ec0a-9000-464e-a4c2-1643c0c9925cn%40googlegroups.com.


Re: [tw5] [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

2021-01-20 Thread Flibbles
Hey @TiddlyTweeter

I checked out innerwiki.js. It's less about it being recursive, and more 
about innerwiki using async functions which are >=ECMA 6 features, and 
aren't supported by UglifyJS. No worries. It just means that single file 
wasn't compressed.

The freezing on modification is one issue I'm not sure what to do with. 
Apparently TW5 *completely rerenders itself* after every change, and 
without modifying the core, I don't think there's a way for Uglify to 
recognize the difference between a rendering from a change, and rendering 
because TW is saving to disk. Fortunately this problem only happens once 
per browser session, since results are cached, and it doesn't occur with 
NodeJS implementations.

Otherwise, glad you like it!

-Flibbles

On Wednesday, January 20, 2021 at 8:48:28 AM UTC-5 TiddlyTweeter wrote:

> *Side thoughts on text/wikitext uglification :-)*
>
> Flibbles wrote:
>
>> I'd love to have wikitext compression too; there are some things I can 
>> do. But it's super tricky. 
>>
>  
> Right. 
>
> Maybe that would a *later thought* for *other situations* than we 
> normally face? 
> I'm thinking particularly of *e-pubs *where you can have huge texts (e.g. 
> novels) with vast excess space use. But I have NO idea how you could get a 
> minify of that working in a TW. 
>
> 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/b6208e38-1995-441b-a659-96313aaf468cn%40googlegroups.com.


[tw5] Re: [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

2021-01-20 Thread Flibbles
I don't think so. I'm not sure what that is, and I can't find it in the 
core. Uglify works by hijacking the View Widget, which is used for all 
plugin writing during saves. It's not great, but it's what I found works. 
If there's a better way, I'd gladly change it over.

On Wednesday, January 20, 2021 at 2:54:50 PM UTC-5 PMario wrote:

> Hi, 
>
> Very interesting. .. Did you try to use the source.map function?
>
> -mario
>

-- 
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/42bf36ee-fb02-408f-b459-a4d9346500acn%40googlegroups.com.


[tw5] Re: Are there any hacks for getting backlinks for soft links?

2021-01-15 Thread Flibbles
If you're just trying to get a list of backlinks to look at, I might 
recommend the Relink plugin. It adds a special References tab to the 
TiddlyInfo panel. Once rememberq is properly configured, which would be 
something like `\relink rememberq question:wikitext answer:wikitext` or 
something like that (depends on the macro argument names), Relink will pick 
them up just fine.

If you're looking for a filter operator like backlinks, then that would be 
trickier...

On Friday, January 15, 2021 at 7:06:07 AM UTC-5 si wrote:

> TiddlyRemember uses macros like this:
>
> < "Who went with [[Frodo]] to [[Mordor]]?"
> "[[Sam]]">>
>
> Which renders like this:
> [image: mordor.png]
> As far as I know, filters like  [[Mordor]backlinks[]] will not return the 
> above example, because the links are contained within the macro syntax.
>
> For cases where the macro is rendered on the tiddler that contains it, you 
> can use the following hack:
>
> <$vars lb="[[" rb="]]">
> <$vars search_term={{{ [addsuffix[Mordor]addsuffix] }}}>
> <]">>
> 
> 
>
> But what about when it's transcluded elsewhere? Are there any hacks out 
> there to get the same effect?
>

-- 
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/b251cbd3-7deb-457e-9b74-131cb55a5f05n%40googlegroups.com.


[tw5] [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

2021-01-19 Thread Flibbles
Some people want a minified version of the TW5 core, but it'd be too much 
work to maintain.
Some people think it should remain uncompressed for the sake of editors, 
but TW5 continues to grow by the day.
Some developers compress their plugins, making efficient code, but it's a 
pain for anyone debugging it.
Some developers leave their plugins uncompressed, but that means it's 
larger than necessary for 90% of all end-users.

Now there's a solution for everybody: TW5-uglify.

This is a plugin primarily designed to be used by a Node.JS server. Your 
server has access to all your uncompressed and unpacked plugins, which is 
fine, since servers have the speed and memory for it. But what it sends to 
browsers are fully compressed plugins. Your little smart phones and tablets 
get the efficient TW5 they deserve.

Or maybe you're a plugin developer who wants to minify their code. Now you 
no longer have to resort to using npm-gulp like some kind of chump. Your 
build process can remain an entirely TiddlyWiki process.

Or maybe you want to miniify your standalone TiddlyWiki file. You can, 
but... think hard about this before you do it. Because unlike with 
TW5-Uglified server, compressing your standalone files is a one-way 
process. You'll forever have compressed code unless you download a new 
Tiddlywiki, redownload all your plugins, and transfer all your tiddlers 
from your old file. But hey! Maybe you're running TiddlyWiki on your 2000 
era Nokia phone in an wifi wasteland. Then go ahead.

Check it out.
Here's the demo site. <https://flibbles.github.io/tw5-uglify/>
And here's the github page <https://github.com/flibbles/tw5-uglify>.

Let me know what you all think.

-- 
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/2ce6fad2-8600-4c73-940c-515548e49c1en%40googlegroups.com.


Re: [tw5] [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

2021-01-19 Thread Flibbles
Hey Mohammad,

Currently, the bulk of the compression occurs in the javascript, but it 
does optimize all plugins somewhat by improving the way they're packed. 
Commander will come down a bit in size.

I'd love to have wikitext compression too; there are some things I can do. 
But it's super tricky. Unlike javascript, wikitext is dependent on white 
space. Definitely not sure if I could reduce them by over 60% like you're 
suggesting though, unless you're thinking of stream compression, but that'd 
be outside the scope of this plugin.

-Flibbles

On Tuesday, January 19, 2021 at 10:37:19 PM UTC-5 Mohammad wrote:

> Hi Flibbles
>
> This is amazing! I am one of those who request for a minified TW5 and you 
> did it!
>
> The empty.html for TW5.1.24 is 2371 kB and the Uglified TW 5.1.24 is 1297 
> kB  EXCELLENT!! around 50% smaller!
> We have a big pain distributing a TW with required plugins (empty.html ~ 
> 4500 kB)
> Love it, I will test it with much of interest.
>
> One question: The doc says it compresses the JS code, how about plugins 
> developed in pure wikitext? Commander is around 112kB, but I think it 
> should be 25-40kB.
> What do you think?
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Jan 19, 2021 at 11:56 PM Flibbles  wrote:
>
>> Some people want a minified version of the TW5 core, but it'd be too much 
>> work to maintain.
>> Some people think it should remain uncompressed for the sake of editors, 
>> but TW5 continues to grow by the day.
>> Some developers compress their plugins, making efficient code, but it's a 
>> pain for anyone debugging it.
>> Some developers leave their plugins uncompressed, but that means it's 
>> larger than necessary for 90% of all end-users.
>>
>> Now there's a solution for everybody: TW5-uglify.
>>
>> This is a plugin primarily designed to be used by a Node.JS server. Your 
>> server has access to all your uncompressed and unpacked plugins, which is 
>> fine, since servers have the speed and memory for it. But what it sends to 
>> browsers are fully compressed plugins. Your little smart phones and tablets 
>> get the efficient TW5 they deserve.
>>
>> Or maybe you're a plugin developer who wants to minify their code. Now 
>> you no longer have to resort to using npm-gulp like some kind of chump. 
>> Your build process can remain an entirely TiddlyWiki process.
>>
>> Or maybe you want to miniify your standalone TiddlyWiki file. You can, 
>> but... think hard about this before you do it. Because unlike with 
>> TW5-Uglified server, compressing your standalone files is a one-way 
>> process. You'll forever have compressed code unless you download a new 
>> Tiddlywiki, redownload all your plugins, and transfer all your tiddlers 
>> from your old file. But hey! Maybe you're running TiddlyWiki on your 2000 
>> era Nokia phone in an wifi wasteland. Then go ahead.
>>
>> Check it out.
>> Here's the demo site. <https://flibbles.github.io/tw5-uglify/>
>> And here's the github page <https://github.com/flibbles/tw5-uglify>.
>>
>> Let me know what you all think.
>>
>> -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/2ce6fad2-8600-4c73-940c-515548e49c1en%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/2ce6fad2-8600-4c73-940c-515548e49c1en%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/e3868d68-0328-4fe3-88c8-067116fcbeean%40googlegroups.com.


Re: [tw5] [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

2021-06-20 Thread Flibbles
I'm not sure how you're "servering versions" or even what that means, but I 
assume it's about generating standalone tiddlywiki files from a NodeJS 
tiddlywiki. If that's the case, then a publish-filter already exists. It's 
part of the "rendertiddler" command. You can see the uglify tiddlywiki.info 
file for an example of how to generate a tiddlywiki file without certain 
plugins or files. In Uglify's case, it creates one without the jasmine 
plugin, or any tiddlers with the "Test/' prefix.

-Flibbles

On Saturday, June 19, 2021 at 6:21:39 AM UTC-4 Jan wrote:

> Hi Flibbles, 
> I think a publish filter is a good idea, I wanted to do that for years 
> with Mat's publish-plugin but lost it out of sight. What is the best tool 
> to do this right now?
> It would be interesting to combine this with your plugin to have the 
> maximum reduction.
>
> Best wishes Jan
>
> Am Sa., 19. Juni 2021 um 01:21 Uhr schrieb Flibbles <
> challenge...@gmail.com>:
>
>> Hey Jan,
>>
>> I'm glad Uglify works well for you. To answer your questions
>>
>>
>>1. Removing overridden core Tiddlers could reduce the code size 
>>somewhat, but I'm not sure how often that use case would come up. Even in 
>>my beastly TiddlyWiki projects, my overridden tiddlers don't make up very 
>>much space, particularly since I (and most people I'd think) only 
>> override 
>>smallish tiddlers. If it's something larger, a monkey-patch injection is 
>>used more often. Meanwhile, removing those overridden shadows could lead 
>> to 
>>a whole slew of nasty bugs if someone A) Removed the override down the 
>>line, or B) Tried to export their project into any form other than 
>> exactly 
>>what it is.
>>2. Temporarily removing deactivated plugins seems out of scope for a 
>>content compression plugin (But just by a little. It compresses plugins. 
>>Removing them is a different job), and it's probably best done by the 
>> user. 
>>If they are serving versions of a tiddler where they want certain plugins 
>>excluded, they'd could use the publishFilter. A slightly elaborate 
>>tiddly-filter could exclude all deactivated plugins.
>>
>>
>> Hope this helps!
>> -Flibbles
>>
>> On Friday, June 18, 2021 at 6:45:03 PM UTC-4 Jan wrote:
>>
>>> Hi Flibbles,
>>> great idea! My wikis tended to grow recently this seems to be a great 
>>> remedy.
>>> Some Questions: Could it also remove 
>>> - overridden core Tiddlers
>>> - temporarily deactivated plugins and inactive themes 
>>> from the version which is served?
>>>
>>> Best wishes Jan
>>>
>>> Am Di., 19. Jan. 2021 um 21:26 Uhr schrieb Flibbles <
>>> challenge...@gmail.com>:
>>>
>>>> Some people want a minified version of the TW5 core, but it'd be too 
>>>> much work to maintain.
>>>> Some people think it should remain uncompressed for the sake of 
>>>> editors, but TW5 continues to grow by the day.
>>>> Some developers compress their plugins, making efficient code, but it's 
>>>> a pain for anyone debugging it.
>>>> Some developers leave their plugins uncompressed, but that means it's 
>>>> larger than necessary for 90% of all end-users.
>>>>
>>>> Now there's a solution for everybody: TW5-uglify.
>>>>
>>>> This is a plugin primarily designed to be used by a Node.JS server. 
>>>> Your server has access to all your uncompressed and unpacked plugins, 
>>>> which 
>>>> is fine, since servers have the speed and memory for it. But what it sends 
>>>> to browsers are fully compressed plugins. Your little smart phones and 
>>>> tablets get the efficient TW5 they deserve.
>>>>
>>>> Or maybe you're a plugin developer who wants to minify their code. Now 
>>>> you no longer have to resort to using npm-gulp like some kind of chump. 
>>>> Your build process can remain an entirely TiddlyWiki process.
>>>>
>>>> Or maybe you want to miniify your standalone TiddlyWiki file. You can, 
>>>> but... think hard about this before you do it. Because unlike with 
>>>> TW5-Uglified server, compressing your standalone files is a one-way 
>>>> process. You'll forever have compressed code unless you download a new 
>>>> Tiddlywiki, redownload all your plugins, and transfer all your tiddlers 
>>>> from your old file. But hey! Maybe you're running TiddlyWiki on your 2000 
>>>> era Noki

Re: [tw5] [Plugin] Presenting TW5-Uglify! Plugin compression the TiddlyWIki way!

2021-06-18 Thread Flibbles
Hey Jan,

I'm glad Uglify works well for you. To answer your questions


   1. Removing overridden core Tiddlers could reduce the code size 
   somewhat, but I'm not sure how often that use case would come up. Even in 
   my beastly TiddlyWiki projects, my overridden tiddlers don't make up very 
   much space, particularly since I (and most people I'd think) only override 
   smallish tiddlers. If it's something larger, a monkey-patch injection is 
   used more often. Meanwhile, removing those overridden shadows could lead to 
   a whole slew of nasty bugs if someone A) Removed the override down the 
   line, or B) Tried to export their project into any form other than exactly 
   what it is.
   2. Temporarily removing deactivated plugins seems out of scope for a 
   content compression plugin (But just by a little. It compresses plugins. 
   Removing them is a different job), and it's probably best done by the user. 
   If they are serving versions of a tiddler where they want certain plugins 
   excluded, they'd could use the publishFilter. A slightly elaborate 
   tiddly-filter could exclude all deactivated plugins.


Hope this helps!
-Flibbles

On Friday, June 18, 2021 at 6:45:03 PM UTC-4 Jan wrote:

> Hi Flibbles,
> great idea! My wikis tended to grow recently this seems to be a great 
> remedy.
> Some Questions: Could it also remove 
> - overridden core Tiddlers
> - temporarily deactivated plugins and inactive themes 
> from the version which is served?
>
> Best wishes Jan
>
> Am Di., 19. Jan. 2021 um 21:26 Uhr schrieb Flibbles <
> challenge...@gmail.com>:
>
>> Some people want a minified version of the TW5 core, but it'd be too much 
>> work to maintain.
>> Some people think it should remain uncompressed for the sake of editors, 
>> but TW5 continues to grow by the day.
>> Some developers compress their plugins, making efficient code, but it's a 
>> pain for anyone debugging it.
>> Some developers leave their plugins uncompressed, but that means it's 
>> larger than necessary for 90% of all end-users.
>>
>> Now there's a solution for everybody: TW5-uglify.
>>
>> This is a plugin primarily designed to be used by a Node.JS server. Your 
>> server has access to all your uncompressed and unpacked plugins, which is 
>> fine, since servers have the speed and memory for it. But what it sends to 
>> browsers are fully compressed plugins. Your little smart phones and tablets 
>> get the efficient TW5 they deserve.
>>
>> Or maybe you're a plugin developer who wants to minify their code. Now 
>> you no longer have to resort to using npm-gulp like some kind of chump. 
>> Your build process can remain an entirely TiddlyWiki process.
>>
>> Or maybe you want to miniify your standalone TiddlyWiki file. You can, 
>> but... think hard about this before you do it. Because unlike with 
>> TW5-Uglified server, compressing your standalone files is a one-way 
>> process. You'll forever have compressed code unless you download a new 
>> Tiddlywiki, redownload all your plugins, and transfer all your tiddlers 
>> from your old file. But hey! Maybe you're running TiddlyWiki on your 2000 
>> era Nokia phone in an wifi wasteland. Then go ahead.
>>
>> Check it out.
>> Here's the demo site. <https://flibbles.github.io/tw5-uglify/>
>> And here's the github page <https://github.com/flibbles/tw5-uglify>.
>>
>> Let me know what you all think.
>>
>> -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/2ce6fad2-8600-4c73-940c-515548e49c1en%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/2ce6fad2-8600-4c73-940c-515548e49c1en%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/f7283bcf-1f16-426e-bfd7-402dfe712a45n%40googlegroups.com.


Re: [tw5] Re: Relink Plugin Performance

2021-07-02 Thread Flibbles
I don't know of a way to get Google to tell me when conversations come up 
concerning Relink, so I'm always late to the party.

PMario is right. Relink has to scrutinize every tiddler when it looks for 
relinking, but it does have an indexer, and that indexer tries to reduce 
the need for a "full tiddlywiki check" as much as possible.


   - The first rename you make after loading your tiddlywiki will take a 
   while. All the subsequent ones will be much quicker, since it will have a 
   shortlist of which tiddlers are relevant.
   - The first keystroke you make when typing in a new title (or looking at 
   the Relink References tab) will also cause a delay. This too is cached, so 
   it should only happen once per browser tab (or once per $:/tags/Macro 
   change).

Hope this helps! You aren't completely wrong that Relink might seem slower 
in certain respects in V2. I had to scrap a ton of old optimizations I had, 
but I got the indexing working as best I could to compensate.

-Flibbles

On Monday, June 7, 2021 at 12:40:04 AM UTC-4 PMario wrote:

> On Monday, June 7, 2021 at 6:26:01 AM UTC+2 History Buff wrote:
>
>> Thanks. That explains it. I’m assuming that’s why Relink performs 
>> similarly since it’s has to calculate backlinks. Would that be a correct 
>> assumption?
>>
>
> Yes, It's not only backlinks. The relink plugin does a lot more checks, if 
> you change the tiddler title. ... It checks all the tags-fields in all 
> tiddlers. It checks all the list-fields and then it checks all the texts, 
> if there are macros, widgets and so on using this tiddler as a parameter. 
> .. So there is a lot of work to do.
>
> If you change the title of a tiddler, the relink-mechanism is activated. 
> It creates the "The following tiddlers will be updated" "dropdown" element. 
> ... If you don't save the tiddler, this list will probably be recalculated 
> with every edit key-stroke . 
>
> So if you change the title, it may be best to save the tiddler and then 
> edit the text afterwards if needed.
>
> -mario
>

-- 
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/1f5ea3b0-e5f9-4804-9044-6af6376c45a4n%40googlegroups.com.


Re: [tw5] Re: A weird request

2021-07-02 Thread Flibbles
Hey. I'm unsure why Relink isn't able to address this. It should be able to 
rename, AND it should be able to show you all references where that macro 
is used.

Are you saying that the macro argument to mapline isn't getting relinked?

I'm looking at your showModal(tid) that you posted. That would easily be 
able to relink "tid" if you include a relink declaration

\relink showModal tid
\define showModel(tid)
blah blah blah
\end

Am I misunderstanding your problem?
On Thursday, July 1, 2021 at 9:22:49 PM UTC-4 David Gifford wrote:

> Hi Tones thanks for the response. See replies below
>
> On Thu, Jul 1, 2021 at 7:21 PM TW Tones  wrote:
>
>> David,
>>
>> I think I have a possible answer, but can not yet repeat your code and 
>> see what is actually does as a start. Can you share the showModal macro and 
>> any other dependencies please?.
>>
>
> This isn't the file I am referring to, but it is the same showmodal code: 
> https://giffmex.org/wiki/nt1.a.html#%24%3A%2F.giffmex%2FEric%2FShowModal, 
> a gift from Eric, slightly modified by me.
>
>>
>> Also when you say "I can write a line in Clipboard", could you share 
>> more, because I think there may be further automation and simplification 
>> possible.
>>
>
> What I mean is, I will have an edit-text window for the tiddler Clipboard, 
> to have open in any tiddler, as an editTemlate tiddler. My hope is to be 
> able to type a phrase in the Clipboard tiddler, and click an editortoolbar 
> button to stamp the following: @@.map1 XX @@<> <$link 
> to='XX'>{{$:/core/images/link}} 
>
> Where XX = the present text of the Clipboard tiddler.
>
> Then I would clear Clipboard and add new text, and hit the editor toolbar 
> button again.
>
>>
>> Thanks
>> Tones
>>
>> On Friday, 2 July 2021 at 09:39:27 UTC+10 David Gifford wrote:
>>
>>> Hi everyone
>>>
>>> I managed to create a macro where I would add <>> delicious">> and in view mode it would show the equivalent of 
>>>
>>> <$view tiddler="$tiddler$" field="title"/> 
>>> <> <>> "$tiddler$">>
>>>
>>> It was a super fast  workflow and kept my tiddler pretty clean. I was so 
>>> happy to have figured that out on my own. But I quickly realized that the 
>>> links do not create backlinks, and te relink plugin doesn't rename them. 
>>> And searching won't show the tiddler where the macro is.
>>>
>>> Now I am wondering: Is there a better way? I am thinking an 
>>> editortoolbar button that 
>>>
>>> 1) grabs the text of another tiddler where I paste that line of text 
>>> (let's say the tiddler is titled "Clipboard" and I have written in the text 
>>> field, Ice cream is delicious
>>> 2) stamps the following:
>>> @@.map1 Ice cream is delicious. @@<> 
>>> <$link to=' Ice cream is delicious'>{{$:/core/images/link}}
>>>
>>> That way, I can write a line in Clipboard, then stamp the line as 
>>> indicated above in the tiddler I am working on, and have it show up as 
>>> simple text, modal and link. And backlinks will show in a view template 
>>> tiddler. I recognize that renaming would only update the link, not the 
>>> modal or simple text. But for what I am doing, I don't foresee needing to 
>>> rename links.
>>>
>>> Any ideas?
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/LPOIaGiXiPY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/cce8881f-fd64-4a7b-9b05-f523ae960024n%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/3128d9e0-b925-47cb-aceb-e7c1efcc53c3n%40googlegroups.com.


Re: [tw5] Re: A weird request

2021-07-03 Thread Flibbles
I was just about to remark to the same effect. Backreferences only includes 
links with string values, nothing else. But Relink has something a little 
more powerful.

You have a tiddler "$:/.giffmex/ViewTemplate/Backlinks", If you change its 
contents to:

<>

Then it will include all the references to a given tiddler at the bottom of 
that tiddler. Downside: It will include them ALL. So tags, lists, macros, 
references, transclusions. All will get listed there.

On Saturday, July 3, 2021 at 10:33:29 AM UTC-4 cj.v...@gmail.com wrote:

> On Saturday, July 3, 2021 at 11:24:56 AM UTC-3 David Gifford wrote:
>  
>
>> Here is an example: Open  Acts exegesis 
>> . If 
>> you click the link in that tiddler to go to 
>> Acts
>>  
>> 17 general 
>>  , 
>> you will see there is no link back to Acts exegesis at the bottom of the 
>> tiddler.
>>
>>
> Looking at Acts 17 general, click on info, and click on Relink references 
> tab.  Relink gives a backlink to Acts exegesis.  Just a matter of including 
> Relink references to the standard TiddlyWiki backlinks.
>

-- 
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/652dfc8e-20b2-4549-abc4-d8c42a541a04n%40googlegroups.com.


[tw5] Re: Does Relink add a new filter operator?

2021-07-10 Thread Flibbles
Hey all,

The behavior of those Relink filter operators is undefined because I didn't 
wish to lock their behavior down and have to remain backward compatible for 
them (for instance, I did make changes to their behavior between V1 and 
V2). They are highly specific toward Relink's internal needs, and if I 
could have prevented them from being publicly exposed, I probably would 
have.

However, I'm also finding out that a lot of people are starting to use 
those filters anyway, so it may be time for me to define them in the 
documentation and ensure ongoing support for them. There seems to be a 
demand for them.

-Flibbles

On Wednesday, July 7, 2021 at 11:02:42 AM UTC-4 Si wrote:

> Thanks David, that's very handy.
>
> On Wednesday, 7 July 2021 at 13:47:57 UTC+1 David Gifford wrote:
>
>> Yes, this is a nice new way of filtering lists.
>>
>> Try <$list filter=" 
>> [!is[system]all[current]relink:backreferences[]!title[$:/StoryList]sort[title]]".
>>
>> On Tuesday, July 6, 2021 at 2:59:10 PM UTC-5 Si wrote:
>>
>>> Relink <https://flibbles.github.io/tw5-relink/> adds a "Relink 
>>> references" tab the info panel for a tiddler, which appears to show any 
>>> fields, links, macros etc. that reference the current one.
>>>
>>> Looking at the template for this (
>>> $:/plugins/flibbles/relink/ui/TiddlerInfo/ReferencesTemplate 
>>> <https://flibbles.github.io/tw5-relink/#%24%3A%2Fplugins%2Fflibbles%2Frelink%2Fui%2FTiddlerInfo%2FReferencesTemplate>),
>>>  
>>> it appears to use a "relink" filter operator:
>>>
>>> <$list filter="[relink:report]">
>>>
>>> I can't find any documentation on this, is it something that is intended 
>>> to be available to end users? I would potentially find it very useful for 
>>> listing backlinks that are contained within a macro.
>>>
>>

-- 
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/6b5f2a07-0a88-43a3-a0b4-c1474fdd558cn%40googlegroups.com.


[tw5] Re: Markdown usage

2021-04-30 Thread Flibbles

   
   1. The markdown way to link to other tiddlers is: [Caption for 
   link](#TiddlerName)
   If your tiddler has spaces, it needs escaping.
   [Caption to link](#Tiddler%20Name)
   2. Calling macros works just fine in Markdown text (as long as it's an 
   inline call). If you want to declare macros, you need to alter 
   "$:/config/markdown/renderWikiTextPragma" and add macrodef
   3. I think your best bet is probably transclusion. I messed around with 
   a way to mix markdown and wikitext. Results weren't great.
   4. Conversion between the two? Not that I know of. Though like Torax 
   said, you can put most wikitext in a markdown file and it'll render.
   

On Friday, April 30, 2021 at 11:05:37 AM UTC-4 Mark S. wrote:

> In the latest official markdown plugin, you can put most wikitext into 
> your markdown text that fits on *a single line*. Unfortunately, this does 
> *not 
> include links [[ ]]* because that markup resembles markdown. But you can 
> use the link widget
>
> <$link to"mytiddler/>
>
> If you want to put markdown into your wikitext, you can transclude the 
> rendered contents of a markdown tiddler into your text:
>
> {{mymarkdowntiddler}}
>
> AFAIK, no one has made a markdown-to-wikitext or vice-versa converter. You 
> could possibly use HTML as an intermediary and then convert to one or the 
> other.
>
> Markdown is the *de facto* markup language used in virtually all modern 
> apps. There is no prospect that the rest of the world will suddenly embrace 
> wikitext. It would be great if we could work seamlessly with markdown, but 
> I guess we have to use whatever work-arounds we can get.
>
> On Friday, April 30, 2021 at 7:09:36 AM UTC-7 zsigmond@gmail.com 
> wrote:
>
>> Hello,
>>
>> Please help me out if these are possible somehow:
>>
>>- Linking tiddlers from MD? 
>>- Or if possible even macros in MD?
>>- Making part of the TW5 formatted tiddler to be rendered as MD, or 
>>in MD to render part of it as TW5?
>>- Conversion between TW5 and MD?
>>
>>
>> Thanks,
>> Laci
>>
>>

-- 
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/155786c9-0a66-4a3c-830b-93471ac310b7n%40googlegroups.com.


Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2021-03-23 Thread Flibbles
Not sure I understand. Relink isn't integrated with any package managers 
like npm. To install Relink under Node.JS, you'd download the source from 
github, and the github page <https://github.com/flibbles/tw5-relink> has 
instructions on how to install.

On Wednesday, March 24, 2021 at 1:15:49 AM UTC-4 Mohammad wrote:

> Hi Flibless,
> Thank you for the update! Relink and Uglify are a constant part of most of 
> my wikis!
> I use both plugins on Node.JS and would like to have a link under Install 
> on demo page redirect/instruct to download the node version of plugins.
>
> Best wishes
> Mohammad
>
>
> On Wed, Mar 24, 2021 at 9:19 AM Flibbles  wrote:
>
>>
>> Hello all!
>>
>> Just announcing that Relink V2 <https://flibbles.github.io/tw5-relink/> 
>> has just been released. Besides support for V5.1.23 Tiddlywiki features 
>> like multi-operand filter operators, this integrates with the Tiddlywiki 
>> index.
>>
>> And THAT is a big thing (for me anyway). This version is much much 
>> faster. If were encountering speed issues with your Tiddlywiki at around 
>> 2500+ tiddlers, Relink may have unfortunately been to blame. It slowed down 
>> basic *typing* in if enough Relink info panels were open. Not anymore. 
>> It's much faster now.
>>
>> If you built any modules for Relink, it SHOULD continue to relink just 
>> fine, but part of the overhaul I did required me to offload all the Relink 
>> Info panel work to a new "report" method which all modules use.  If you 
>> want your module to fully integrate with V2, see the demo page for 
>> details <https://flibbles.github.io/tw5-relink/#Migration%20to%20V2>. 
>> better yet, reach out to me, because I can probably migrate your modules in 
>> about 10 seconds.
>>
>> Anyway! Hope you all enjoy. This version of Relink will save you seconds. 
>> *Seconds*!
>>
>> -Flibbles
>> On Thursday, December 17, 2020 at 1:03:51 AM UTC-5 Flibbles wrote:
>>
>>> Yes. The parent-plugin field is present on both of Relink's supplemental 
>>> plugins.
>>>
>>> On Thursday, December 17, 2020 at 12:45:13 AM UTC-5 Mohammad wrote:
>>>
>>>> Flibbles,
>>>>  Have you tried the parent-plugin field  to distribute subplugin of 
>>>> relink as its children?
>>>> Take a look in  https://tiddlywiki.com/prerelease/#PluginMechanism 
>>>> presented in 5.1.23
>>>>
>>>>
>>>> Best wishes
>>>> Mohammad
>>>>
>>>>
>>>> On Wed, Dec 16, 2020 at 4:24 AM Flibbles  
>>>> wrote:
>>>>
>>>>> For those who may be interested, many people requested that Relink be 
>>>>> able to handle renaming titles of nested directory tiddlers associated 
>>>>> with 
>>>>> a renamed tiddler.
>>>>>
>>>>> Here it is. Relink-titles, the supplemental plugin 
>>>>> <https://flibbles.github.io/tw5-relink/#Plugins%2FTitles>.
>>>>>
>>>>> It also allows for custom rename rules based on filters, as well as 
>>>>> rules introduced by 3rd party plugins.
>>>>>
>>>>> Currently, the only built in rule is the directory tree one. I 
>>>>> couldn't think of any others that people would generally want. If you 
>>>>> know 
>>>>> of any, let me know.
>>>>>
>>>>> -Flibbles
>>>>> On Monday, May 25, 2020 at 11:06:03 PM UTC-4 joshua@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Actually, that's really cool. I have that on my ToDo list, but have 
>>>>>> put it off while I tinker with UI stuff.
>>>>>>
>>>>>> Best,
>>>>>> Joshua F
>>>>>>
>>>>>>
>>>>>> On Monday, May 25, 2020 at 6:54:16 PM UTC-7, Flibbles wrote:
>>>>>>>
>>>>>>> *Now with Markdown support!*
>>>>>>>
>>>>>>> ...in the form of a supplemental plugin.
>>>>>>>
>>>>>>> But I integrated Relink v1.10 with Tiddlywiki's PluginLibrary 
>>>>>>> wizard, so now when you go to "Get More Plugins", Relink has it's own 
>>>>>>> tab 
>>>>>>> where you can easily see all Relink sub-plugins (installed or not 
>>>>>>> installed), what needs updating, and then update with a single click. 
>>>>>>> It's 
>&

Re: [tw5] Re: Presenting: a plugin which automatically relinks renamed tiddlers

2021-03-23 Thread Flibbles

Hello all!

Just announcing that Relink V2 <https://flibbles.github.io/tw5-relink/> has 
just been released. Besides support for V5.1.23 Tiddlywiki features like 
multi-operand filter operators, this integrates with the Tiddlywiki index.

And THAT is a big thing (for me anyway). This version is much much faster. 
If were encountering speed issues with your Tiddlywiki at around 2500+ 
tiddlers, Relink may have unfortunately been to blame. It slowed down basic 
*typing* in if enough Relink info panels were open. Not anymore. It's much 
faster now.

If you built any modules for Relink, it SHOULD continue to relink just 
fine, but part of the overhaul I did required me to offload all the Relink 
Info panel work to a new "report" method which all modules use.  If you 
want your module to fully integrate with V2, see the demo page for details 
<https://flibbles.github.io/tw5-relink/#Migration%20to%20V2>. better yet, 
reach out to me, because I can probably migrate your modules in about 10 
seconds.

Anyway! Hope you all enjoy. This version of Relink will save you seconds. 
*Seconds*!

-Flibbles
On Thursday, December 17, 2020 at 1:03:51 AM UTC-5 Flibbles wrote:

> Yes. The parent-plugin field is present on both of Relink's supplemental 
> plugins.
>
> On Thursday, December 17, 2020 at 12:45:13 AM UTC-5 Mohammad wrote:
>
>> Flibbles,
>>  Have you tried the parent-plugin field  to distribute subplugin of 
>> relink as its children?
>> Take a look in  https://tiddlywiki.com/prerelease/#PluginMechanism 
>> presented in 5.1.23
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Wed, Dec 16, 2020 at 4:24 AM Flibbles  wrote:
>>
>>> For those who may be interested, many people requested that Relink be 
>>> able to handle renaming titles of nested directory tiddlers associated with 
>>> a renamed tiddler.
>>>
>>> Here it is. Relink-titles, the supplemental plugin 
>>> <https://flibbles.github.io/tw5-relink/#Plugins%2FTitles>.
>>>
>>> It also allows for custom rename rules based on filters, as well as 
>>> rules introduced by 3rd party plugins.
>>>
>>> Currently, the only built in rule is the directory tree one. I couldn't 
>>> think of any others that people would generally want. If you know of any, 
>>> let me know.
>>>
>>> -Flibbles
>>> On Monday, May 25, 2020 at 11:06:03 PM UTC-4 joshua@gmail.com wrote:
>>>
>>>> Actually, that's really cool. I have that on my ToDo list, but have put 
>>>> it off while I tinker with UI stuff.
>>>>
>>>> Best,
>>>> Joshua F
>>>>
>>>>
>>>> On Monday, May 25, 2020 at 6:54:16 PM UTC-7, Flibbles wrote:
>>>>>
>>>>> *Now with Markdown support!*
>>>>>
>>>>> ...in the form of a supplemental plugin.
>>>>>
>>>>> But I integrated Relink v1.10 with Tiddlywiki's PluginLibrary wizard, 
>>>>> so now when you go to "Get More Plugins", Relink has it's own tab where 
>>>>> you 
>>>>> can easily see all Relink sub-plugins (installed or not installed), what 
>>>>> needs updating, and then update with a single click. It's super slick, 
>>>>> guys. For real!
>>>>>
>>>>> But probably not worth all the work it took.
>>>>>
>>>>> -Flibbles
>>>>>
>>>> -- 
>>>
>> 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 view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/tiddlywiki/a57a3b3b-9a8b-4147-8717-40787ef67befn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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/fc82a8f9-81b6-423f-8093-ccf285024916n%40googlegroups.com.


[tw5] Re: rQuickTid vs Relink: buggy cloning instead of renaming

2021-02-23 Thread Flibbles
Clone? So is this the "Reuse content" button in the tiny rQuickTid window? 
(I've never used, or even heard of, rQuickTid, so you'll need to bear with 
me.)

On Tuesday, February 23, 2021 at 11:21:54 AM UTC-5 bartosz.w...@gmail.com 
wrote:

> Hello there.
>
> I started using rQuickTid . It is great 
> for creating quick notes outside of main TW window. Unfortunately there 
> were some problems with updating TOC so in the code I changed 
> *action-setfield 
> *to *action-createtiddler *and it made a difference.
>
> But latter I have found out that Relink 
>  has some problems with tiddlers 
> created using rQT. Clone with new title appears but old one stays instead 
> of being deleted. Minor bug but annoying especially when using rQT en masse.
>
> *Any ideas what can be a cause?*
>
> *Can rQT code make tiddlers that are different from Relink point of view?*
>
> -Bartosz
>

-- 
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/bfa80a36-bb27-483c-90b2-6156e39965fcn%40googlegroups.com.


  1   2   >