[twdev] Dynamical exchangeable PageTemplate?

[Mirko Richter]

Hi,

in my project a need switch want to switch the PageTemplate dynamically. 
For that i modified my local PageTemplate like this:


(and remind myself using a Diff-Mechanism if someone changes the 
PageTemplate-Tiddler during TW5-Development to have a look on it ;) )

The code i removed in the Screenshot above (marked mostly red) is part of 
the my "DefaultPageTemplate". When i like to switch to another style just 
change "ActivePageTemplate" to point to my active Template. It works like a 
charm for me (but may introduce performance-issues).

However, i more and more get the feeling that others also need to solve 
that problem and ask myself how they do that. Is there something i oversee? 
If not, can it be implemented into the core-TW5 somehow to make that change 
in my TW5-Instance a little less >>unstable<< (just means the fact that i 
overwrite the core-ShadowTiddler)?

Thanks a lot,
Mirko

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/a1af12ed-f3cf-471b-b04a-20fe78125098o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

I need to clock Off, almost midnight here, Great work, 
The revolution is Brewing :)
Tony

On Friday, 18 September 2020 at 23:44:48 UTC+10 TonyM wrote:

>
> Mario,
>
>
>> The Usage string is: ° » ´ › - -- --- 
>>
>
> Lol
>
> Actually finally we have a way to obfuscate! for good I mean, like hard to 
> find strings. Or user or password details?
>
> Regards
> Tony
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/244c7b2c-28eb-42e2-ab1e-6384c1645df8n%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

Mario,


> The Usage string is: ° » ´ › - -- --- 
>

Lol

Actually finally we have a way to obfuscate! for good I mean, like hard to 
find strings. Or user or password details?

Regards
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/46b3368b-7305-47f2-976f-5ca6bf12d211n%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 2:18:47 PM UTC+2, TonyM wrote:
>
> In the new Google Groups I can edit an existing post :( again
> *Additional Content*
>
> In the below it demonstrates how convention allows the Capital to be used, 
> eg Big X refers to Close all
>
>- Close all works, but not copy to clipboard?
>- Again this shows how rather than write a macro you can use  
>_element="$widget" to simply code a shortcut for a button
>   - I imaging this should work in lists with variable content as well?
>- My use here of the degree, may be a convention for customised 
>wikitext buttons as an example, of my prior idea of preconfigure the 
>behaviour, or at least set a de facto standard.
>
>
> \customize degree=X _element="$button" message="tm-close-all-tiddlers"
> \customize degree=C _element="$button" message="tm-copy-to-clipboard" 
> param={{!!text}}
> \customize degree=x _element="$button" message="tm-close-tiddler"
>
> °X Close all 
> °x Close me
> °C copy content
>
> Again,
> This use of X for All and x for here would be a suggested de facto 
> standard to guide users (Which they can ignore)
> But having some standards will open people eyes to the possibilities as 
> well as encouraging some informal standards.
>

That's definitely something that should work as inline-text eg: If you 
click this °°x Close me°° button, this tiddler will be closed. So we can 
use working buttons within wikitext and still have readable prose text, 
that makes sense.

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/dcb95ccf-5685-45b8-b868-6574e1f3ace9o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

It would be used mainly for documentation purposes
-m

On Friday, September 18, 2020 at 2:27:27 PM UTC+2, PMario wrote:
>
> That's a nice example.
>
> But what I wanted is a "partial" copy-to-clipboard, which isn't possible 
> atm. The <$button> body  is used to create the button-text 
> instead of defining the text, that should be copied. 
>
> So the widget I'm imagining is more like this
>
> <$clipboard buttonText="copy to clipboard" class="" showCode=yes/no 
> showText=yes/no mode=block/inline template="name of a template tiddler">
> Content, that is copied to the clipboard
> 
> just brainstorming
> -m
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/422176b3-298c-4740-9605-209f5a2734dbo%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

That's a nice example.

But what I wanted is a "partial" copy-to-clipboard, which isn't possible 
atm. The <$button> body  is used to create the button-text 
instead of defining the text, that should be copied. 

So the widget I'm imagining is more like this

<$clipboard buttonText="copy to clipboard" class="" showCode=yes/no 
showText=yes/no mode=block/inline template="name of a template tiddler">
Content, that is copied to the clipboard

just brainstorming
-m

 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/c4f96160-5754-4379-b3b5-9d4366108fdco%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

Hi,

I think the following works well out of the box for me. 

».hl several lines of paragraph text with 
single line breaks
where onyl 1 indicator is needed

just a thought.
-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/2f99abcb-150b-4e0b-a17f-3560354e2f47o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

In the new Google Groups I can edit an existing post :( again
*Additional Content*

In the below it demonstrates how convention allows the Capital to be used, 
eg Big X refers to Close all

   - Close all works, but not copy to clipboard?
   - Again this shows how rather than write a macro you can use  
   _element="$widget" to simply code a shortcut for a button
  - I imaging this should work in lists with variable content as well?
   - My use here of the degree, may be a convention for customised wikitext 
   buttons as an example, of my prior idea of preconfigure the behaviour, or 
   at least set a de facto standard.


\customize degree=X _element="$button" message="tm-close-all-tiddlers"
\customize degree=C _element="$button" message="tm-copy-to-clipboard" 
param={{!!text}}
\customize degree=x _element="$button" message="tm-close-tiddler"

°X Close all 
°x Close me
°C copy content

Again,
This use of X for All and x for here would be a suggested de facto standard 
to guide users (Which they can ignore)
But having some standards will open people eyes to the possibilities as 
well as encouraging some informal standards.

Tony

On Friday, 18 September 2020 at 22:05:44 UTC+10 TonyM wrote:

> All,
>
> In the below it demonstrates how convention allows the Capital to be used, 
> eg Big X refers to Close all
>
>- Close all works, but not copy to clipboard?
>- Again this shows how rather than write a macro you can use  
>_element="$widget" to simply code a shortcut for a button
>   - I imaging this should work in lists with variable content as well?
>- My use here of the degree, may be a convention for customised 
>wikitext buttons as an example, of my prior idea of preconfigure the 
>behaviour, or at least set a de facto standard.
>
>
> \customize degree=X _element="$button" message="tm-close-all-tiddlers"
> \customize degree=C _element="$button" message="tm-copy-to-clipboard" 
> param={{!!text}}
>
> °X Close all  
> °C copy content 
>
>
> Regards
> Tony
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/75e52091-b6a1-4fc2-ae98-48437d284d58n%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 1:39:42 PM UTC+2, TonyM wrote:


Example (just a brainstorm) may be inaccurate as I learn still to memorise 
> the existing, its just the concept. I am still to learn how some simple 
> defaults will lend them self to each character. But publishing firs as just 
> a larger set of symbols and no defaults my b fine with a view to giving 
> them some defaults as we lean more about the scope and opportunities.
>
>-  ° degree use for emphasis 
>
> In my examples I did use the degree ° ID to indicate functions that have 
been "imported"

>
>-  ´ to introduce styles
>
> It was the first one, that worked after dot failed. So we are used to it. 

>
>-  › dividers lines/headings 
>
> I thought you would want them for CTRL-A - toggle button as a fast way to 
apply custom styles
and relatively nice way to read prose text. 

>
>-  _ specials including html 
>
> I think I could live with _ for "specials" like HTML tags. ... Will have a 
closer look. 

>
>-  » Formatting blocks
>
> I want to use it for simple paragraph formatting 

>
>-  ≈ indicating state
>
> This is a spare one at the moment. It also has 2 elements in the char. 
Which indicates \n\n as the default _endString

---

°° some text°° is used at the moment for "\customizeinline" .. But only 
°°.class.c.lass is implemented atm°°

We will need to use it for a wile and then we can see, if we can identify 
some patterns ... 

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/d490fbda-10f6-49d0-a936-16cbc65ac466o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

All,

In the below it demonstrates how convention allows the Capital to be used, 
eg Big X refers to Close all

   - Close all works, but not copy to clipboard?
   - Again this shows how rather than write a macro you can use  
   _element="$widget" to simply code a shortcut for a button
  - I imaging this should work in lists with variable content as well?
   - My use here of the degree, may be a convention for customised wikitext 
   buttons as an example, of my prior idea of preconfigure the behaviour, or 
   at least set a de facto standard.


\customize degree=X _element="$button" message="tm-close-all-tiddlers"
\customize degree=C _element="$button" message="tm-copy-to-clipboard" 
param={{!!text}}

°X Close all  
°C copy content 


Regards
Tony

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/dbb04a57-b6b4-43e8-b77f-4b767ee002a0n%40googlegroups.com.

[twdev] Re: Poll-Time for fetching Tiddler-List not *dynamically* configurable

[Mirko Richter]

This just means: by using the value in a config-tiddler. if it changes, the 
poll-time should also change accordingly. Sorry for the lack of clarity...

Mirko

Am Freitag, 18. September 2020 13:26:53 UTC+2 schrieb PMario:
>
> On Friday, September 18, 2020 at 1:06:23 PM UTC+2, Mirko Richter wrote:
>
> Can the intervall be made Tiddler-Configured with respect to the current 
>> wiki-state?
>>
>
> I think it would be possible. .. But what do you mean by "current 
> wiki-state"
>
> -m
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/8b4a8bb4-812f-4ded-a126-eb4d5b41ac3eo%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 1:45:12 PM UTC+2, TonyM wrote:

These answers of yours really are demonstrating the flexibility. We need 
> some how to capture this knowledge, without making it too complex for 
>
users.
>

Yea, I try to build a "story" around the possibilities. ... I did try to 
start with the simple things. ... But if you have a look at the code of 
this tiddler: 
https://wikilabs.github.io/editions/tick-text/#test-high-abstraction

The Usage string is: ° » ´ › - -- --- 

Which is close to insanity or close to Brainf*ck 
 syntax and IMO doesn't make sense 
at all. ... BUT it was nice to see, that it works. 

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/4e9c0571-7854-4a6d-97be-f72c5da35ec3o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

Mario,

I think this could be an independent solution. ANd alias may be away to go, 
but I am thinking more with a view to core one day, perhaps that's where a 
simplified alias should go as well?

Regards
Tony

On Friday, 18 September 2020 at 20:55:56 UTC+10 PMario wrote:

> I'll give it an   OT - marker. 
> But it is slightly related. 
>
> You are right. "readable" wikitext shouldn't contain the $:/xxx/yyy/ 
> namespace. 
>
> I was already thinking about the possibility to use my uni-link plugin 
> with the custom-markup 
> plugin. 
>
> At the moment unilink allows you to give every tiddler an "aliases" field, 
> which can contain several aliases. 
> At the moment it will _not_ use "shadow" tiddlers for speed reasons. We 
> know, that no core shadows use aliases atm. This would need to be changed. 
>
> [[aliasName|?]] will create a link to any tiddler including system 
> tiddlers. 
>
> [[AliAsNaMe|?]] is _not_ case sensitive, this gives the user the 
> possibility to nicely use it in prose text. eg: At the start of the line. 
>
> [[aliasName|?c]] will show the caption field as the link text. 
> [[aliasName|?myField]] can use any field. 
>
> --
>
> The right sidebar More: Aliases tab gives an overview about used aliases. 
>
> The plugin comes with 2 new toolbars to improve usability of aliases. 
>
> There are some filter functions for alias-backlinks ... and so on. 
>
> IMO . It should be possible to use \importcustom [[alias|?]] ... BUT I'm 
> not sure if this is an advantage already. 
>
> ---
>
> I was hesitating to allow [[alias|?{]]  or something similar as a 
> representation for {{real tiddler name}}
>
> The only reason to do that, would be the "backlinks" mechanism would work 
> for these links. 
>
> just some thoughts.
>
> -m
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/c407d216-4b76-4f31-947f-aadd608e4d33n%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

Mario,

These answers of yours really are demonstrating the flexibility. We need 
some how to capture this knowledge, without making it too complex for users.

Tony

On Friday, 18 September 2020 at 21:11:32 UTC+10 PMario wrote:

> On Friday, September 18, 2020 at 4:21:21 AM UTC+2, TonyM wrote:
>
> As I said before, I love the "details" example of yours. However I just 
>> wanted to let you know, I do not resonate with you use of multiple hyphens 
>> -- and --- etc, perhaps because of my eye-site or the difficulty matching 
>> or remembering how many to do what. This example with the existing system 
>> is a little better for me;
>>
>> \customize tick="d" _element="details" _params=
>> ".notop.cbox.cbox-primary.hard-linebreaks" _endString="/d" _mode=block 
>> open  
>> \customize tick="s" _element="summary" _params=".margin-init"
>>
>> ´d ´s Details - Summary /s
>> line 1
>> line 2
>> /d
>> So I am quite happy with the "out of the box" solution.
>>
>
> That's fine. You can use it that way. I'll add some more information, that 
> the _endString is "just a convention" (In this case my convention). But 
> everyone can develop their own thing. 
>  
>
>> However this prompts me to ask, if for block custom wikitext, that could 
>> we automate the end string if desired? eg wrap something in 
>> ´d details here ´/d
>>
>
> tick automatically defaults to end of line. So you can skip it, if there 
> is only 1 line like your example
>  
>
>> ´d 
>> line 1
>> line 2
>> ´/d
>>
>> Where the ´/d or /d
>>
>
> This can be done. You only need to configure it that way. 
>  
>
>>
>>- is the default end-string unless one is provided
>>
>> yes. 4 + 2 ... 4 elements use \n and 2 elements use \n\n by default. 
>
>>
>>- and of course all "Symbol/anything" are only possible end strings 
>>
>> It has to be a unicode character. So it basically depends on the OS and 
> the installed unicode fonts, what's possible. 
>  
>
>> I expect this details and similar incantations are going to give us 
>> something many have called for, for a long time, easy sliders and toggled 
>> content. This also helps with Q&A quizzes, tests etc...
>>
>
> Yes. .. I was thinking about a "details widget", that can store the state. 
>
> There may be some CSS eg: for printing, that makes all the details open by 
> default ... or something similar. 
>  
>
>>
>> Question;
>> In the following case where I define a "More Details"
>> \customize tick="md" _element="details" _params=
>> ".notop.cbox.cbox-primary.hard-linebreaks" _endString="/md" _mode=block  
>> \customize tick="m" _element="summary" _params=".margin-init"
>>
>> ´md ´m
>> line 1
>> line 2
>> /md
>>
>>- Is there a way the tick="m" provides its own content eg more...
>>
>> Use: 
>
> ´md ´m more ...
>  
>
>>
>>- Or could we even hide the ´m in the ´md definition? ie define the 
>>summary in the more details since it is
>>
>>
>>- a default?
>>
>> If you use this: 
>
> ´md 
> line 1
> line 2
> /md
>
> The browser will use a "default" summary.* It's a _browser_ thing*. So I 
> do nothing here. 
>
> -mario
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/b81424f0-cac8-4e67-84a6-988c167272f4n%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

Sorry,

Not sure what you mean here, but its intriguing.

Tony

On Friday, 18 September 2020 at 20:58:13 UTC+10 PMario wrote:

> On Friday, September 18, 2020 at 3:40:10 AM UTC+2, TonyM wrote:
>
> In the process of us developing this solution I see the value in the use 
>> of templates, but this makes me baulk, because the standard naming needs to 
>> be a system tiddler, then as a result it needs another prefix such as in my 
>> last example 
>> $:/core/ui/ListItemTemplate2 we want to hide these so we are forced to 
>> use $:/
>>
>
> You can use a field name: my-field: template for $:/xxx
>
> \customize template={{{[my-field[template]]}}} should give you the right 
> tiddler name
>
> I didn't test it, but I think it should owrk. 
> -m
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/644c77a7-0790-4a01-a740-35a9946a099fn%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

Mario,

Some responces;

>
> That will be a ToDo, since we will need to improve the TW doc quite a bit, 
> so we can link to it. The existing docs 
> 
>  
> for specific styling imo needs some love
>

So true 
 

>  
>
>>
>>- Will there be some smart defaults for each special Characters out 
>>of the box, so unless they are inadequate they serve a purpose right away?
>>   - angel is already somewhat defined
>>   
>> Yea, I thought, that angel is the only one, that has active toolbar 
> buttons, if you install the plugin. So it can be used "out of the box". 
> Mainly to modify paragraph styling. 
>

> All the other toolbar buttons can be enabled using the ControlPanel and 
> the Plugin Settings / Plugin Readme page.
>

Yes, but apart from naming the two that respond to \n\n would it make sense 
to give some default customisations for the additional characters so the 
work out of the box, many users may then simply select from an existing 
character, perhaps add a class we provide and that is the end of the story 
for them. No need to revert to customisations. This may allow instructions 
to be shared without having to present bespoke customisations except for 
those keen to extend the power;

Example (just a brainstorm) may be inaccurate as I learn still to memorise 
the existing, its just the concept. I am still to learn how some simple 
defaults will lend them self to each character. But publishing firs as just 
a larger set of symbols and no defaults my b fine with a view to giving 
them some defaults as we lean more about the scope and opportunities.

   -  ° degree use for emphasis 
   -  ´ to introduce styles
   -  › dividers lines/headings 
   -  _ specials including html 
   -  » Formatting blocks
   -  ≈ indicating state


>>- But the "special" chars do nothing visual "out of the box" other 
>>   than covering 1 line of text into a "div" with no styling. Similar to 
>> » 
>>   which starts to create a difference, if you use 2 of them »» .. 
>>
>>  And this is what I question, perhaps we do craft some default 
behaviours, because many users may be happy with the "Out of the box" only.

>
>>- Perhaps for shortcuts you could suggest in the doco the user may 
>>select alternatives that map to a similar character on their keyboard 
>>layout eg alt-' for tick alt-. for its shift > value for angle etc...
>>
>> I think editor keyboard shortcuts need a button, per shortcut. ... Is 
> there some info at tiddlywiki.com how to create buttons and shortcuts. .. 
> I'm not keen to create it. 
>

Me neither, was doing it recently for myself, I have to return to that, but 
It was becoming a night mare. However I need to so perhaps this is my Job 
then.

But - all I am saying is to* add to the documentation* that users can go to 
the definitions at Control Panel > Keyboard Shortcuts and select 
alternatives that map to a similar character on their keyboard layout eg 
alt-' for tick alt-. for its shift > value for angle etc.. (no more or less)

*Wiki text integrations*
>> By the way, this is so cool, and possibly replaces the need for custom 
>> macros in many cases. meaning once you know how to use is not need to write 
>> the macro solution when you can use a custom wikitext marker
>>
>>- This area will take sometime to explore; here is a quick test of 
>>mine, how would we go about forcing a line feed or using a template?
>>
>> \customize tick="listtagging" _element="$list"  filter=
>> "[tag]" 
>> ´listtagging
>>
>> \customize tick="listtagging" _element="$list"  filter=
>> "[tag]" template="$:/core/ui/ListItemTemplate2"
>> ´listtagging
>> This works with a break after the link widget in the template
>>
>> \customize tick="listprefixed" _element="$list"  filter=
>> "[all[]prefix]" template="$:/core/ui/ListItemTemplate2"
>> ´listprefixed
>>
>>
> Yea, that's really cool. .. I want to have the copy-to-clipboard widget, 
> that can be customized. ... the existing solution is a TW docs-macro. .. 
> And we can't call macros. .. So I'll create a new widget. .. Not sure, if 
> Jeremy will merge it. 
>

There is the "WidgetMessage: tm-copy-to-clipboard", but it is only an 
action widget. Would it be more productive to feed the message (or action 
tiddler title) into a button?
*I will experiment on that.*

 

>  
>
>>
>> Questions
>>
>>- Do you want a continued search for appropriate uni-code characters 
>>or are you happy with the available ones?
>>
>> I would be happy to get new ones. .. At the moment I'm happy with the 
> existing situation. We have 4 + 2. 4 that stop at \n and 2 that use \n\n
>

OK
 

>
> We will see, how the community reacts. It's basically a "keyboard layout" 
> problem. I think only 1 character has to work, to use the full potential. 
>

I agree, but the value of more than one, Is why I proposed some

[twdev] Re: Poll-Time for fetching Tiddler-List not *dynamically* configurable

[PMario]

On Friday, September 18, 2020 at 1:06:23 PM UTC+2, Mirko Richter wrote:

Can the intervall be made Tiddler-Configured with respect to the current 
> wiki-state?
>

I think it would be possible. .. But what do you mean by "current 
wiki-state"

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/532a5a40-8836-40ac-9510-95f69340cf52o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 4:21:21 AM UTC+2, TonyM wrote:

As I said before, I love the "details" example of yours. However I just 
> wanted to let you know, I do not resonate with you use of multiple hyphens 
> -- and --- etc, perhaps because of my eye-site or the difficulty matching 
> or remembering how many to do what. This example with the existing system 
> is a little better for me;
>
> \customize tick="d" _element="details" _params=
> ".notop.cbox.cbox-primary.hard-linebreaks" _endString="/d" _mode=block 
> open  
> \customize tick="s" _element="summary" _params=".margin-init"
>
> ´d ´s Details - Summary /s
> line 1
> line 2
> /d
> So I am quite happy with the "out of the box" solution.
>

That's fine. You can use it that way. I'll add some more information, that 
the _endString is "just a convention" (In this case my convention). But 
everyone can develop their own thing. 
 

> However this prompts me to ask, if for block custom wikitext, that could 
> we automate the end string if desired? eg wrap something in 
> ´d details here ´/d
>

tick automatically defaults to end of line. So you can skip it, if there is 
only 1 line like your example
 

> ´d 
> line 1
> line 2
> ´/d
>
> Where the ´/d or /d
>

This can be done. You only need to configure it that way. 
 

>
>- is the default end-string unless one is provided
>
> yes. 4 + 2 ... 4 elements use \n and 2 elements use \n\n by default. 

>
>- and of course all "Symbol/anything" are only possible end strings 
>
> It has to be a unicode character. So it basically depends on the OS and 
the installed unicode fonts, what's possible. 
 

> I expect this details and similar incantations are going to give us 
> something many have called for, for a long time, easy sliders and toggled 
> content. This also helps with Q&A quizzes, tests etc...
>

Yes. .. I was thinking about a "details widget", that can store the state. 

There may be some CSS eg: for printing, that makes all the details open by 
default ... or something similar. 
 

>
> Question;
> In the following case where I define a "More Details"
> \customize tick="md" _element="details" _params=
> ".notop.cbox.cbox-primary.hard-linebreaks" _endString="/md" _mode=block  
> \customize tick="m" _element="summary" _params=".margin-init"
>
> ´md ´m
> line 1
> line 2
> /md
>
>- Is there a way the tick="m" provides its own content eg more...
>
> Use: 

´md ´m more ...
 

>
>- Or could we even hide the ´m in the ´md definition? ie define the 
>summary in the more details since it is
>
>
>- a default?
>
> If you use this: 

´md 
line 1
line 2
/md

The browser will use a "default" summary.* It's a _browser_ thing*. So I do 
nothing here. 

-mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/6f0ff74b-4a6c-4653-9459-711acda53cfao%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[TonyM]

Mario,

*Like Tail winds says;*
*Most CSS frameworks do too much. They come with all sorts of predesigned 
components like buttons, cards, and alerts that might help you move quickly 
at first, but cause more pain than they cure when it comes time to make 
your site stand out with a custom design.*


   - I suppose what I think we need  is an even simpler set for the author 
   of the content in a tiddler, leveraging CSS for layout and formatting 
   within that space. All more easily implemented via the customised wikitext. 
   No need to stray into designer territory since that is handled already. I 
   best do a little research.



   - Yes I do "..want a "clone / duplicate selection" button? "
   But I can create it. Just noting its value along side customised wikitext


I observe - No Quote or code button in the new Groups!


   - I am expecting your link changes etc...
   - Custom Markup  sounds good 
   

Regards
Tony


   - 
   
On Friday, 18 September 2020 at 19:39:04 UTC+10 PMario wrote:

> On Friday, September 18, 2020 at 11:24:01 AM UTC+2, PMario wrote:
>
>
>>>- Perhaps the short form of color boxes ".cbox-primary" should be 
>>>cbp cbs etc... this leaves .cb available for simple color Blue
>>>
>>> OK .. I'll make them .cb .. for the box definition and .cbX for the 
>> color definitions.
>>
>
> I just found out that I used:  .c, cbox ... cb isn't used. .. So you can 
> use it for color Blue. .. but as I wrote you are not specific enough 
>
> IMO it needs to be 
>
> .bg-b  .. background blue
> .fg-b  .. text color blue and so on. 
>
> There is no standard yet. ... So we may have a look at "short" but 
> specific shortcuts. ... May be: https://tailwindcss.com/ will give us 
> some hints. The idea behind the mechanism is the same. 
>
> So I'll change nothing atm.
> -mario
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/92b52e67-f164-4b15-a17c-5579f39e55bbn%40googlegroups.com.

[twdev] Poll-Time for fetching Tiddler-List not *dynamically* configurable

[Mirko Richter]

Hi,

for my project i'd like to change the Poll-Intervall for calls to the 
server-side "tiddlers.json" dynamically. Currently it is initialized in $:/
core/modules/syncer.js either from the options-Param or via the hardcoded 
field Syncer.prototype.pollTimerInterval within this same tiddler. 
The pollTimerIntervall is than used whenever the next intervall is set 
(also in this file) via the follwing code:

triggerNextSync = function() { self.pollTimerId = setTimeout(function() { 
self.pollTimerId = null; self.syncFromServer.call(self); 
},self.pollTimerInterval); }; 

Can the intervall be made Tiddler-Configured with respect to the current 
wiki-state?

Thanks,
Mirko

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/9cec1a10-5141-4209-b98e-740cbdbc3df8o%40googlegroups.com.

[twdev] Filter of TiddlyWebAdaptor hardcoded

[Mirko Richter]

Hi,

for my current TW5-project i need to make the Filter of the TiddlyWebAdaptor 
configurable whe fetching the Tiddler-List from the server. As far as i can 
see, the method TiddlyWebAdaptor.prototype.getSkinnyTiddlers is the one 
that triggers that call but has a hard-coded Filter set. Can that filter be 
made "Tiddler-Configurable"? 

Thx in advance,
Mirko

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/88d1b0d3-3cc3-4fa5-b47d-067b6a6c1261o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 3:40:10 AM UTC+2, TonyM wrote:

In the process of us developing this solution I see the value in the use of 
> templates, but this makes me baulk, because the standard naming needs to be 
> a system tiddler, then as a result it needs another prefix such as in my 
> last example 
> $:/core/ui/ListItemTemplate2 we want to hide these so we are forced to 
> use $:/
>

You can use a field name: my-field: template for $:/xxx

\customize template={{{[my-field[template]]}}} should give you the right 
tiddler name

I didn't test it, but I think it should owrk. 
-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/224f1307-6bfa-4342-9e07-fe880a333e5bo%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

I'll give it an   OT - marker. 
But it is slightly related. 

You are right. "readable" wikitext shouldn't contain the $:/xxx/yyy/ 
namespace. 

I was already thinking about the possibility to use my uni-link plugin 
with the custom-markup 
plugin. 

At the moment unilink allows you to give every tiddler an "aliases" field, 
which can contain several aliases. 
At the moment it will _not_ use "shadow" tiddlers for speed reasons. We 
know, that no core shadows use aliases atm. This would need to be changed. 

[[aliasName|?]] will create a link to any tiddler including system 
tiddlers. 

[[AliAsNaMe|?]] is _not_ case sensitive, this gives the user the 
possibility to nicely use it in prose text. eg: At the start of the line. 

[[aliasName|?c]] will show the caption field as the link text. 
[[aliasName|?myField]] can use any field. 

--

The right sidebar More: Aliases tab gives an overview about used aliases. 

The plugin comes with 2 new toolbars to improve usability of aliases. 

There are some filter functions for alias-backlinks ... and so on. 

IMO . It should be possible to use \importcustom [[alias|?]] ... BUT I'm 
not sure if this is an advantage already. 

---

I was hesitating to allow [[alias|?{]]  or something similar as a 
representation for {{real tiddler name}}

The only reason to do that, would be the "backlinks" mechanism would work 
for these links. 

just some thoughts.

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/f6eb5a6f-f3ff-4ef3-abf2-8e7d26c48225o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 12:16:03 PM UTC+2, PMario wrote:

At the moment the only way to influence the parser is \importcustom per 
> tiddler and per macro. BE AWARE
>
> \define x()
> \importcustom [[pragma-details]]
> °d °s Details - Summay
> ---
> line 1
> line 2
> --
> \end
>
> <>
>

I also don't see any advantage of the custom system here. It's only slowing 
things down. If you want to create macros, you should definitely use the 
existing system only. 

It will avoid the introduction of 3rd party dependencies. 

just my thoughts
mario



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/216fff21-0f4b-4afa-b01f-fba73b5e7d1co%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 3:20:37 AM UTC+2, TonyM wrote:
...

> View on top of V4.1
>
>- I think you could delegate the historical methods to a link rather 
>than have them complicate the documentation from the beginning. How to 
>style a Paragraph 
>
> 
> Misusing standard wikitext to indent a paragraph 
>
> 
>. 
>
> That will be a ToDo, since we will need to improve the TW doc quite a bit, 
so we can link to it. The existing docs 

 
for specific styling imo needs some love
 

>
>- Will there be some smart defaults for each special Characters out of 
>the box, so unless they are inadequate they serve a purpose right away?
>   - angel is already somewhat defined
>   
> Yea, I thought, that angel is the only one, that has active toolbar 
buttons, if you install the plugin. So it can be used "out of the box". 
Mainly to modify paragraph styling. 

All the other toolbar buttons can be enabled using the ControlPanel and the 
Plugin Settings / Plugin Readme page.

>
>- 
>   - If so a list of special Characters and their default 
>   functionality up front and an explanation of the buttons would be 
> enough to 
>   get started. Including the name used in the customise pragma eg degree, 
>   perhaps the official character names would also help some.
>
> https://wikilabs.github.io/editions/tick-text/#Custom%20Markup%20Definition 
has the names.

But the "special" chars do nothing visual "out of the box" other than 
covering 1 line of text into a "div" with no styling. Similar to » which 
starts to create a difference, if you use 2 of them »» .. 


>- Perhaps for shortcuts you could suggest in the doco the user may 
>select alternatives that map to a similar character on their keyboard 
>layout eg alt-' for tick alt-. for its shift > value for angle etc...
>
> I think editor keyboard shortcuts need a button, per shortcut. ... Is 
there some info at tiddlywiki.com how to create buttons and shortcuts. .. 
I'm not keen to create it. 
 

>
>- "markup for advanced users", yet to be written could be "use 
>focused" (initially) rather than technically the current solution eg
>- Introducing html tags into you own markup
>   - Using classes to rapidly style your content with css
>   - Using the end string or \n or \n\n to terminate your custom markup
>   - It may also provide one or more "libraries" of css that can be 
>   activated. In future you could add effective ones, developed in the 
>   community (like mine :)
>  - When ever a solution enables the accumulation of techniques 
>  and methods it improves over time.
>   - Perhaps in 
>
> https://wikilabs.github.io/editions/tick-text/#Custom%20Markup%20Definition 
>explain why the parameters begin with an underscore, this helps 
>understanding and remembering the fact.
>
> OK will go to ToDos
 

> *Wiki text integrations*
> By the way, this is so cool, and possibly replaces the need for custom 
> macros in many cases. meaning once you know how to use is not need to write 
> the macro solution when you can use a custom wikitext marker
>
>- This area will take sometime to explore; here is a quick test of 
>mine, how would we go about forcing a line feed or using a template?
>
> \customize tick="listtagging" _element="$list"  filter=
> "[tag]" 
> ´listtagging
>
> \customize tick="listtagging" _element="$list"  filter=
> "[tag]" template="$:/core/ui/ListItemTemplate2"
> ´listtagging
> This works with a break after the link widget in the template
>
> \customize tick="listprefixed" _element="$list"  filter=
> "[all[]prefix]" template="$:/core/ui/ListItemTemplate2"
> ´listprefixed
>
>
Yea, that's really cool. .. I want to have the copy-to-clipboard widget, 
that can be customized. ... the existing solution is a TW docs-macro. .. 
And we can't call macros. .. So I'll create a new widget. .. Not sure, if 
Jeremy will merge it. 
 

>
> Questions
>
>- Do you want a continued search for appropriate uni-code characters 
>or are you happy with the available ones?
>
> I would be happy to get new ones. .. At the moment I'm happy with the 
existing situation. We have 4 + 2. 4 that stop at \n and 2 that use \n\n

We will see, how the community reacts. It's basically a "keyboard layout" 
problem. I think only 1 character has to work, to use the full potential. 


>- As in the examples above *Wiki text integrations* how do I make 
>these useful options global?
>   - I am confident I will want to push examples like ´listprefixed into 
>   view templates and macros so I must test the

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 2:34:16 AM UTC+2, TonyM wrote:

I have to download your new versions so I can save changes. Then you 
> release another. Could you add the local storage plugin (not enabled) so I 
> can activate it install other plugins is needed? I will export local 
> storage, then clear local storage and reload when you release a new version 
> and selectivity restore my working tiddlers? 
>

I'll use my release setup from now on. So the plugin will get new version 
numbers. Only if the plugin changes.
The TW importer can be used to import new plugin versions. 

The edition (docs) will have its own versioning.

I'll need to rename the plugin from Tick Paragraph to *Custom Markup*
The edition will be *custom-markup* too .. So the URL will change. .. 
 
-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/8fe04399-3733-4ee2-9c26-83551034e55bo%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 11:24:01 AM UTC+2, PMario wrote:


>>- Perhaps the short form of color boxes ".cbox-primary" should be cbp 
>>cbs etc... this leaves .cb available for simple color Blue
>>
>> OK .. I'll make them .cb .. for the box definition and .cbX for the color 
> definitions.
>

I just found out that I used:  .c, cbox ... cb isn't used. .. So you can 
use it for color Blue. .. but as I wrote you are not specific enough 

IMO it needs to be 

.bg-b  .. background blue
.fg-b  .. text color blue and so on. 

There is no standard yet. ... So we may have a look at "short" but specific 
shortcuts. ... May be: https://tailwindcss.com/ will give us some hints. 
The idea behind the mechanism is the same. 

So I'll change nothing atm.
-mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/962e3513-7e94-4a20-aa27-3a07a445713bo%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 2:28:28 AM UTC+2, TonyM wrote:

Related notes
>
>- An interesting observation is if you select and copy a *rendered 
>tiddlers text* and paste it into a new tiddler, the result really 
>needs this custom formatting help.
>
> I think this could be done with the TW drag&drop mechanism. ... That's a 
TW feature request. 


> Questions arising?
>
>- There is a large set of html color names, I wonder if there were a 
>way to pass these into a text or background colour via this mechanism?
>   - one example "°.class#green This is green text "
>   - This would avoid needing to code a set of foreground and 
>   background colour specified classes
>
> The problem is, that °.class#green isn't specific enough if you want the 
text color, text background, image color or image background

So the way to go is °.X  where X is defined in a CSS tiddler and exactly 
defines, what should be done. 

The "customize parser" is already overloaded. It's probably the "biggest" 
parser element in TW already. .. IMO it is already a bit "feature 
overloaded"

 

> Incidental ideas.
>
>- The ability to select some text and have it duplicated. in place 
>with an editor toolbar could be useful in general
>   - However it would also help if one wanted to add another special 
>   character, just highlight it and hit the button to add another as well.
>   - A matching duplicate line / selection / block as well would help.
>
> You want a "clone / duplicate selection" button?

-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/62c09e1a-2482-48a9-87ea-79390dd4f760o%40googlegroups.com.

[twdev] Re: Custom markup (continued 2)

[PMario]

On Friday, September 18, 2020 at 2:28:28 AM UTC+2, TonyM wrote:
[...]

>
>- I notice if I have the cursor anywhere in a line and apply the ID it 
>works however the cursor jumps to the end of the line
>   - If the cursor could remain where was, or perhaps be placed just 
>   after the symbol I could then type a .class or something, but this way 
> all 
>   I save is hitting the end key.
>
> I'll have a look, if there are functions in the core, that allow us to set 
cursor position. 
 

>
>- Perhaps the short form of color boxes ".cbox-primary" should be cbp 
>cbs etc... this leaves .cb available for simple color Blue
>
> OK .. I'll make them .cb .. for the box definition and .cbX for the color 
definitions.

>
>- Perhaps a little padding could be added to each box definition 
>"padding: 4px;"
>
> The idea is to have .cb for padding, margin and so on. .cbX is color only. 
.. So if you need a new xb you should define one. The "box padding" is 
already very big for my personal taste. 

We may be able to use CSS variables, to make settings more dynamic. ... 
We'll see. @Mat is the CSS variable voodoo master?
 

>
>- I see value retaining the following styles working especially if the 
>.i.i.i and .r.r.r do not work (why?)
>
> The browser doesn't do it that way.  is the same as 

>- .i { margin-left: 2.65em; }
>.ii { margin-left: 5.3em; }
>.iii { margin-left: 7.95em; }
>.r { margin-right: 2.65em; }
>.rr { margin-right: 5.3em; }
>.rrr { margin-right: 7.95em; }
>
> I'll add the RRRs ... but I personally would only use the .r .. 
.r and .-i .. is the same thing

-mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/6bacf4cc-a946-4c9d-a02a-2f1c3af84adao%40googlegroups.com.