Supporting Markdown's rule of forcing a line break with two spaces at the
end of the line would be straightforward but I'm concerned that those
spaces will be annoyingly invisible when using the browser textarea control
to edit text. So it might be useful to add a more explicit syntax for line
breaks. One possibility is double backslash at the end of a line:
This will have a linebreak\\
But these two
lines will not
The @@ rule also comes in an inline variant that generates a span much like
the old {{class{content}}} syntax:
@@.class content@@
@@color:red;This is in red@@
It is more flexible in that it allows for styles as well as classes.
However, while it is almost the same number of keystrokes, it doesn't read
as well to my eyes.
One possibility might be to use double round brackets:
((class(content)))
I'm open to suggestions.
Best wishes
Jeremy
On Sun, May 12, 2013 at 9:02 PM, Arc Acorn <[email protected]> wrote:
> Interesting, I guess I may be over use to hanging around "bigger" beta
> stage projects where it's normally pointless to bring the idea of any form
> of function change up.
>
> After doing some good reading about MarkDown and common wiki syntax I
> think I see the overall issue much better.
> I also never realized how common/popular MarkDown was/is, so I can see
> the appeal from a developmental standpoint to use something that more
> people already use and therefore are use to handling and styling.
>
> My own favoritism for having line breaks handled like classic TW aside, it
> dose look like MarkDown have a fairly simple linebreak standard that
> doesn't appear to be implemented in TW5.
> http://en.wikipedia.org/wiki/Markdown#Line_breaks
> [Two spaces at the end of a line followed by a line break]
> Which would be strange to get use to, would be usable for my typing/note
> taking style compared to manually adding hundreds of <br /> tags.
>
>
> On the subject of syntax and styling though:
> One other thing I noticed is that the old easy span class system no longer
> exists:
>
> {{spanClass{Content}}}
>
> If I'm right it looks like it was intended to largely be replaced with:
>
> @@.pClass
> Content
> @@
>
> For ease of proper and quick reusable styling structure I would really
> like to see the return of some kind of syntax for handling span classes.
>
>
>
> On Sunday, May 12, 2013 8:10:14 AM UTC-7, Jeremy Ruston wrote:
>
>> Hi Arc
>>
>>
>>> I can see how for some people styling TwClassics system could be
>>> tricky... I've never had any issue with it myself though.
>>
>> I suppose one reason for that is that I like all text to look a standard
>>> per element unless I want a small part to be different, and wrapping blocks
>>> of text in a span class allowed me to do everything I've ever wanted.
>>>
>>> The new system is something I'll have to keep in mind though since I do
>>> a lot of scratch and quick note style typing that requires a lot of proper
>>> line breaks, I think it'll be best for my sanity and fingers for me to go
>>> ahead and bow out of the TW5 game for the foreseeable future.
>>>
>>
>> That's disappointing, your feedback has been very valuable in the project
>> so far. Please remember that TW5 is a work in progress, evolving in the
>> light of the feedback from the early users; things like this are not fixed.
>> In fact, this is pretty much the first discussion that's taken place about
>> this aspect.
>>
>> Right now, TW5 tries to emulate the behaviour of MarkDown with respect to
>> paragraph handling. We can separate out some underlying options though: the
>> first is whether to use <p> tags or <br/> tags. That is independent of the
>> second issue: how to mark up the ends of paragraphs. So we could, for
>> instance, stick with TW classic's behaviour of treating a single newline as
>> a paragraph break, and still use <p> tags.
>>
>> One deeper issue is whether and how far to be influenced by MarkDown. The
>> motivation for taking it into consideration is its popularly, of course,
>> but there are other perspectives (eg http://www.wilfred.me.uk/**
>> blog/2012/07/30/why-markdown-**is-not-my-favourite-language/<http://www.wilfred.me.uk/blog/2012/07/30/why-markdown-is-not-my-favourite-language/>
>> )**.
>>
>> Anyhow, I hope TW5 continues to hold your interest,
>>
>> Best wishes
>>
>> Jeremy.
>>
>
--
Jeremy Ruston
mailto:[email protected]
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
