Item2285: Fullscreen mode might be confusing
Current State: New
Target Release: patch
There's no save/continue/cancel button in fullscreen.
I have had one phone call pleading "I lost my save button", a user who meant to switch to raw but clicked fullscreen by accident and didn't understand what had happened.
Though, I've received positive feedback about the new fullscreen feature as well.
I propose this:
- Add save/continue/quiet/cancel buttons in the TMCE toolbar
- Hide the form button equivalent when TMCE is in view
- Un-hide them when we switchToRaw
I really dislike redundant UI controls... But it's important that whatever we change, non-JS users are still able to edit on configurations where those users are supported.
- 24 Oct 2009
what about leaving our weirdness behind?
button - so its like a normal editor - where
pops up a
want to save
what about a
- 27 Oct 2009
I've set this WaitingFor
to get some ideas on this.
Please consider firstly a low-impact solution for patch release context, and then your thoughts for Foswiki 1.1:
- What do we do about making fullscreen less confusing for those who accidentally found it?
- How should we add save and cancel buttons to the toolbar?
- Should the toolbar only have these extra buttons in fullscreen mode?
- Should the buttons in the footer be hidden?
- Should the solution to this task be configurable?
- 03 Jan 2010
WRT to the full screen mode:
The full screen mode has really big flaws from a user expereince point of view. Your proposed changes might provide the lost functions but they do not cure the root cause.
Things like save, full screen, wiki text etc. should not be part of the editor as they don't edit anything. The editor's functions must be related to editing content. If we integrate those functions within the actual editor (like we have it today) we end up having completely different interfaces and experiences with each editor.
So the correct answer is that we need an area that is always visible, even in full screen mode. This area features save, full screen and things like that.
The not so good answer is that you might want to integrate the functions in the toolbar, but if so, please make them propper buttons not icons.
WRT to the save/save and continue:
exit pops up a
want to save dialog"
I see the point but a pop up confirmation is not the correct way to go. Dialogs cause misery. As soon as you've learned and understood the behaviour the pop up becomes a PITA and adds no value at all.
A better wording might be "finish editing" (no confirmation) and "save changes".
I'll adress both issues in my WireframesEditScreen
- 05 Jan 2010
Ahh, even better. I found an quiet old mock up of full screen edit mode I made the other day:
- 05 Jan 2010
Carlo, thanks for the input. I see what you mean now. So here are the functions not immediately related to topic content:
- HTML mode
I am actually tempted to suggest killing the HTML button, except I have a graphics designer that actually enjoys bashing out markup instead of WYSIWYG or WikiText
All these functions can be planted outside of the editor window. I will make this a background task to provide the mechanics (hrefs or submit buttons) to trigger these functions from outside the edit window, then the UI/design guys can clean it up...
- 05 Jan 2010
Need skin developers to be able to include template content into TinyMCE's fullscreen mode.
This requires customisation of the fullscreen plugin.
Also, skin developers need a way to toggle fullscreen from widgets they implement in their templates
- 15 Jan 2010