On Wednesday, March 4, 2020 at 11:16:17 PM UTC+1, TonyM wrote:

Would it be possible to still trigger this markup with <dot>any character? 
> This was the original desire?
>

This will follow once I did the \parserule dotparagraph pragma. ... It's a 
bit more complicated as it seems. 

The \rules except/only pragma is only capable of removing wiki rules after 
the parser for a tiddler is instantiated. What we need for \parserule is: 
"_add_ a new rule and make sure it is higher priority as others" mechanism. 
Which doesn't exist atm. Most of the functions exist in the core, but I 
need to make it useable in a different way. Plus keep backwards 
compatibility, if possible. 
 

> Can your extended markup still accommodate this?
>

I think so. 
 

> Although I see that the space may allow to load it with more possibilities.
>
>    - I am yet to grasp the use of trailing "space space enter"
>
> That's compatible to the new "CommonMark" markdown parser spec for "hard 
linebreaks". So if someone copies a markdown paragraph to TW, they should 
see the same result. 
see: https://spec.commonmark.org/0.29/#hard-line-breaks .. (I just found 
out, that it's not 100% compatible, but good enough to start with)

This rule is also intended to work with TW syntax like: 

* test  

next line should be part of the li-element. 

*If you copy the above code into tiddlywiki.com and your experimental wiki, 
you'll get a different result.* 

This is intended, to be a global modification and is intended to work for 
every list-like wikitext. eg: *#:;. and so on. 

>
>    - Is there a reason why we could not issue a <br> for 
>    <dot><space><space>, or even turn the previous line into a paragraph as a 
>    result.
>
> I think, it should be possible to "remove" empty lines or empty lines 
preceded by a dot from the generated DOM. At the moment empty p-tags are 
created. They are not visible, but they are there, which isn't nice. 
 

> I have also started testing if and how the previous markup method work 
> with and without the ".paragraph" to introduce css the ".classname" eg 
> ";.classname "
>

ok

You asked
>
>> What does a notes do ?
>
>
> It was only an example of another bespoke markup, I imagined it boxing a 
> div and providing dl dt tags to highlight a specific note.
>

Yea, I did think about that. ... But there will be a steeper learning 
curve, the more elements we add or change from the original behaviour. 
 

> Given your work so far and this particular case of providing markup to use 
> `<p>` html tags makes me ask if it makes sense to also develop markup for 
> `<section>`, `<div>` and `<span>` to which one can introduce css. I am 
> thinking of what markup could be helpful for rapid authorship, note taking 
> and very simple layout.
>

<section> and <div> should be no problem, because they allow "flow content 
<https://developer.mozilla.org/en-US/docs/Web/HTML/Element/section>" as 
"Permitted Content" see the link. 
<span>'s are inline elements only. They only allow "phrasing content 
<https://developer.mozilla.org/en-US/docs/Web/HTML/Element/span>" (same as 
paragraphs). It will produce invalid html code if used at the start of the 
line like: * or # or .

I was thinking about an <aside> (note) using > at the beginning of the 
line. 
 

> eg: place this in a dot paragraph wiki and see how beautiful the result 
> with little effort
>
.....

Yea, It looks nice. The html code is OK-ish, but there is potential for 
improvements. eg:

TW knows about a mechanism, to manipulate heading levels for transcluded 
tiddlers. see: https://tiddlywiki.com/#tv-adjust-heading-level%20Variable 
If it would be possible to set this veriable with a \pragma or \define and 
the rendering mechanism would accept it, it would be possible to start your 
notes like this: 

\startheading 5

! Class notes Feb 23 2020
!! Subject: Analysis
. Analysis and Synthesis.

The html output could be 

<h5>Class notes Feb 23 2020</h5>
<h6>Subject: Analysis<h6>
<p>Analysis and Synthesis.</p>

If there would be a proper CSS setting, it would be the same manual work, 
but produce much better html code, from a semantic point of view. 

Having a closer look at your example code and the description: 

If dot space is applied to all lines and they include blank lines I am 
> getting the desirable result from the html paragraph tag, the blank lines 
> collapse into one paragraph break.
> This is helpful when pasting content from elsewhere because it is often 
> full of multiple blank lines, eg copy off a webpage.
>

I also think, the manual workflow could be improved, using less time and 
getting improved html output. ... BUT I'll need to think about this. ... I 
think about new editor-shortcuts, 
That can speed things up segnifficantly. 

-m
PS: I'll need some time, since the last storm knocked over some of my 
trees. I have to remove them. 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/388890a8-4778-4303-a39e-5a9c7d32ccdf%40googlegroups.com.

Reply via email to