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

[Georg Ringer]

Hi,

my opinion:

I don't need a default layout in TsConfig as this can just be done very
fast with BackendLayouts anyway.

Having every layout in TsConfig is IMO a bad idea, I like having it in
records (for extending it, whatsoever), but what could be improved is
the handling with multiple enviroments like a dev system with other uids
then in production. An idea: What about having an additional identifier
field in the belayout record which could then be used in the TS cObj
CASE to load different templates?

this would make it also easier for integration without different systems
because the identifier could be "home" or "news" or "2colpos" and the TS
would look like

PAGE.10 = TEMPLATE
PAGE.10 {
  template = FILE
  template.file.cObject = CASE
  template.file.cObject {
    key.data = levelfield:-1, backend_layout_next_level, slide
    key.override.field = backend_layout

    default = TEXT
    default.value = fileadmin/templates/default.html
    2colpos = TEXT
    .....
  }
}

or mabe even something like
template.file = TEXT
template.file.value = fileadmin/templates/{backend_layout}.html and we
could get rid of the CASE completley which needs to be extended all the
time by simple2 lines for a new template.

what you think?

georg