[twdev] Re: Custom markup (continued 3)

2020-10-03 Thread @TiddlyTweeter
Ciao PMario *Is Six ID's Enough? YES.* In practical use I think its a good number. - Good balance between strict TECHNICAL NEED to make it work (i.e. 2) and .. - ... VISUAL VARIANCE to make typing variant markup a good experience. In my tests I used all 6. 2 extensively. 2 moderately. 2 for

[twdev] Re: Custom markup (continued 3)

2020-10-03 Thread @TiddlyTweeter
Ciao PMario *A CONFESSION -* Using Custom Markup at first was very confusing for me! As soon as I started to do anything other than simple the layout would break. *This is because of Custom Markup's richness. Because it can do a lot a lot of different ways.* There are several dimensions which

[twdev] Re: Custom markup (continued 3)

2020-10-03 Thread @TiddlyTweeter
Ciao PMario *Comments on INLINE markup.* At the moment I'm writing markup like this ... »§ ›¶ `›¶` Example single line for SA phrase groups. Won't fully work till custom-inline is finished. ([[TT Notes]]) »¶ °O `»¶ ... ⁋` Example mutli-line block for SA phrase groups. °O Good

[twdev] Re: Custom markup (continued 3)

2020-10-03 Thread @TiddlyTweeter
Ciao PMario & all I been doing a lot of testing of using Custom Markup for layouts and precision CSS application. It is VERY good. A number of issues came up. I will post about each separately. First I comment about Editor Look & Keys, then Fonts & Unicode. I did testing on English Win7

[twdev] Re: Custom markup (continued 3)

2020-10-03 Thread PMario
On Saturday, October 3, 2020 at 12:57:31 PM UTC+2, @TiddlyTweeter wrote: *Comments on INLINE markup.* > > At the moment I'm writing markup like this ... > > »§ > ›¶ `›¶` Example single line for SA phrase groups. Won't fully work till > custom-inline is finished. ([[TT Notes]]) > »¶ >°O