[TYPO3-core] Discussion: Remove default columns in favour for backend_layout
Søren Malling
soren.malling at gmail.com
Thu Jul 19 12:30:36 CEST 2012
I still think that we are missing something here, concerning
backend_layout (totally OT of my original mail, but as we are
discussing it)!
backend_layout is made to visualize the frontend output, but still we
have no connection between a backend_layout and a frontend output.
So what is it worth, if the editor can choose a different (backend)
layout, but the FE is unchanged?
Søren Malling
Twitter: twitter.com/sorenmalling
TYPO3 Danmark: twitter.com/typo3dk
On Thu, Jul 19, 2012 at 12:03 PM, Philipp Gampe <philipp.gampe at typo3.org> wrote:
> Hi Jigal van Hemert,
>
>> It will introduce extra parsing of TSconfig and looking up extra data
>> when handling the BE layouts. This will certainly not speed up the BE.
>
> Parsing needs to be done anyway, as the content of the records are pretty
> much TSconfig too.
>
> Considering the huge TS that is there by default, especially the RTE TS, I
> do not thing that those few lines add a lot of parsing time.
>
> But we should advice users to use records if they have many different
> layouts.
>
> Best regards
> --
> Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
> Documentation – linkvalidator
> TYPO3 .... inspiring people to share!
>
> _______________________________________________
> Before posting to this list, please have a look to the posting rules
> on the following websites:
>
> http://typo3.org/teams/core/core-mailinglist-rules/
> http://typo3.org/development/bug-fixing/diff-and-patch/
> _______________________________________________
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core
More information about the TYPO3-team-core
mailing list