[TYPO3-hci] proposal for tabdesign w screenshots

[Jens Hoffmann]

Hi, thanks four your work in front!
I think this is not the right solution. Sorry.

- Microsoft's Icon-Bar has bad bad Usability, please don't take it as pro.
- If we need this much space for a Menu, the Concept must be wrong.
- 3 Tabs Rows with the same Style is totally confusing
- Redundant Menus is already a Problem of Typo3. This really doesn't help Usability!
- Without Icons it's faster for sure but it's bad for usability

I hope you don't hate me now :)
But i think, if we like to make Typo3 better, we need to be direct to ideas.

Friendly greez, Jens

Ps: Please comment my Ideas, too. PPT Thread.

redacted user schrieb:
> Hello *,
> 
> I'd like to share my approach and thoughts for the issue 
> 'tab/menubar-design for backendmodules'. I made some mock-ups to 
> illustrate the whole thing:
> 
> http://screens.typoheads.at/t3_tabs/
> 
> As you can see the basics for this design are coming from flex_forms 
> without t3_skin (from v 4.x) enabled. This approach has IMHO some 
> advantages:
> 
> * users will see elements of a BE-design which is already known
> * it is scalable: new rows can be added as you can see with quicklinks
> * users can 'switch' off rows as they like (with the little +-icon on 
> the outer right side)
> * users can acces submodules in two ways: either via the second row or 
> via the :hover-menu in the mainmodules
> * if we use the same css-classes as in flexforms, tabs will be 
> 'automatically' designed (as it is now with t3_skin and flex_forms) >> 
> less work (now and in future)
> * at least it looks like TYPO3 :-)
> 
> 
> disadvantages:
> * of course kasper (and maybe some others) did a lot of work already
> * it was shown on t3con (is this an argument or not...)
> * hmmm, come up with something...
> 
> 
> I'd like to offer my help on the programming level for realising this 
> menubar, please keep me updated if you need somebody.
> 
> 
> Have fun,
> Boris