[style size="30px"]Large Text[/style]
[style size="85"]Smaller Text[/style]
[style color="fuchsia"]Text in fuchsia[/style] or
[style color=#FF00FF]Text in fuchsia[/style] or Text in fuchsia
Well, this seems bad on multiple levels, i vote to return to BBCode, even if the white background issue can be solved.
-no preview (but i can't find a way to use codes, so that's maybe relate with that)
-no editable quotes
-i found the spoiler function, but can not use it well. Can't write a new paragraph outside it if activated once, and i don't find it by editing a comment.
Edit: ok with double enter i can escape from the spoiler tag, and i can copy it to paste in an older comment, but it's far from convenient.
Automation is the bane of humanity and will be the ultimate cause of its downfall. Thus, for the sake of the human race, I vote for the use of a BBCode based text editor, like it was in the very beginning before Vanilla started to create this new WYSIWYG text editor. It is a serious burden to sane online existence, and thus must be replaced with the old, stable manually-formattable, fully functional, and easier to use manual text editor. Vanilla, please let us use that good old text editor that used HTML.
This is why Martians are more advanced than us. They use manual text editors.
@JuliusBorisov My first impression: The new rich editor is not very intuitive to use, and it takes time to properly format comments. Direction keys (especially up/down) behave in a very unintuitive way.
I think a detailed instruction guide is really needed or there will be many frustrated users.
Testing: bold, italic, strikethrough, code and links. No underlined text? No colored text?
Emojis: 🤔🐹😱👽️
Testing advanced features:
(no 1st level heading)
2nd level heading
3rd level heading
4th level heading
5th level heading
unordered list
entry 2
subentry 1
ordered llist
entry 2
subentry 1
(no forced line breaks in list elements?)
Quoting a quote...
// A script block
IF
Global("testvar","GLOBAL",0)
THEN
RESPONSE #100
SetGlobal("testvar","GLOBAL",1)
Continue()
END
Tab key doesn't work (bad for writing code) :(
Testing markdown codes...
bold, italic, code
heading 2
heading 3
A quote...
Nothing to see here...
This is code inside a spoiler...
(or should be inside a spoiler)
The worst part of this IMO, is that the editor truncates quotes. So if there was a long string of quotes in a post, and you try to quote it, you only get a portion of the text near the top, and the later posts, which are probably what you're replying to are now lost.
Also, I notice that quotes are no longer collapsed in any posts, even those that predate the change.
They work, but only when the formatting is through the button to the left, and only if the tabs are pasted in. They are lost when formatting through the dropdown menu by highlighting the text, which also only appears to work on single lines, selecting multiple lines doesn't always present the dropdown menu for text. I don't know why there is a small white box underneath this paragraph, there are no lines after it.
What was "wrong" with the former old editor? (Still have it on mobile, thank god).
I find the new one anti-intuitive and on my computer, typing goes really slow like there were a ton of scripts that need to be executed.
@Alonso , it was temporarily activated by @JuliusBorisov . Now you can't access it, just when it will be activated next. (If there will be a next time at all.) But you didn't missed anything important.
Now the background when using Rich Editor is black. What is your opinion - would it still be bad to switch to it?
I vote no.
didn't properly support the TAB character
adding Code/Quote/Spoiler formatting through the highlight dropdown alters the content
quoted posts broke their formatting
quoted posts could not be edited, it's all or nothing, with most of it hidden behind a non-optional expansion button (spoiler tags do this just fine, as desired)
Now the background when using Rich Editor is black. What is your opinion - would it still be bad to switch to it?
Not unless Vanilla allows spontaneous switching between the two different editors at the will of the general users.
Reasons:
1. Lacks flexibility and fine tuning. Editing is complicated and unintuitive.
2. Various options are not accessible on the mobile and desktop versions (mobile version was missing emojis tab and desktop one was missing some formatting options).
3.Also, the text selection formatting pop up menu that appeared on mobile was in such an awkward position that it was covered by the default Chrome text selection pop up (Copy/Cut/Paste).
4. Quotes are horribly BROKEN.
5. Interface isn't intuitive and user-friendly. It is clunky, misses a lot of important options in an attempt to be compact, and it's design is just outdated to current expectations.
6. Doesn't support the all the formatting possibilities that can be achieved using BBCode and HTML. Do note that several rich text editors in current existence do support a wide array of formatting options, almost as much as BBCode and HTML allow.
7. I didn't find any options for alignment of the text (right, left, centre). If there's no such option, it isn't a proper rich text editor.
My conclusion: It needs a lot more development if it is to replace the current text editor. Even then, we should have the ability to switch between two different text editors, rich text and manual.
IF
See(NearestEnemyOf(Myself)) // If I see my nearest enemy
THEN
RESPONSE #100
Attack(NearestEnemyOf(Myself)) // Then attack my nearest enemy
END
That's not inlined code...
Maybe @argent77 can help...? I'm looking for something like "\verb" (from LaTeX)...
Moreover, being able to use something like "\begin{lstlisting}[language=WeiDU] ... \end{lstlisting}" (from LaTeX) would be great too... But I fear that's pretty much impossible ...?
I don't think that's possible with the limited number of BBCode tags available on this board. Many format elements were removed when Beamdog switched from Html to BBCode.
Comments
bolded text
italicized text
underlined text
strikethrough text
https://forums.beamdog.com/discussion/63570/forum-guidelines
Forum Guidelines
[style size="85"]Smaller Text[/style]
[style color="fuchsia"]Text in fuchsia[/style] or
[style color=#FF00FF]Text in fuchsia[/style] or
Text in fuchsia
table cell 1
table cell 2
table cell 3
table cell 4
Mushroom
just a test
abc
Ok, I have enabled it for an experiment and reverted back.
Well, this seems bad on multiple levels, i vote to return to BBCode, even if the white background issue can be solved.
-no preview (but i can't find a way to use codes, so that's maybe relate with that)
-no editable quotes
-i found the spoiler function, but can not use it well. Can't write a new paragraph outside it if activated once, and i don't find it by editing a comment.
Edit: ok with double enter i can escape from the spoiler tag, and i can copy it to paste in an older comment, but it's far from convenient.
'Tis something most unnatural here and I want no part of it
Automation is the bane of humanity and will be the ultimate cause of its downfall. Thus, for the sake of the human race, I vote for the use of a BBCode based text editor, like it was in the very beginning before Vanilla started to create this new WYSIWYG text editor. It is a serious burden to sane online existence, and thus must be replaced with the old, stable manually-formattable, fully functional, and easier to use manual text editor. Vanilla, please let us use that good old text editor that used HTML.
This is why Martians are more advanced than us. They use manual text editors.
@JuliusBorisov My first impression: The new rich editor is not very intuitive to use, and it takes time to properly format comments. Direction keys (especially up/down) behave in a very unintuitive way.
I think a detailed instruction guide is really needed or there will be many frustrated users.
Testing: bold, italic,
strikethrough,codeand links. No underlined text? No colored text?Emojis: 🤔 🐹 😱 👽️
Testing advanced features:
(no 1st level heading)
2nd level heading
3rd level heading
4th level heading
5th level heading
Quoting a quote...
// A script block IF Global("testvar","GLOBAL",0) THEN RESPONSE #100 SetGlobal("testvar","GLOBAL",1) Continue() ENDTab key doesn't work (bad for writing code) :(
Testing markdown codes...
bold, italic,
codeheading 2
heading 3
A quote...
Nothing to see here...
Edit: Code inside spoilers doesn't work???
The worst part of this IMO, is that the editor truncates quotes. So if there was a long string of quotes in a post, and you try to quote it, you only get a portion of the text near the top, and the later posts, which are probably what you're replying to are now lost.
Also, I notice that quotes are no longer collapsed in any posts, even those that predate the change.
They work, but only when the formatting is through the button to the left, and only if the tabs are pasted in. They are lost when formatting through the dropdown menu by highlighting the text, which also only appears to work on single lines, selecting multiple lines doesn't always present the dropdown menu for text. I don't know why there is a small white box underneath this paragraph, there are no lines after it.
I find the new one anti-intuitive and on my computer, typing goes really slow like there were a ton of scripts that need to be executed.
Not unless Vanilla allows spontaneous switching between the two different editors at the will of the general users.
Reasons:
1. Lacks flexibility and fine tuning. Editing is complicated and unintuitive.
2. Various options are not accessible on the mobile and desktop versions (mobile version was missing emojis tab and desktop one was missing some formatting options).
3.Also, the text selection formatting pop up menu that appeared on mobile was in such an awkward position that it was covered by the default Chrome text selection pop up (Copy/Cut/Paste).
4. Quotes are horribly BROKEN.
5. Interface isn't intuitive and user-friendly. It is clunky, misses a lot of important options in an attempt to be compact, and it's design is just outdated to current expectations.
6. Doesn't support the all the formatting possibilities that can be achieved using BBCode and HTML. Do note that several rich text editors in current existence do support a wide array of formatting options, almost as much as BBCode and HTML allow.
7. I didn't find any options for alignment of the text (right, left, centre). If there's no such option, it isn't a proper rich text editor.
My conclusion: It needs a lot more development if it is to replace the current text editor. Even then, we should have the ability to switch between two different text editors, rich text and manual.
My rating of the current rich text editor: 3.5/10
This kinda ruins e.g. my post here, or my top-post here.
Has anyone found a work-around to get multiple images in one line again?
Currently how those images are loading is proper behaviour.
Does Beamdog have the ability to add custom CSS to the forums, or it is all managed by Vanilla?
The following CSS rule would fix it:
.Message img.embedImage-img { display: inline; }This had been fixed, but now the exact same thing happened again.
Vanilla really loves to mess up existing posts, don't they?
EDIT: Now it works fine again.
Should be [inline]code[/inline], but it's not working...
IF See(NearestEnemyOf(Myself)) // If I see my nearest enemy THEN RESPONSE #100 Attack(NearestEnemyOf(Myself)) // Then attack my nearest enemy ENDThat's not inlined code...
Maybe @argent77 can help...? I'm looking for something like "\verb" (from LaTeX)...
Moreover, being able to use something like "\begin{lstlisting}[language=WeiDU] ... \end{lstlisting}" (from LaTeX) would be great too... But I fear that's pretty much impossible
testing