Mario, Et al.
More review and research into the extensibility on top of Version 0.4.1
I just did this in a tiddler
\customize degree="button" _element="$button" mode="block"
\customize tick="kbd" _element="kbd"
°button Content
´kbd This is > [[A List]] > of items
another
However I am confused the content button has the kbd result wrapped onto
the same line but the word "other" seems to me to be more than one line
below.
This continues to be a stumbling block, I am trying to commit to memory how
to make use of the two cases \n and \n\n when customising.
1. Such as customising something so it occurs until the end of line
only, or until a blank line "\n\n" only
2. once I master this I need to work out how to have the result
generated on the current line, and in other cases to end with a blank line
3. Then I want to find how to apply things inline, like in a middle of a
sentence.
4. I am also well aware of the endString, but here I am looking for the
line based customisations without having to specify an endString.
Perhaps its the 24 hour break I had, or Sunday laziness, but it could also
be a lack of clarity either in the solution or in the documentation.
*Would it be possible for you to write a short clarifying summary of the
differences between these 4 items above please?*
- *It seems to me this is a key area of the documentation*
Thank in advance
Tony
On Sunday, 20 September 2020 at 09:12:12 UTC+10 TonyM wrote:
> 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/c69c4e56-6c9b-4035-a49d-5639a7a24475n%40googlegroups.com.
