@PMario
OK, so I'm testing things directly on your site. As noted, this is super
cool and could become very useful.
I did publish an EXPERIMENTAL wiki [1] at wikilabs, that contains 3 new
> wikitext elements.
>
I understand these three to be
´ = tick
» = angle quotes
space-space-newline
That last one is independent of the former, yes? However, this code does
not render line break between 111 and 222:
».aaa 111 (ends with space space newline)
222
<style>
.aaa {background:red; display:inline-block; max-width:133px;}
</style>
...and using tick instead also shows no difference between
space-space-newline and just newline.
The "*tick*" will create a *DIV *element _and_ stopps at the first *\n *newline
> it finds
>
> The "*angle*" will create *P *element, stopps at the first *\n\n*
> double-newline it finds.
>
So, the point here is presumably that one is allowed to do \n and still
keep the styling after. But, as noted, what is the point in allowing a \n
when such a single linebreak is not seen in the rendered text anyway? I
still cannot use one "command" to style two paragraphs (i.e separated by an
empty row). Or can you give an example where ´ is insufficient but » saves
the situation?
...or maybe you mean one also *has *to use your .h class that you bring up
below, for the linebreaks?
´.r.j.c.cp Some test text
>
will create
>
> <div class="r j c cp wltc-l1 wltc">Some test text </div>
>
So do tick and anglequote add extra classes beyond what the user specifies
(wltc-11 etc)?
There are 5 new edit-toolbar-buttons: Only 3 have shortcuts atm. You can
> assign them at the Control Panel
>
>
>
>
IMO this is a pretty expensive compromise for not using more accessile
markers. It is expensive in real estate and visually (*four*!). Note also
that there's a Controlpanel setting to Show/hide the toolbar. I, for one,
prefer it hidden. More cricitally I stand by my opinion that we should aim
for Grubers goal as much as possible in that the authoring process should
be minimally distracted and adding the marker should be as non-distracting
as adding a list-bullet or a heading exclamation mark.
...or no marker; I don't think anyone answered why there needs to be a
marker at all beyond just starting the line directly with
.class My text
BTW, it is worth noting that all options also require an empty preceding
row (except the very first line in editor). This is not a complaint, just a
fact.
> - space-space-newline or
> - space-space-backslash
>
> There are 2 tiddlers
>
> - test-hard-linebreak-and-transclusion
> - nl-is-hard-linebreak
>
> That test a different way to crate hard linebreaks. NO plugin involved!!
>
Nice! So that is done by adding the .h class if I understand. It works for
angle quotes but not tick so, as noted above, maybe this is the practical
outcome difference between angle quotes and tick?
Planned:
>
> - test if it's possible to use --- aka HR instead of \n\n as a
> stop-indicator.
>
(Advantage: Visible in edit mode.)
> - test if it's possible to use pragmas to use different HTML tags instead
> of DIV and P
>
So would this mean one would *also *have to add pragmas as soon as one
wants to use, say, ´.foo ?
> - test if it's possible to use a pragma to define the stop-indicator
>
Locally?
> - test if it is possible to create a wrapper element and call a macro
> using the text as the ONLY parameter
>
I'm kneeling in prayer.
PS: Yea I know my page has a typo. I named it "angel bracket" .. and I'm
> not sure if I'll fix it ;)
>
Angels are more interesting than angles so keep it ;-)
<:-)
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/15596c44-3466-4f5f-bf35-e1d2d887eb79o%40googlegroups.com.
