[twdev] Re: Custom markup (continued 4)

[TonyM]

Do note I found these alternate small braces that may be better.
﹙₍ ₎﹚

Regards
Tony

On Saturday, 31 October 2020 12:01:43 UTC+11, TonyM wrote:
>
> Mario,
>
> I would be keen to see these additional inline glyphs made available. They 
> look like a fusion of [ ] and ( )
>
> It would be ideal for mark-up that involves links or buttons and where the 
> content is considered a title.
>
> *A line with〖 This inline 〗and more
>
>
>- They also look good when no customisation plugin is in use but does 
>communicate, if it were, this would be treated differently. 
>- I would for example use it like [[ ]] but to trigger a button to 
>create the tiddler from a template
>- Or 〖task This inline 〗to create from the task template
>- Its the more visible version TT is asking for.
>
> However I do want you to retain ﹙ little﹚ for the same reason TT does not 
> want them, they are similar but different to ( ) and less visible. 
>
>- TT can just "*not use them"* if he does not like them (I say with 
>all due respect).
>
>
> 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/fd88d292-d4a4-43ef-a974-34a8a1dc24e6o%40googlegroups.com.

[twdev] Re: Custom markup (continued 4)

[TonyM]

Mario,

I would be keen to see these additional inline glyphs made available. They 
look like a fusion of [ ] and ( )

It would be ideal for mark-up that involves links or buttons and where the 
content is considered a title.

*A line with〖 This inline 〗and more


   - They also look good when no customisation plugin is in use but does 
   communicate, if it were, this would be treated differently. 
   - I would for example use it like [[ ]] but to trigger a button to 
   create the tiddler from a template
   - Or 〖task This inline 〗to create from the task template
   - Its the more visible version TT is asking for.

However I do want you to retain ﹙ little﹚ for the same reason TT does not 
want them, they are similar but different to ( ) and less visible. 

   - TT can just "*not use them"* if he does not like them (I say with all 
   due respect).


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/7ae0fa0e-b0c5-43ab-a2db-3504c994155fo%40googlegroups.com.

[twdev] Re: Custom markup (continued 4)

[TonyM]

Question,

If other glyphs and characters could be selected could we actually redefine 
existing mark-up with customise?
\customise glyph="*" parameters

*This would then take on the new definition here?

I raise this because this us what the current double underscore is 
effectively doing.

An example I may use if this was possible is to add underline or bold to 
H1/H2

This would allow redefinition of mark-up already in a text perhaps even 
making it behave like another mark-up language.
and additions like
\customise glyph="-" _element="li"

- to accept bullets pasted from GitHub


Tones

-- 
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/0a8dce1e-9e25-40b2-b8bf-e7170b501f56o%40googlegroups.com.

[twdev] Re: Custom markup (continued 4)

[TonyM]

Mario,

Just for clarification the double underscore (not underscore) is used, does 
this not clash with its existing use?, or is this intentional?

It is available on most keyboards.

Regards
Tony


On Saturday, 31 October 2020 00:55:25 UTC+11, PMario wrote:
>
> Hi folks,
>
> I'd like to discuss with you the table syntax as shown in
>
> \customize tick=table _element=table _endString="/endTable" _mode=block
> \customize tick=caption _element=caption
>
> \customize tick=! _element=th 
>
> \customize tick=cell _element=td _classes=".hl"
> \customize tick _use=cell
>
> \customize angle="===row" _element=tr _mode=block _endString="---"
> \customize angle=cmulti _element=td _classes=".hl" _mode=block 
> \customize angle=| _use=cmulti
>
> ´table ´caption Some caption text
> »===row
> ´! header 1
> ´! header 2
> ´! header 3
> ---
> »===row
> »| 1 text 
>
> »| 12 text «  and  » 
>
> »|
> * cell 13 text
> * line 2 
> * line 3 
> ---
> »===row
> »| 2 text 
>
> »| 22 text 
>
> »| 23 text 
>
> ---
> /endTable
>
> and: https://wikilabs.github.io/editions/custom-markup/#test-dave-table
>
> Do you think it could be used as a default, shipped with the plugin. .. 
> The CSS for multiline and eg: bullet lists will need some adjustment .. 
>
> tick-cells are use for single line cells terminated by \n
> angle-cells are used for multi, block like cells terminated by \n\n
>
> »===row
>ends with 
> ---
>
> -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/ad5cc2f9-5494-4ba9-af57-3ced3be597dco%40googlegroups.com.

[twdev] Re: Custom markup (continued 4)

[TonyM]

Mario,

I think it would be useful to include such "compound customisations" with 
the plugin or at lest on the plugins website. Although perhaps it could be 
an optional item that requires tagging.

Having used html tables within wikitext for so long, I find it easier to 
follow a html table format, and simple closures, as follows;

\customize tick=table _element=table _endString="/table" _mode=block
\customize tick=caption _element=caption

\customize tick=th _element=th

\customize tick=td _element=td _classes=".hl"  _mode=block

\customize tick="tr" _element=tr _mode=block _endString="/tr"

´table ´caption Some caption text
´tr
´th header 1
´th header 2
´th header 3
/tr


´tr
´td 1 text
´td 12 text «  and  »
´td
* cell 13 text
* line 2
* line 3
/tr


´tr
´td 2 text
´td 22 text
´td 23 text
/tr
/table

However if we are considering distributing or documenting "compound 
customisations" I would be tempted to extend my table to to include a lot 
more such and head/foot/body, a list widget for both rows and columns, as I 
would do this for myself anyway.

Perhaps your table responding to classic tiddlywiki tables AND one 
responding to html tables included would make sense?

Tony



On Saturday, 31 October 2020 00:55:25 UTC+11, PMario wrote:
>
> Hi folks,
>
> I'd like to discuss with you the table syntax as shown in
>
> \customize tick=table _element=table _endString="/endTable" _mode=block
> \customize tick=caption _element=caption
>
> \customize tick=! _element=th 
>
> \customize tick=cell _element=td _classes=".hl"
> \customize tick _use=cell
>
> \customize angle="===row" _element=tr _mode=block _endString="---"
> \customize angle=cmulti _element=td _classes=".hl" _mode=block 
> \customize angle=| _use=cmulti
>
> ´table ´caption Some caption text
> »===row
> ´! header 1
> ´! header 2
> ´! header 3
> ---
> »===row
> »| 1 text 
>
> »| 12 text «  and  » 
>
> »|
> * cell 13 text
> * line 2 
> * line 3 
> ---
> »===row
> »| 2 text 
>
> »| 22 text 
>
> »| 23 text 
>
> ---
> /endTable
>
> and: https://wikilabs.github.io/editions/custom-markup/#test-dave-table
>
> Do you think it could be used as a default, shipped with the plugin. .. 
> The CSS for multiline and eg: bullet lists will need some adjustment .. 
>
> tick-cells are use for single line cells terminated by \n
> angle-cells are used for multi, block like cells terminated by \n\n
>
> »===row
>ends with 
> ---
>
> -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/53fb6198-c3bd-41f0-b02e-e1ddbe403d95o%40googlegroups.com.

[twdev] Re: Custom markup (continued 4)

[PMario]

Hi folks,

I'd like to discuss with you the table syntax as shown in

\customize tick=table _element=table _endString="/endTable" _mode=block
\customize tick=caption _element=caption

\customize tick=! _element=th 

\customize tick=cell _element=td _classes=".hl"
\customize tick _use=cell

\customize angle="===row" _element=tr _mode=block _endString="---"
\customize angle=cmulti _element=td _classes=".hl" _mode=block 
\customize angle=| _use=cmulti

´table ´caption Some caption text
»===row
´! header 1
´! header 2
´! header 3
---
»===row
»| 1 text 

»| 12 text «  and  » 

»|
* cell 13 text
* line 2 
* line 3 
---
»===row
»| 2 text 

»| 22 text 

»| 23 text 

---
/endTable

and: https://wikilabs.github.io/editions/custom-markup/#test-dave-table

Do you think it could be used as a default, shipped with the plugin. .. The 
CSS for multiline and eg: bullet lists will need some adjustment .. 

tick-cells are use for single line cells terminated by \n
angle-cells are used for multi, block like cells terminated by \n\n

»===row
   ends with 
---

-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/4d80861d-3ad5-4b05-83ef-f313fe6ca11co%40googlegroups.com.

[twdev] Re: Custom markup (continued 4)

[TonyM]

Mario,

Go how you want, but my understanding comes from the more "modern use" 
noted later in the Wikipedia entry, truthfully a leading one may confuse me 
ans many others given this;

*The pilcrow is used in desktop publishing software 
>  such as 
> desktop word processors 
>  and page layout 
>  programs to mark the presence 
> of a carriage return 
>  control character 
>  at the end of a 
> paragraph. It is also used as the icon 
>  on a toolbar 
>  button that shows or hides the 
> pilcrow and similar hidden characters, including tabs 
> , whitespace 
> , and page 
> breaks . In typing 
>  programs, it marks a return that one 
> must type.*


I have being keen to make a preview that acts as the aforementioned toolbar 
button would.

You are right to *"produce html output that is well formed", *I will return 
to reviewing the html my tests generate. I not you have many of my prior 
examples in test tiddlers, thanks its a helpful reference. 

Tony

On Friday, 30 October 2020 15:44:29 UTC+11, PMario wrote:
>
> On Friday, October 30, 2020 at 1:09:16 AM UTC+1, TonyM wrote:
>
> Only one issue you may have overlooked, or I missed your answer. Rather 
>> than use pilcrow at the beginning of a line I would only use it at the end, 
>> if you don't see an "end of line only pragma" being possible as 
>> discussed in this reply 
>>  
>> then 
>> I would suggest the reverse pilcrow, as it indicates beginning of paragraph.
>>
>
> Have a look at this: https://en.wikipedia.org/wiki/Pilcrow
>
> Pilcwrow is used at the beginning of a new paragraph and by default stops 
> with \n\n in the customize implementation. ... Similar to TTs suggestion. 
> ... 
>
> I did try to implement pilcrow / reverse pilcrow as inline markers too. .. 
> BUT it produces really strange and invalid HTML code. Ps inside SPANs 
> inside Ps if stuff was nested. .. So I did move it to "block" like syntax, 
> where it produces some predictable html output. 
>
> One of my goals still is, to produce html output that is well formed. ... 
> There is a pending PR and some discussion at GitHub, that try to fix the 
> problems with too many Ps in TW wikitext output. Especially in the UI 
> sections, where it causes theming problems. 
>
> -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/47d77f8a-6a93-4fdb-8fb1-cd560fcaa1f8o%40googlegroups.com.