Postponed
Project:
Aloha Editor (obsolete)
Version:
8.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
12 Oct 2012 at 18:54 UTC
Updated:
29 Oct 2012 at 21:05 UTC
Jump to comment: Most recent file

Comments
Comment #1
Bojhan commentedBetter image
Comment #1.0
Bojhan commentedUpdated issue summary.
Comment #2
wim leersVery interesting.
It is of course technically possible. However, it will cause a schizophrenic UX:
- for text formats that *can* work with AE, the format selector will be inside AE's UI
- for text formats that don't work with any WYSIWYG editor, the format selector will be below the textarea
- for text formats that work with another WYSIWYG editor, the format selector can be in yet another location
Thoughts?
Comment #3
Bojhan commentedI don't really see how any of those arguments really matter, the only schizophrenic part would be the WYSIWYG disappearing when you select an other text format.
I assume for all text formats, its in the AE UI, we can't have two places for textformat selector. It would remove the WYSIWYG buttons if you select a other textformat
No, it will always be in the top bar.
Well, contrib can do what they want. Often they lead by example, so I dont think this is a concern?
Comment #4
wim leersSo you're saying that the Aloha UI should remain present even if the user selects a text format that cannot work with Aloha?
It really depends on the active text format whether a WYSIWYG editor is possible and/or makes sense.
So it shouldn't be part of the Aloha UI?
Fair enough, but the point is that right now, the text format selector is in a consistent location. If we implement what you propose, that would no longer be the case.
Comment #5
wim leersTalked to Bojhan; can happen post-feature freeze.
Comment #6
wim leers.
Comment #6.0
wim leersUpdated issue summary.