We were having a small discussion of the topic with Bergius
Jr. (aka Joonas Bergius) and Oskari Kokko.
Some of the keypoints we were talking about were
* toolbars should be configurable and configuration
inheritable (last is the strongest)
* server
* sitegroup
* (site)
* user
## WYSIWYG-editors
This goes especially to TinyMCE and htmlArea. I would
suggest that we will make the user experience nice and give
a GUI to twiddle the settings for the user.
I also suggest that we can determine the possibilities with
ACL eg. in the following way (this one is for
administrators)
Bold (x) default ( ) yes ( ) no [ ] power user
setting
Italics ( ) default ( ) yes (x) no [x] power user
setting
This would be interpret that italics would be off for a
certain user and only power user can change this setting. Of
course the end user won't even see those marked with power
user level nor to set it on.
## Toolbars
We would place toolbars eg. on the right side of the screen
with fixed positioning as Bergie was also mentioning. They
also could (or should) be distracting as little as possible,
so I would be hiding them as default and showing them on
hover (or onMouseOver in case of IE).
I was playing a bit around and made a small example:
* http://www.kaktus.cc/?t
oolbar
This example has been tested with Firefox, Camino and
Safari. Due to time limit I didn't even bother to try it on
Internet Explorer. There shouldn't be anything preventing
it from working (besides position: fixed and hover, but both
of these have simple fixes anyway).
This uses script.aculo.us (I simply hate writing these
dotted things, the same goes to del.icio.us) JavaScript
libraries. At the moment the toolbar is positioned with CSS,
but I think that it should be less error prone to
non-JavaScript browsers and have JavaScript change the CSS
on load.
These settings should also be memorized either by JavaScript
into cookies (this would still make MidCOM caching possible,
even though with non-MidCOM template pages performance
shouldn't be a problem) or by Ajax to tie the position to
person preferences.
Local cookies might be the best option because of different
screen sizes. It would prevent the toolbar from being hidden
away if using a screen of different size.
## Datamanager2 itself
We were pondering on access keys. I think that 'Submit'
should have an access key (eg. Alt-S as just an example).
This could also be configured by
* component
* schema
Even though this wouldn't be a part of progress now, I
would like to reserve keywords for this in schema
definitions already.
Some widgets also should be using less space. Eg. datatype
image should give full access over the display size,
description text and such, but this shouldn't be visible
all the time to put on load for image editing.
-----------
This message has been sent to the Midgard Forums on http://www
.midgard-project.org/discussion/
DO NOT reply to this message by email. If you want to reply
to it, go to https://ww
w.midgard-project.org/discussion/developer-forum/reply/880a3
4907a7a3ebd80721923ea238833.html
Go to h
ttps://www.midgard-project.org/discussion/account/ to
update your contact details or click https://www.midgard-project.org/discussion/subscriptions/
campaign/unsubscribe/25eded291764e251a0b57d1cb42d6c4d.html to unsubscribe.
|