Mario,
This idea is very powerful from a user perspective, but I have no idea how
achievable technically, please give it some thought.
- If feasible it only needs the development of one new customise feature
reference the content
- My thought is a variable such as currentContent, idealy
$(currentContent)$ because then it is easy to concatinate
- eg to="$:/prefix/$(currentContent)$"
- This also raised the desire to access other variables in the pragma
such as current tiddler / storyTiddler or any if possible.
I am experimenting with customise to try and toggle something.
- I realise that I would be useful if the content of the line could be
referenced in the "pragma"
Here is a simple example I have "fudged"
\customize degree="button" _element="$button" to="Content"
°button Content
°button A Todo item
I have set the to="Content" as if I could have the content of the line
passed into the pragma. This navigates to a tiddler named "Content" however
I would like the second "button" to navigate to " A Todo item"
Why?
I expect its obvious, The ability to create toggles and new buttons and a
lot more such as state tiddlers/data indexes and much more would be
possible by allowing the content of the line be a parameter to the
customised mark-up.
For me this started with a desire to construct custom mark-up such as
°do An item I may have to do, quickly typed into a tiddler
- Which could be used to generate a clickable item in the view template
to indicate complete
Other possibilities
- Click line
- to flag that line/paragraph for subsequent processing
- to create a tiddler by that title
- to places that text in a data tiddler with next nth key
- Turn text into a tag
- to copy line to keyboard
- Allowing footnotes to be created
- many more
Tony
On Friday, 18 September 2020 at 22:33:33 UTC+10 PMario wrote:
> 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/e9c3f61e-8904-4e92-aee9-5664296de445n%40googlegroups.com.
