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

[Dmitry Dulepov [typo3]]

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...

>> 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...

>> But I think it went without proper supervision and therefore did not 
>> make expected result. 
> 
> Not true, just because you might not see all the communication that is 
> going on, doesn't mean that there isn't any.

Ok, but how it happened that we still have redundant functions with all supervision?

> Well, we had to start somewhere, right? You also know that we can't do 
> any voodoo magic, right? We will keep improving... but somewhere we also 
> need to come to a point where we say "this is a state we can release and 
> we can build on".
> I also think that we can iron out UI glitches up to some point with 
> 4.2.x releases.

Why didn't all started with old good Jens slides? :) I thought they are really good example how BE should look like.

-- 
Dmitry Dulepov
TYPO3 core team
Web: http://typo3bloke.net/
Skype: callto:liels_bugs
"Nothing is impossible. There are only limits to our knowledge"