TYPO3 Core

Hi! I'll try it. For which T3 version? 4.7?

For master branch (6.0) as this is a new feature.

Please have a look here: http://wiki.typo3.org/Contribute_Walkthrough

Can sombody help me with git, please?
I'm using Aptana with EGit.

I've succeeded with TYPO3_4-7-0.

But I can't see the tag "TYPO3_6-0-0alpha1" like in the repository (http://forge.typo3.org/projects/typo3v4-core/repository/show?rev=TYPO3_6-0-0alpha1).

Patch I055810ec19c2b1cde7a00f8703d6810264fab1ff pushed to review
https://review.typo3.org/#/c/11701/

Usage:

tx_cms_backendlayout {
    # If this option set the record configuration will override the TSconfig.
#    overruleRecords = 1
    # Comma seperated list of layout IDs to exclude.
#    exclude = 1,layoutC2313

    setup {
        # UID or record UID of the backend layout.
        layoutC2313 {
            title = Page C2313
            description = Page with a 2/3 and 1/3 column
            icon = 
            config {
                colCount = 2
                rowCount = 1
                rows {
                    1 {
                        columns {
                            1 {
                                name = ..Left..
                                colPos = 0
                            }
                            2 {
                                name = ..Right..
                                colPos = 2
                            }
                        }
                    }
                }
            }
        }
    }
}

To use IDs like "layoutC2313" it's necessary to change the fields backend_layout and backend_layout_next_level to varchar.

2 things

- I don't like changing the uid to varchar inside a topic called "tsconfig". please make a seperate issue for that as I am quite sure there are some queries which need then to be checked a bit different?

- I don't really get what this change does. which tsconfig can be changed? can you give some real world examples? thx a lot

@changing the uid
#37663

@examples
I just use the gridelements together with an own extension that supports some recurrent features like two, or three columns. Also sliders can be realized by gridelements for better usability (no seperate record storage needed).
For backend layouts this are layouts with two columns and a feature area for example. So I just install the extension and have at once all usable layouts and does not have to create records first.
For this it is usefull to have static and readable UIDs like "contentGroupThreeColumns" for gridelements or "layoutC2313" for backend layouts. Cause the record UID can change from one installation to the other.
But you can use records anyway.

To use this feature just copy and paste the example above into the field "TypoScript Configuration", "Page TSConfig" of a page. (This is a simple real world example. ;) )

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11804

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11804

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11804

Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11804

Patch set 6 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11804

Hi Arno,

are you willing to rebase this patch for latest master?

I think this makes a lot of sense, allowing us to move even more configuration to files. I might take care of rebasing the change.

Alexander Opitz wrote:

are you willing to rebase this patch for latest master?

Hi all!
Yes, I'm gladly do it, if the disscussion have ended.

Already on it - patchset will follow shortly ;-)

Patch set 7 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 8 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 9 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 10 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 11 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 12 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 13 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 14 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 15 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

At the code sprint in Essen we had a discussion about this feature with Ernesto, Oliver, Steffen R. and me. The result was that a slightly different solution would suite the future themes extension and possibly other extensions.
The core will not support BE layouts in TS config natively, but stick to records. The solution will be that extensions can define a data provider which will give the core information for:
- the list of available BE layouts in the page properties (each source is a separate group in the list to show the integrator where the BE layout comes from)
- the configuration of the BE layout for the Page module
Preferably the wizard may be modified to support that the configuration to edit comes from a data provider too.

This way any extension can add a way to store BE layouts. It can be stored in TSconfig, files, or anything else someone can think of.

The feature in the core should include:
- possibility for an extension to register a data provider
- change BE layout field to include information about data provider it comes from
- add info from data provider to list of BE layouts in page properties
- get BE layout configuration from data provider in Page module
- if possible: a mechanism to use the wizard on the BE layout configuration from a data provider

Patch set 16 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

By seeing this issue i wonder on how things are decided in the core team.

Can you maybe discuss this in your next core team meeting? or give a hint on how this patch can find a way into TYPO3 CMS core (maybe via hooks?)

Look at the current 30 votes in favor and try to put your objection in relation of the efforts made.

Thank you.

@Jigal van Hemert, during the discussion you heavily cared on performance.
now you want to introduce a more complicated way to do the same.
We already have a hook in the core to add TSConfig.

So please tell me / us how to proceed and how to ensure, that this is included in the next release!

@Olivier thanks a lot for taking care.

After thinking about the proposal of the core team for a while, I really start to like that approach, especially since we already got most of the necessary functionality in the existing patch. :-)

If I got it right, we have to remove the "hardcoded" TSconfig part from the loadSetup methods and replace it with the mentioned dataProvider, that can be registered by extensions then. In any case we will need itemsProcFuncs to modify the selectboxes of the backend_layout, backend_layout_next_level and colPos fields, which are already there and working.
We even got the modified Singleton class, that Claus mentioned in his comments.

So I guess after implementing the dataProvider-Hook into the loadSetup method and modifiying the related methods, we should almost be there.

Please correct me as soon as possible, if necessary at all, since I will start coding more or less immediately :-)

@Jo I say "go for it!" :) I agree about the todo list and implementation, that's the way to go. The other big problems are already fixed and indeed it would be awesome to make such a DataProvider for fluidpages as well - we'll have fewer conflict possibilities than before. It's beginning to sound like a solid solution with only a tiny performance impact (and I hope that DataProvider concept will be used elsewhere in CMS, too!).

@Claus, @Kay Wienöbst, @Jigal van Hemert: Since the feature freeze for 6.2 LTS has been postponed to Oct. 15th, I think we can make use of the additional time.

We will have a Gridelements weekend as described here: http://www.startnext.de/typo3-grid-elements-2-0/blog/?bid=20897
So I think it would be a good idea to have a discussion and final decision for the best backend layout solution there as well.

Currently we've got still enough places, so anybody who would like to join, feel free to do so! :-)

Still I will try to provide a proof of concept for the data provider before that weekend.

Patch set 17 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 18 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 19 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 20 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 21 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 22 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 23 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 24 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 25 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 26 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 27 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 28 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 29 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 30 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 31 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 32 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 33 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 34 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 35 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 36 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 37 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 38 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 39 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24767

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24769

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24769

Patch set 40 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 41 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Patch set 42 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/11804

Hi, will there be an example on how to use this?
I'm really confused, which is the final solution.

Here is an extension which utilizes the new backend layout dataprovider.
https://github.com/georgringer/belayout_fileprovider

and without this extension ?

can i outsourcing the backendLayouts with typoscript?

Something like: https://github.com/benjaminkott/bootstrap_package/blob/master/Classes/Hooks/Options/BackendLayoutDataProvider.php