Mario,

On HTML elements and Wiki text,

Please bare with me here trying to express this, I believe this is an 
important concept, but I know I am still no expert here.

It seems to me there is a rich set of opportunities to use html tags to 
achieve much in tiddlywiki. As we were considering;

<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 .
>
Yes, provide but not at start of line 

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



   - I raised this before because there seems to be a slow evolution within 
   tiddlywiki of replacing such html tags with either markup or widgets. 
   Changing markup is risky from a standards point of view, and widgets 
   certainly do limit sharability to tiddlywiki without further conversion, 
   but some bespoke markup could be available like the dot paragraph.
   - adding to the wikitext markup globally as you are discussing is a 
   worthy goal, however it is by nature is a slower process to maintain within 
   standards.
   - Of course we can feely add html to wiki text and have a lot of it 
   honoured, but this defeats the value of a markup language because html 
   makes the text much messier. An exception I find is in complex tables and 
   lists, I prefer to use html tables containing list widgets.


A strategy I am thinking about

I wonder if we could introduce a way to open up the access to html elements 
without compromising the markup. Hence my suggestion for being able to 
introduce div and/or section elements (span like within a line) via 
wikitext that are themselves css addressable. Like your paragraphs with 
classes.

The three key reasons are;

   - Provide a set of layout controls within tiddlers via markup
   - Provide access to the richness of HTML elements via markup
   - Reduce the need to progressively design wikitext/widget alternatives 
   to introduce new features by providing the extendibility 


Some points

   - We can already use the ".classname" against ";" and ":" markup 
   ";.classname" 
   - The key html tags for basic layout are here HTML inline and Block 
   elements <https://www.w3schools.com/html/html_blocks.asp>
   - Any HTML element can actually be redefined with the display parameter 
   <https://www.w3schools.com/cssref/pr_class_display.asp> 
   - If we focused on one html block (eg section even paragraph) and one 
   inline element that can be introduced with wikitext but then enable the 
   ability to pass "style/class and display parameter settings" then we have a 
   wikitext way to introduce html elements. I see here semantic elements 
   <https://www.w3schools.com/html/html5_semantic_elements.asp> which could 
   be introduced to a block element via the display parameter. Also see the 
   the  semantic elements that can be used to define different parts of a web 
   page, it would be good if there was an avenue to make use of such layout 
   within tiddlers via wikitext.
   - We may be able to ensure a tiddler copied elsewhere will just fall 
   back to the basic elements.

I hope I have being able to illustrate a concept that has being broiling in 
my mind for some time, and in quite relevant to this consideration of 
extending wikitext markup. The idea is a generic solution for bespoke 
extended markup, that resides safely within the markup standards. The idea 
is to make a leap rather than focus on gradual introduction of features to 
wiki text.

Speculation;

I would like to see some widgets that allows us to integrate html on-click 
and submit such that one could paste in a html form and have the input 
captured in tiddlers and fields. Even if we have to add a widget or two.

   - I wonder if we could use a standard dom, with a way to connect to the 
   TiddlyWiki dom, eg; allow html to populate a "sandbox" dom, with a submit 
   or action that dumps it to a tiddlers fields.

The idea once again is to leverage the technologies and content available 
without compromising the markup.

Regards
Tony

-- 
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/329b5c05-21cb-4d83-beb4-f2f0ad026bc1%40googlegroups.com.

Reply via email to