[twdev] Re: Custom markup (continued 2)

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 >

[twdev] Re: Custom markup (continued 2)

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 >

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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 > >

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

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

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:

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

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

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

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

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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,

[twdev] Re: Custom markup (continued 2)

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 >

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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 > >

[twdev] Filter of TiddlyWebAdaptor hardcoded

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

[twdev] Re: Custom markup (continued 2)

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: > >

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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 > > <> >

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Re: Custom markup (continued 2)

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

[twdev] Dynamical exchangeable PageTemplate?

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

[twdev] Re: Custom markup (continued 2)

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.