[TYPO3-core] RFC: #7573: Page properties: Make author and author_email visible instantly

[Martin Kutschker]

Dmitry Dulepov [typo3] schrieb:
> Hi!
> 
> Ingo Renner wrote:
>>> - current GUI design is not made with HCI in mind (it ignores certain 
>>> HCI concepts)
>>
>> which concepts exactly? can you name them?
> 
> Well, I had a short list below in my e-mail. In general BE does not take 
> into account what zones are most viewed by operator, there is a lot of 
> redundancy and there is no way at all to quickly make typical tasks for 
> editors.
> 
>> I agree with you in this point as I've noticed that, too. However 
>> they're not new but just more prominent now that the docheader drwas 
>> attention to them.
> 
> So that has to be fixed before developing docheaders. You see, these 
> things went into docheaders, so time was spent on integrating them 
> instead. Next someone will spend time removing them. Does this sound as 
> a right development cycle to you? Couldn't this be done more 
> efficiently? This is why we need HCI specialist at first place, 
> approving any change in GUI, reviewing all toolbars, select boxes, 
> positions, etc.
> 
>> I think we should remove them (maybe even before beta2) and leave only 
>> one way to switch modules -  the module menu. Another advantage that 
>> comes with that is deduced code once we get around and remove(!) the 
>> according parts that generate these buttons and usually also check for 
>> access rights before adding these buttons...
> 
> You mean - remove all these extra buttons or all doc headers? Docheaders 
> as such is a great idea, they just need to be clearly thought for each 
> module.
> 
>> These big ugly buttons in the page module are set to be removed, too - 
>> totally redundant...
> 
> Hm, I almost do not use standard page module, cannot comment on that...

There here for convenience as they show the most used functions. Yes, 
they are redundant, but you can disable them with user TS

> 
>>> And convenience, I am sorry, is not there.
>>
>> Not true, just some overload!
> 
> What about typical task for editors? Csn they be done quickly by 
> editors? Like creating a simple page? This is what people contantly ask. 
> They mus be able to *focus* on the task, not on finding fields in many 
> tabs. Long forms are bad but many tabs are bad too: more work to find 
> fields...

How about a quick toggle button "tabs<->list". Normally it would be tabs 
- or whatever the user TS sets as default :-) - but with a simple click 
you would get all tabs in one long list ready for scrolling. Cannot be 
too hard to implement with JS. ;-)

Masi