Monday 14 December 2009 9:40:00 am

Hi there,

Little late for me to jump into the discussion, but glad most of what I would have suggested was already covered ;) So just my key concerns:

• Maintain extensibility and make it easier to extend further. This especially regards tab menu, which in some of our projects simply doesn't fit in even with 1920px screen... Also, try to make all the new cool ajax tools extensible, as well.
• Extend the content object model with new meta attributes. By that I mean a very simple operation of extending content class attribute with two text fields, one for help texts (for the users), the other for implementation notes (internal or more technical).
• Don't overdo the ajax. I'm not an ajax extreme fan, but still I can appreciate how ajax can improve overall ease of use and performance. However, this is quite easy to spoil if you go too far with it. I have a new online banking account with total ajax interface that is winning prizes for the approach, but driving users crazy at the same time. Let's just maintain a good balance here.
• Introduce content class/object attribute tabs. This isn't impossible to implement by one's own, we've done it. But I think it deserves to be available out of the box. If you have content object that consists of 30 attributes, it is usually very helpful to have them tabbed into: content, images, meta attributes, geolocation and so on plus all others. This could entirely depend on INI settings for starters.
• Full screen width editing. While high resolution screens are more and more popular, so are some complex datatypes' or custom views interfaces. It would be great to be able to use not much less than 100% of screen width, especially in edit mode. Custom browse/edit views could enjoy that as well.

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Tuesday 15 December 2009 5:23:22 am

So your suggestion is?
Suggestions so far is to place them vertically, which will bump the content structure menu far further down.
Or only show ~5 tabs have a 6th tab called "more" where you'll get the rest as a drop down menu when you hover it.

• First of all I would stick to the current division between top menu and left/context menu (I agree that putting too much to the left menu might not be the best idea). So some sort of top menu - yes.
• The idea with 6 tabs + "more" drop down is kind of OK, but may be not very convenient on some occasions. This could be a bit improved if we always took user's last accessed tabs to the direct view and hiding the less frequently accessed in the "more" list.
• I would suggest an introduction of perspectives. A perspective would be a named, ordered collection of tabs. By default, we could have one or two perspectives. We could switch between perspectives somewhere in the top part of the layout, maybe a simple drop-down select. Perhaps this could be linked to access control subsystem, even though I don't think it would be the most important thing right away.

As you are the 5^2 person mentioning that I have now updated the requirement doc with a section on the class content model, please review!

• Should: Add (non-)translatable description text per class for use as internal notes.
• Should: Add (non-)translatable description text per class attribute for use as internal notes.

I have not included your Integrity flag suggestion, as I think required attributes are actually requried now and can't be left out of the post as of 4.1.0 and up.

• Sure, we assume that attributes cannot be simply skipped (which should be the case of obvious security reasons), then there's no more need for it.

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Tuesday 15 December 2009 8:58:07 am

tab menu, which in some of our projects simply doesn't fit in even with 1920px screen
Now that tabs support policy's (see the follow up blog post where we should have been discussing this ), will it still be that big for most users?

I'm not sure what you're referring to as "follow up blog post".

But not necessarily tabs policies resolve the issue, or at least not entirely, as there will be users who will face difficulties because they will have broad access to the system. Perspective idea is kind of similar to, but much simpler than a role login. Some systems make it possible to declare role at login and then you only have enough tools and interfaces to carry out tasks resulting from this particular role. Of course, I don't say that's a good idea for eZ, but the perspective approach is: "show me about just what I need at the moment". For example: content perspective - content, media, users; administration perspective: setup of all sorts; client company perspective: all sorts of dedicated tabs.

Please point me to where I can read more about tab policy support.

Thanks,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Tuesday 02 February 2010 2:15:27 am

oh man I feel so much on this topic, especially with tabs. It gets so confusing with so many tabs, especially Mozilla Firefox, for some reason Chrome is much easier and much better organized, although I know there are some codes for lining up tabs not just in line but in columns as well.

Tuesday 20 July 2010 11:48:19 pm

Good article, http://www.hc-cca.com,Each and every point is good enough.http://www.jin-kun.comThanks for sharing with us your wisdom.

http://www.jxselak.cn

http://www.zlstoy.com