Annoyingly I can't "reply privately to author" anymore so must post this publicly:@PMario - could you edit the first post in this thread to include the main link you recommend for testing things?Tx<:-)
On Wednesday, September 16, 2020 at 12:22:05 PM UTC+2 PMario wrote:
Hi folks,This is the continuation of Custom markup [1] and Custom markup (continued) [2]Let's start a new one before [2] starts to use pagination.Have a closer look at link [1] it's possible to show all the topics in 1 page
have fun!mario
Revert to "Classic" (on Desktop). This will also let you complain to Google as it will ask you why you are reverting ...
\customize tick="listtagging" _element="$list" filter="[tag<currentTiddler>]"
´listtagging
\customize tick="listtagging" _element="$list" filter="[tag<currentTiddler>]" template="$:/core/ui/ListItemTemplate2"
´listtagging
\customize tick="listprefixed" _element="$list" filter="[all[]prefix<currentTiddler>]" template="$:/core/ui/ListItemTemplate2"
´listprefixed
\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
´d details here ´/d
or
´d
line 1
line 2
´/d
\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
- 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.
- Perhaps the short form of color boxes ".cbox-primary" should be cbp cbs etc... this leaves .cb available for simple color Blue
- Perhaps a little padding could be added to each box definition "padding: 4px;"
- I see value retaining the following styles working especially if the .i.i.i and .r.r.r do not work (why?)
- .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; }
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.
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
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.
- 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 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?
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.
- 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
- 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.
- 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...
- "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.
Wiki text integrationsBy 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<currentTiddler>]"
´listtagging
\customize tick="listtagging" _element="$list" filter="[tag<currentTiddler>]" template="$:/core/ui/ListItemTemplate2"
´listtaggingThis works with a break after the link widget in the template
\customize tick="listprefixed" _element="$list" filter="[all[]prefix<currentTiddler>]" template="$:/core/ui/ListItemTemplate2"
´listprefixed
Questions
- Do you want a continued search for appropriate uni-code characters or are you happy with the available ones?
- 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 these. Do you foresee any problems?
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
<<x>>
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 $:/
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
/dSo I am quite happy with the "out of the box" solution.
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
´d
line 1
line 2
´/dWhere the ´/d or /d
- is the default end-string unless one is provided
- and of course all "Symbol/anything" are only possible end strings
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...
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...
- Or could we even hide the ´m in the ´md definition? ie define the summary in the more details since it is
- a default?
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.
- 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.
Wiki text integrationsBy 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<currentTiddler>]"
´listtagging
\customize tick="listtagging" _element="$list" filter="[tag<currentTiddler>]" template="$:/core/ui/ListItemTemplate2"
´listtaggingThis works with a break after the link widget in the template
\customize tick="listprefixed" _element="$list" filter="[all[]prefix<currentTiddler>]" template="$:/core/ui/ListItemTemplate2"
´listprefixedYea, 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 these. Do you foresee any problems?
At the moment I personally would _not_ use this in TW ViewTemplate or tiddlers tagged with $:/tags/ViewTemplate .. it's too dangerous to "brick" the system.
These answers of yours really are demonstrating the flexibility. We need some how to capture this knowledge, without making it too complex for
users.
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
<$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 </$clipboard>
just brainstorming
-m
In the new Google Groups I can edit an existing post :( againAdditional ContentIn 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 contentAgain,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.
The Usage string is: ° » ´ › - -- --- ----
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"
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
Mario, Et al.More review and research into the extensibility on top of Version 0.4.1I 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 itemsanotherHowever 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.
- Such as customising something so it occurs until the end of line only, or until a blank line "\n\n" only
- 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
- Then I want to find how to apply things inline, like in a middle of a sentence.
- 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.
I had an example Use Case to show but things changed so much in your tool I'm revising it. Hopefully I have time soon.
I note your comment on buttons. Right.I also read the detail on discussion of using it for macros. I'm slightly nervous about that.The GAINS on HTML insertion and CSS styling are very substantial. I would not want handling macros to confuse the basic need to expand easy invoke of HTML & CSS.
I do have issues with INLINE markup (°) in that there is no way to nest at the moment. It is also "verbose" having to do °°match°°.
@TiddlyTweeter wrote:I do have issues with INLINE markup (°) in that there is no way to nest at the moment. It is also "verbose" having to do °°match°°.
Yea, Inline needs more love. It's the basic function only. similar to @@match@@ So we don't win anything yet.
There is the _need_ to have a uniquely identifiable endstring. So the \customizeinline will need an _endString param to make nesting possible.
I expect it is too late in the rendering process; but it seems common sense (does not mean it is) that some pragma could read as such;°☐ "This is a todo line"
and thus call the macroIn this case I am accepting if I wanted to pass other parameters to the macro the first, the content needs to be quoted.Eg°☐ "This is a todo line" color:"blue"
The macro(s) just for completeness\define done-check(tiddlername)\whitespace trim<$set name=tiddlername value="""$tiddlername$""" emptyValue=<<currentTiddler>> ><$list filter="[<tiddlername>!done[yes]!done[cancel]]"><$button tooltip="click to indicate done" class="tc-btn-invisible">
[...]
<$set name=todo-tiddler value="""$:/todo/$(currentTiddler)$/$content$""">
I also read the detail on discussion of using it for macros. I'm slightly nervous about that.The GAINS on HTML insertion and CSS styling are very substantial. I would not want handling macros to confuse the basic need to expand easy invoke of HTML & CSS.
The more I hear about "macros" in this the worse I feel.
I don't care if the device lets you skip over the moon. I DO care that mortals can understand it. OR totally avoid it.
IMO "macro use" within this tool is a highly advanced feature. I am very UNCLEAR of the added value.
I need examples to see the added value!!!
The checklist example TonyM gave I don't think adds anything that does not exist already.As PMario implied before, the Grossinger plugin IS using markup intelligently to deliver live.Dimmi (tell me) the added value, please!
<$presentation> <$slide>Welcome to ''Reveal.js''</$slide> <$slide>Embedded inside TiddlyWiki</$slide> <$slide> <$slide>Vertical Slides</$slide> <$slide>Can also me manged with one level of nesting</$slide> </$slide>
<$slide>End!</$slide>
</$presentation>
<$slide>Have fun!</$slide>
I think it depends on the users taste, what they like more
-mario
@TiddlyTweeter wrote:The more I hear about "macros" in this the worse I feel.Why? ... It works now, which is a big win.
BUT are we seeing a version of Advanced Yoga (bloke was able to twist his leg behind his head)?
My concern is it will confuse adding macros. Let's see.
The issue is you will have to find a way to document BOTH major layout change AND the indefinable scope of macros (not all though) elegantly.I'm concerned its getting too complicated. BUT let us see.
For the minute a macro seems the best.
I'm unfortunately swamped with work, thus my absence here. Sorry for that.
I have to go through several books and in doing so I take out notes and quotes. I want to refer to these snips by the page they can be found at. It is common practice to refer to a page using the abbreviation "p." or "pp." (not sure what pp stands for?).
»note ´page [[book]] 1-5your comment!
------
The content of "customOrderedList" is a bit tricky but that's not, what the user has to see:
\customize degree="orderedList" _element="$macrocall" $name="list-links" type="ol" class="iNeedIt" emptyMessage="Nothing found!" _srcName=filter
\customize degree="orderedList" /* MAIN framework, project 9 */
_element="$macrocall" $name="list-links" type="ol" class="iNeedIt" emptyMessage="Nothing found!" _srcName=filter
\customize degree="orderedList" _element="$macrocall" $name="list-links" type="ol"
class="-v-p9" // NOTE project 9 must have this
emptyMessage="Nothing found!" _srcName=filter
\customize angel="note" _element="div" _params=".note.notop.cbox.cbox-primary.hard-linebreaks" open _mode=block _endString="------"\customize tick="page" _params=".margin-init.page"
»note ´page [[book]] 30-5
So, if the CSS is defined elsewhere, do I understand it right that the user has to insert the following bit in every tiddler that he wants to make such styled notes in?
For real world I think this needs to be a template of some kind.
E.g any tiddler tagged "book" has this automatically applied, i.e triggered via someting intuitive that the user probably already does (e.g tag). It is unrealistic to think that a user would manually add this even via a stamp unless he is totally into it and working with a dedicated book-note-taking wiki. The wiki user who occasionally wants to make a "book notes tiddler" would otherwise need to dig this out, which it just unlikely IMO. Or do I misunderstand something?
»note ´page [[book]] 30-5How is the above to be interpreted?
Style it with "note", yes, but then there's also "page" style? But [[book]] 30-5 are "headlines" seen in the text, right?
\customize tick=address _element="$vars" address="N Blah St Randwick" name="Anthony Muscio" phone="612 4075581847" email="to...@virtual.com"
´address Here we use <<name>> <<phone>> <<address>>
´address Here we use <<name>><br>Phone: <<phone>><br><<address>>
\customize tick=debug _element="$list" filter="[all[current]has:field[debug]]"
\customize tick=design _element="$list" filter="[{$:/config/design-mode}match[yes]]"
\customize tick=draft _element="$list" filter="[all[current]has:field[draft.of]]"
´debug Debug: in <<currentTiddler>><br>Transclusion=<<transclusion>>
´design Show only when global design mode is set. to yes
´draft `Show only when Tiddler is in draft mode`
\customize tick=toc _element="$list" filter="[tag[toc]]"
´toc <<currentTiddler>><br>
´toc <$link/><br>
´toc <$transclude/><br>
\customize tick=toc _element="$list" filter="[tag[toc]]"
´toc <$text text={{{ [all[current]match[Basics]then[Matches Basics]] }}}/><br>
´toc <$text text={{{ [all[current]match<storyTiddler>then[In TOC list]else[]trim[]] }}}/>
Hi folks,This is the continuation of Custom markup [1] and Custom markup (continued) [2]Let's start a new one before [2] starts to use pagination.Have a closer look at link [1] it's possible to show all the topics in 1 pageV 0.4.0 https://wikilabs.github.io/editions/tick-textstarting with V 0.5.1 https://wikilabs.github.io/editions/custom-markup/ the above link won't work anymore!have fun!mario
\customize tick=system-shadows _element="$list" filter="[all[shadows]is[system]]"
´system-shadows <$list filter="[all[current]has[caption]] +[!is[blank]]">{{!!title}} {{!!caption}}<br></$list>
'customers `country `state {{{ [all[current]size[large]] }}} Automatic end string for each on \n?
\customize tick=all-tiddlers _element="$list" filter="[is[tiddler]!is[system]]" template="$:/core/ui/ListItemTemplate"
´all-tiddlers This does nothing so can describe it
\customize tick=all-customers _element="$list" filter="[is[tiddler]!is[system]object-type[customer]!archive[yes]]" template="(customer-record)"
´all-customers List all customer-records
Hi folks,\customize tick=tagging _element="$list" filter="[tag<currentTiddler>]"
On Wednesday, 16 September 2020 20:22:05 UTC+10, PMario wrote:Hi folks,
A little experimental fun;
This method uses the vars widget to pre-define a set of variables for use inside the custom markup. As in this examples we have all out standard address details using well known names. You choose which to use and how to arrange them. Of course the variable are only available inside the vars
\customize tick=address _element="$vars" address="N Blah St Randwick" name="Anthony Muscio" phone="612 4075581847" email="to...@virtual.com"
´address Here we use <<name>> <<phone>> <<address>>
´address Here we use <<name>><br>Phone: <<phone>><br><<address>>
The following shows how the list widget with a pre-set filter can be used to choose if the content is to be displayed or not, emptyMessage can be used as well.
\customize tick=debug _element="$list" filter="[all[current]has:field[debug]]"
\customize tick=design _element="$list" filter="[{$:/config/design-mode}match[yes]]"
\customize tick=draft _element="$list" filter="[all[current]has:field[draft.of]]"
´debug Debug: in <<currentTiddler>><br>Transclusion=<<transclusion>>
´design Show only when global design mode is set. to yes
´draft `Show only when Tiddler is in draft mode`
This also triggers me to ask Mario
- How do I get a new line, but not double, newline to be used in the result(s)?
- Was it a specific Character?
- Would it be costly to have an alias to \customize of \customise? For me this is a common error.
As expressed earlier, I would so love to pass the filter to a customized list definition.Here we simply use list to access a canned list of tiddlers defined by a filter
\customize tick=toc _element="$list" filter="[tag[toc]]"
´toc <<currentTiddler>><br>
´toc <$link/><br>
´toc <$transclude/><br>Notice how common wiki text is all you need that refers to currentTiddler?
- Empty message can also be used in the customise.
In this case you can test is the current tiddler, or a named tiddler is a member of the canned filter
\customize tick=toc _element="$list" filter="[tag[toc]]"
´toc <$text text={{{ [all[current]match[Basics]then[Matches Basics]] }}}/><br>
´toc <$text text={{{ [all[current]match<storyTiddler>then[In TOC list]else[]trim[]] }}}/>- however this second one produces empty lines.
This example not only shows that the customise pragma can be used to store a canned filter for reuse, but also shows how the first in a nested list can be concealed behind a helpful name like system-shadows
\customize tick=system-shadows _element="$list" filter="[all[shadows]is[system]]"
´system-shadows <$list filter="[all[current]has[caption]] +[!is[blank]]">{{!!title}} {{!!caption}}<br></$list>
I am confident with Mario's nesting method a simple line could define a set of nested lists with the content of the line equal to each final record.If named well the variable set for each nested level will make the wiki text look like some 4th Generation reporting languages.
But in this example I think the last filter here, on the line, needs to be in a list because otherwise it generates unnecessary line breaks
'customers `country `state {{{ [all[current]size[large]] }}} Automatic end string for each on \n?
This is approaching simpler than SQL
- Of course if somehow we can pass the filter to each nested level, not only would canned filters be used.
- However if one has structured data in a wiki it would be simple to create the set of canned filters for handling the structured content in the wiki.
- For users of a wiki (rather than owner designers) it may be simple to provide them the info they need to generate any list or report
- Especially with some useful templates.
In the following case we use a list template
\customize tick=all-tiddlers _element="$list" filter="[is[tiddler]!is[system]]" template="$:/core/ui/ListItemTemplate"
´all-tiddlers This does nothing so can describe itThis is another case where passing the template value may be helpful
I am working on a better way to name templates/transclusions so the above could read
\customize tick=all-customers _element="$list" filter="[is[tiddler]!is[system]object-type[customer]!archive[yes]]" template="(customer-record)"
´all-customers List all customer-records
By the way, If the List widget was to contain two new parameters before and after, that could provide header and footer content, Only if there were content, this would expand further, allowing content and or table headers. I miss foreachtiddler still :(
\customize tick=children _element="$list" filter="[parent<currentTiddler>]"And the last one children has set me of on a one and many to many relationship solution* now that what TocP is no longer magical to me :)
Hi folks,
Especially the use of srcDo I understand correctly the _srcName=filter effectively says, assign the value found in the line, to the parameter filter, in this case that is in the list?
I think you suggested this before, but our use of widgets is limited by those who do not honour the close part of <$wiggetname params>content</$wiggetname> rule
A case in point is the <$count widget, as it can only be closed with /> not </$count>
Going forward
- Perhaps we should raise this as a fix, for each widget we find, just to get the consistency we need that all widgets to allow the full close
- I do not think you should cater for this because it could compromise nesting (a guess)
Every widget that is used "self closing" like <$count /> there should be _no_ problem. They should all work. _And with the _srcName you have one parameter, that can be defined in the "user line"..
Count: `<$count filter="[prefix[$:/state]]"/>` works
Count: `<$count filter="[prefix[$:/state]]"</$count>` does not
As written with the _srcName parameter, there should be almost no limit in using any widget. ... except may be the <$button widget, if you want more than 1 parameter from the line.
\customize tick=style _element="style"
´style .mystyle { border: 1px solid green; border-style: dotted; }
;.mystyle Content
;Perhaps also;
´style {{myStyleSheet}}
However, without customisations
Count: `<$count filter="[prefix[$:/state]]"/>` works
Count: `<$count filter="[prefix[$:/state]]"</$count>` does not
`<$count filter="[prefix[$:/state]]"></$count>`
So I think this observation still stands.Since customise will generate </$count> It will not work
I do not know how to identify others without exhaustive testing or reading (understanding) widget definition code.
As written with the _srcName parameter, there should be almost no limit in using any widget. ... except may be the <$button widget, if you want more than 1 parameter from the line.
- Can I ask?, I have not test yet but is their any reason this would be limited to widgets?, because html could also make use of the content being applied to an attribute?
- Perhaps too much to ask if there were a way to pass SOME content into the src and other as usual treated as content.
- In a dreamy state you could imagine any key=value pair in the "content" being translated to attribute=value with every thing else placed in the body.
Here is another experiment that has WORKED!
\customize tick=style _element="style"´style .mystyle { border: 1px solid green; border-style: dotted; };.mystyle Content;Perhaps also;´style {{myStyleSheet}}so one could have a
There is a typo: you need to close the first widget element:`<$count filter="[prefix[$:/state]]"></$count>`
Not really. The string </$count> is like the _endString parameter for the standard TW parser. So it doesn't need to be created.
\customize tick=count-filter _element="$count" _srcName=filter
Count: <$count filter="[prefix[$:/state]]"/>
´count-filter [prefix[$:/tags/macros]]
- Can I ask?, I have not test yet but is their any reason this would be limited to widgets?, because html could also make use of the content being applied to an attribute?
Do you have any examples, that would need it. .. There is no special reason.
- Perhaps too much to ask if there were a way to pass SOME content into the src and other as usual treated as content.
- In a dreamy state you could imagine any key=value pair in the "content" being translated to attribute=value with every thing else placed in the body.
The problem is, that there is no way for the algorithm to know, if it is content, or if it is key:value as parameter.
Yea, but that is not best practice. It will hide a <style> element, which shouldn't be used except for examples... <style> will always win and if a user wants to do some CSS customisation, those elements are very hard to find.
navmainarticlesectionheaderfooter
But, as I work with it myself I sometimes struggle with the PERMUTATIONS possible.
My main wondering is WHO is it FOR, mainly?
</tagname> </$widgetname>
Unicode does provide many paired glyphs, albeit some are outside the UTF-16 range.See, for instance, some of them: https://www.compart.com/en/unicode/mirrored
To clarify my last point about TWO configs, nasty & irritating as the idea is :-(...I think it very LIKELY that PMario's Custom Markup system will be, eventually, widely used by AUTEURS (originating author geeks).
\customize degree=☐ _element="$macrocall" $name="xx"
\define xx(src)
<$checkbox tiddler=<<__src__>> tag=done class="db"> <<__src__>></$checkbox>
\end
°☐ This is a Test
°☐ This is a test 1
°☐:a This is a Test
°☐:b This is a test 1 .... or something similar
I am NOT convinced that a TW that uses that brilliant system should expose it to every user. I think it would be a support issue of scale to do so.
Can you PLEASE correct angel to angle. !!!!
Tony wanted the possibility to add more key=value _params. .. And I think it should be possible, in the _params section and calling it. eg:
°☐:a This is a Test
On Friday, September 25, 2020 at 12:13:08 PM UTC+2, @TiddlyTweeter wrote:Can you PLEASE correct angel to angle. !!!!I knew, that someone would have a problem. But for me this looks like an angel »|« , with some phantasy.
There are two issues in our context ...1 - does the end user need to see what the author used? My guess is that they don't.I mean we are doing this to make WRITING easier. But most READERS won't be writers so will never need to see the markup glyphs.
2 - font support is a very complex issue. It is extremely difficult to determine what glyphs are available visually universally (because of sophisticated OS substitutions). HOWEVER, I made the point that in many cases it is ONLY the author who needs to have them supported by a font.