PHPBB3-10418 - WYSIWYG Editor/Rich Text Editor

[brunoais]

Cookies can be set to expire an arbitrary amount of time into the future. Say, six years. As long as the user visits your site in the next six years, the cookie data is never lost.

May be, but due to privacy problems, most browsers clear cookies after certain period of time. Hence cookies ARE NOT fool proof!

Only if you program for them to have a max expire date.
Firefox, by default, trusts the server. If you tell the user's browser to save the cookie for 5 years, it will save it for 5 years unless you changed it in its settings so that it would not do it.
Chrome seems to work the same way.
IE sounded also the same way.
...
What's your point?

[AliasM2K]

Only if you program for them to have a max expire date.
Firefox, by default, trusts the server. If you tell the user's browser to save the cookie for 5 years, it will save it for 5 years unless you changed it in its settings so that it would not do it.
Chrome seems to work the same way.
IE sounded also the same way.
...
What's your point?

Was just implying that it is better to rely on databases than on cookies to determine the default state of the users editor.

[AliasM2K]

Besides, have been working on a CKEditor based rich text editor...
Here is my progress... Just completed the toolbar. Now working on outputting BBCode.

Did my best to reproduce the current BBCode editor to a rich text editor.

What do you think?

[Senky]

...What do you think?

I would recommend to remove bottom panel (currently showing "body p span") - We will not need it using BBCode as well as majority of users do not know what does this even mean...

[AliasM2K]

I would recommend to remove bottom panel (currently showing "body p span") - We will not need it using BBCode as well as majority of users do not know what does this even mean...

Thanks for the suggestion... Implemented!

[AliasM2K]

Made quite a lot of enhancements... What do you think?

[brunoais]

Looks good. Please proceed.

[Senky]

Is there a way to quicky switch back to old textbox-style editor? This should be one of the most important features. Maybe it does not need to switch it back to textarea, but (as it works ie for vBulletin) just keep editor, but show BBCodes in text. I mean something like when you use rich text editor, you can see:

bold italic underline

and when you click on button which is to toggle editors, your message changes, so that you can see BBCodes:

Code: Select all

[b]bold[/b] [i]italic[/i] [u]underline[/u]

Hope you understand.

I would recommend also to include fullscreen option (if possible), distraction-free fullscreen, and keyboard shortcuts (just like in Word, or WordPress) - it rapidly speeds up writing...

Anyway, good job you are doing!

[brunoais]

^ and also:
Don't make the button unavailable when viewing the "source code". E.g. IP.B disables compeltly the buttons while viewing the source.
"Wanna change the source? Sorry, no buttons available."
I hate that!

[jsebean]

^ and also:
Don't make the button unavailable when viewing the "source code". E.g. IP.B disables compeltly the buttons while viewing the source.
"Wanna change the source? Sorry, no buttons available."
I hate that!

That's default in CKEditor when you switch to source code from what I noticed. Unless this can be changed, then when the user selects the plain bbcode editor it should go back to the editor like we have now. Only issue is if you want to switch to source code editor right then and there, unless, again, the default action of disabling buttons in CKEditor when in Source code view could be changed.