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

[Philipp Gampe]

Hi Jigal van Hemert,

Jigal van Hemert wrote:

> Hi,
> 
> On 17-7-2012 19:18, Steffen Müller wrote:
>> Store default layout using pageTS:
>> http://forge.typo3.org/issues/37208
> 
> This has been discussed in a different issue and/or different patch. It
> got several negative votes because this stuff doesn't belong in pageTS.
> It's easy enough to transfer the layout in records.

Really? SO how do you version it? How do you import it if some records 
already exist.
Plus it uses numeric key, so if you assign a different uid to a record, 
frontend rendering breaks.
This can all be avoided by adding the definition to the pageTS.

>> In the end, ship some fine-selected default backend_layouts:
>> http://forge.typo3.org/issues/39025
> 
> Why pollute the installation with BE layouts you will not use? An
> integrator must clean this up for his clients.
> Bloat, unnecessary stuff. This can easily go in an extension which
> supplies the FE templates and matching BE layouts.

Those few CSS classes can be shipped by default which would make TYPO3 
finally easily templateable for newcommers. This is really just a wrapping 
div and few CSS rules to support this layout frontend. This is only about 
structure and not about layout.

This could be part of styles.content.get* just the left, right, border is 
now.
Or maybe even better a styles.layout.*.


There are even more options. Extensions can then just add a layout via 
pageTS and (assuming text keys) just add the needed TS whichout big 
precessing.
This is not possible with the current system.

Cheers
-- 
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – linkvalidator
TYPO3 .... inspiring people to share!