I think that Brunoais was talking about the BBCode insert buttons (above the posting input window -- B, I and u, for example), not the keyboard "buttons" (AKA "keys").CarstenF wrote:Yes, definitively!brunoais wrote:Is it hard or unpleasant to press the buttons to generate the BBCode tags' text?
With German keyboard layout (and I suspect the same is true for many other non-US layouts as well), it is even difficult with a regular, full PC hardware keyboard, as explained in my earlier post.
+1.EXreaction wrote:But really, who uses their mobile devices for that much anyways? Does anyone expect to write well formatted documents on their phone? No, they don't--people use their phones for quick tasks and leave in depth work to devices with more usable input.
It would be far worse on a mobile device for the 95% of users who haven't memorized all of the formatting rules for whatever flavor of markdown is used on the site. Whenever I have to try and format something in markdown I always need a separate dedicated window open with the specific rules for the site I'm trying to use--try that on a phone.
that ^.Pony99CA wrote:I think that Brunoais was talking about the BBCode insert buttons (above the posting input window -- B, I and u, for example), not the keyboard "buttons" (AKA "keys").CarstenF wrote:Yes, definitively!brunoais wrote:Is it hard or unpleasant to press the buttons to generate the BBCode tags' text?
With German keyboard layout (and I suspect the same is true for many other non-US layouts as well), it is even difficult with a regular, full PC hardware keyboard, as explained in my earlier post.
I was going to ask that question myself. Why can't you press those buttons to insert the BBCode for you instead of typing it?
Steve
Well... sometimes, it's desirable write at least a minimum of formatting on phones and tablets, too. For example, if I want to include a list with a handful of items in a reply post, I would like to do that no matter if I'm at the desktop PC or with a mobile device at this time.EXreaction wrote:But really, who uses their mobile devices for that much anyways? Does anyone expect to write well formatted documents on their phone? No, they don't--people use their phones for quick tasks and leave in depth work to devices with more usable input.
Sorry, but this sounds like Markdown could only be used if the user memorized all of its syntax at once, and was unusable otherwise, but I think that this is wrong. Let me re-quote your statement, with "Markdown" replaced by "BBCode":It would be far worse on a mobile device for the 95% of users who haven't memorized all of the formatting rules for whatever flavor of markdown is used on the site. Whenever I have to try and format something in markdown I always need a separate dedicated window open with the specific rules for the site I'm trying to use--try that on a phone.
It would be far worse on a mobile device for the 95% of users who haven't memorized all of the formatting rules for whatever flavor of BBCode is used on the site. Whenever I have to try and format something in BBCode I always need a separate dedicated window open with the specific rules for the site I'm trying to use--try that on a phone.
Because the sequencePony99CA wrote:Why can't you press those buttons to insert the BBCode for you instead of typing it?
This sounds very very exiting!brunoais wrote:It's already part of the TODO to allow swapping SCE between RTE, WYSIWYG and source code. With some adjustments, we probably can make 2 source code modes where 1 is BBCode and the other is MD.
With that, the only issue that remains is how to work with things that have no MD correspondence... I'll think about that later. Anyway, making something that does BBCode <-> MD is possible and easy (after having something that parses MD) for all BBCode that has MD correspondence.
But MarkDown is *obvious*. It makes sense unformatted, usually.EXreaction wrote:But really, who uses their mobile devices for that much anyways? Does anyone expect to write well formatted documents on their phone? No, they don't--people use their phones for quick tasks and leave in depth work to devices with more usable input.
It would be far worse on a mobile device for the 95% of users who haven't memorized all of the formatting rules for whatever flavor of markdown is used on the site. Whenever I have to try and format something in markdown I always need a separate dedicated window open with the specific rules for the site I'm trying to use--try that on a phone.
If there's no installed BBCode correspondence, then it is ignored and it is not parsed (just stored as-is).CarstenF wrote:This sounds very very exiting!brunoais wrote:It's already part of the TODO to allow swapping SCE between RTE, WYSIWYG and source code. With some adjustments, we probably can make 2 source code modes where 1 is BBCode and the other is MD.
With that, the only issue that remains is how to work with things that have no MD correspondence... I'll think about that later. Anyway, making something that does BBCode <-> MD is possible and easy (after having something that parses MD) for all BBCode that has MD correspondence.
Just a question, what is about MD that has no correspondence in BBCode, such as headings or (much less important) tables?
Hmmm, I was afraid of that. That means that features likebrunoais wrote:If there's no installed BBCode correspondence, then it is ignored and it is not parsed (just stored as-is).CarstenF wrote:Just a question, what is about MD that has no correspondence in BBCode, such as headings or (much less important) tables?
Makes sense, right?
Code: Select all
Headings
========
Sub-Headings
------------
Sorry, I'm not sure if I actually understand this:brunoais wrote:Depends if there's a BBCode for that or not.
Personally, I am disappointed by this so-called "standard" Markdown. It's been several years in the making behind closed doors and now they're going public without a formal grammar. Instead, we have a set of 441 "examples".CarstenF wrote:lso, please see this new and very promising effort:
http://standardmarkdown.com/