[TYPO3-core] Discussion: Remove default columns in favour for backend_layout

[Helmut Hummel]

Hi Joey,

On 19.07.12 13:01, JoH asenau wrote:

> Well - then b) is the only way to go, since IMHO its a "no go" to remove
> the records and the wizards in favour of TSconfig only.

I never inteded to remove the wizards :-P

> We introduced the record based backend layouts AND the wizard to improve
> usability.

The wizard is great. It would be a real pity to remove it.

> BTW: TYPO3 has always been famous for it's flexibility and multiple ways
> of doing things in slightyl different "flavours".

That is btw. also why TYPO3 is famous for being confusing and having a 
steep learnign curve.

> We often provide
> solutions for average users doing the same stuff as some other more
> complex solutions for the power users.

That is of course fine. But that does not mean that backend layouts need 
to be stored in records, does it?

I think it was implemented that way, because it was the easiest with the 
tools and frameworks we currently have.

> If it's about performance a simple switch that enables either records or
> TSconfig would not hurt too much. As a side effect it would reduce
> confusion since it would be clearly defined then, where to get the
> backend layouts from.

That is why I mentioned that as possible way to go.

> Streamlining things is a good idea, but we should not overoptimize
> things at the expense of usability and flexibility.

Of course not.

Backend Layouts are great, the wizard is great. I only think the storage 
would better fit in TsConfig than i records. But I also agree that we 
then need to transfer all the convenience we have and not just remove 
the wizards altogether.

Kind regards,
Helmut

-- 
Helmut Hummel
Release Manager TYPO3 6.0
TYPO3 Core Developer, TYPO3 Security Team Leader

TYPO3 .... inspiring people to share!
Get involved: typo3.org