That's very, very close--too close to make a decision based on the polling alone. I'll take this back to my tower sanctuary, though, and figure out what makes the most sense.
After reviewing the poll results, and making a list of pros and cons for each, I've decided that we'll return to using HTML for the time being.
There are things that we need to be able to do with HTML that we can't do with BBCode. There are things I'd like to do with BBCode that are more advanced, but those all require time to develop and troubleshoot with Vanilla.
We may revisit this sometime in the future, but for now, the site's back to "Simple HTML". The formatting bar will remain at the top of the post box, and the [ spoiler ] tag still works.
Thank you all for your patience while we debated this issue!
After reviewing the poll results, and making a list of pros and cons for each, I've decided that we'll return to using HTML for the time being.
There are things that we need to be able to do with HTML that we can't do with BBCode. There are things I'd like to do with BBCode that are more advanced, but those all require time to develop and troubleshoot with Vanilla.
We may revisit this sometime in the future, but for now, the site's back to "Simple HTML". The formatting bar will remain at the top of the post box, and the [ spoiler ] tag still works.
Thank you all for your patience while we debated this issue!
Drat! And I was going to suggest that we replace the editor with vi!
Does this mean we can post .bmp images again? Even if it does mean that, should we avoid posting .bmp images as a courtesy, because they're too big?
You could already post .bmp files with the BBcode too. That said, you shouldn't post .bmp files, unless you have a good reason for them to be .bmp.
For example, if you want to share a portrait, already cropped to 330x210, then it makes sense to post it as a .bmp file, since people can then simply save it in their portraits file and use it. Coincidentally, the relatively low resolution means it's not really a problem filesize wise (if you don't post dozens at once).
@Thels - < b > and < i > still work for bold and italics (same for underline). Not sure why the advanced editor chooses to use less intuitive tags, but the basic ones should all still work.
@Thels - < b > and < i > still work for bold and italics (same for underline). Not sure why the advanced editor chooses to use less intuitive tags, but the basic ones should all still work.
@Dee: Yeah, the basic ones are obvious, but images and quotes look fairly different. Also, when I drag an image in, it includes several parameters within the tag, and I haven't tested yet if these can be safely removed.
Obviously, it makes sense that the tags are less intuitive. They're not just tags, they're actual HTML code, designed to create entire websites, while BBcode is specifically designed for making up forum posts. It stands to reason that the HTML code is less intuitive than the BBcode.
That said, the spoiler tag is still BBcode inside HTML. If the spoiler tag BBcode can be included, wouldn't it be possible to include a few more basic BBcode tags, so that we have best of both worlds? Basic BBcode tags that most users could conveniently work with, and HTML support for those that want more complex post formats.
Comments
That's very, very close--too close to make a decision based on the polling alone. I'll take this back to my tower sanctuary, though, and figure out what makes the most sense.
We have Bengoshi, Lady Rhian, Shandyr, Anduin. . That would be a walk in the park
After reviewing the poll results, and making a list of pros and cons for each, I've decided that we'll return to using HTML for the time being.
There are things that we need to be able to do with HTML that we can't do with BBCode. There are things I'd like to do with BBCode that are more advanced, but those all require time to develop and troubleshoot with Vanilla.
We may revisit this sometime in the future, but for now, the site's back to "Simple HTML". The formatting bar will remain at the top of the post box, and the [ spoiler ] tag still works.
Thank you all for your patience while we debated this issue!
Does this mean we can post .bmp images again? Even if it does mean that, should we avoid posting .bmp images as a courtesy, because they're too big?
Do the < i > < b > and < u > commands work now?
I guess I could test that.
test
Yes they do.
Glowy text, rejoice!!!
*Glowy text*
Arrows of Fire ready!
Arrows of Ice ready!
Rainbow Arrows ready!
K-THUNK!
Things are back to normal, brave warriors!
Is there a list of examples somewhere? You could already post .bmp files with the BBcode too. That said, you shouldn't post .bmp files, unless you have a good reason for them to be .bmp.
For example, if you want to share a portrait, already cropped to 330x210, then it makes sense to post it as a .bmp file, since people can then simply save it in their portraits file and use it. Coincidentally, the relatively low resolution means it's not really a problem filesize wise (if you don't post dozens at once).
Obviously, it makes sense that the tags are less intuitive. They're not just tags, they're actual HTML code, designed to create entire websites, while BBcode is specifically designed for making up forum posts. It stands to reason that the HTML code is less intuitive than the BBcode.
That said, the spoiler tag is still BBcode inside HTML. If the spoiler tag BBcode can be included, wouldn't it be possible to include a few more basic BBcode tags, so that we have best of both worlds? Basic BBcode tags that most users could conveniently work with, and HTML support for those that want more complex post formats.
Here's a list. Should you need help, you can feel free to tag me in the How To Format Your Post topic.
Sample Text
Sample Text
Sample Text
Sample Text
Sample Text
Sample Text
</blockquote>
</blockquote>
</blockquote>
<li> Sample Text</li>
<li> Sample Text</li>
</ol>
<li> Sample Text</li>
<li> Sample Text</li>
</ul>