#90348PageLayoutView and BackendLayout should be refactored to separate rendering, processing and fetching of content
Description
The giant class PageLayoutView should be refactored to create smaller and more managable components with dedicated responsibilities:
- Seperate content fetching from markup output
- Seperate drawing from content processing
Furthermore it makes sense to use the BackendLayout concept as a binding class, making a PageLayoutView instance require a BackendLayout in order to render, and having BackendLayout provide the delegates that will fetch, process and render content elements.
Reviews 5
- 11.5 75357[TASK] Remove superfluous TYPO3_CONF_VARS | BE | fluidPageModule
- main 75387[TASK] Remove superfluous TYPO3_CONF_VARS | BE | fluidPageModule
- main 73366[!!!][FEATURE] Override any backend template with TsConfig
- main 64067[TASK] Remove warning from BackendLayout UnitTest after method removal
- main 63186[FEATURE] Fluid-based replacement for PageLayoutView
Related issues 11
- Feature #78450Introduce PreviewRenderer pattern
- Bug #90479New fluidbased PageLayoutView throws error, if backendLayout can no longer be resolved
- Bug #90559After Update from 10.2.2 to 10.3.0 translation button in alternative language column is missing
- Bug #90603Check in fluidbased PageLayoutView for language existence
- Bug #90605fluidbased PageLayoutView doesn't take `tables_modify` into account
- Bug #90608PageLayoutView doesn't take `tables_modify` into account
- Bug #90617Page Module: No content elements displayed with mod.web_layout.defLangBinding
- Task #90882Refactor BackendLayout and fluid page module components
- Task #90943Warning in unit tests due to BackendLayout::parseConfigurationStringAndSetConfigurationArray being removed
- Feature #96812Override any backend template with TSconfig
- Task #98095Remove superfluous TYPO3_CONF_VARS | BE | fluidPageModule