Major Feature #39887
Task #44372: Improve Frontend Rendering
Sematic grid by awareness of content
| Status: | Resolved | Start date: | 2012-08-17 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Jo Hasenau | % Done: | 0% |
|
| Category: | Frontend rendering | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.5 | PHP Version: | ||
| Votes: | 0 |
Description
I'm not quite sure if this a bug or a missing feature. I'm talking about correct semantics:
Take a 2-column subgrid as an FCE example:
<div class=“container“>
<div class=“span6“>some leftside content</div>
<div class=“span3“>some rightside content</div>
</div>
Now imagine, that nothing has been entered into the left column. If you leave the markup unchanged, the right content will move left, to the position of the empty div. You could circumvent this behaviour by faking some content („ “ or „clear.gif“), but that's not semantic at all. It is a no-go. Better render the following:
<div class=“container“>
<div class=“span3 offset 6“>some rightside content</div>
</div>
In a FLUIDTEMPLATE that would be no problem at all, since you can check for available content and create the matching markup according to the previous check.
To solve this by means of Typoscript you must know about the content of the left column when it comes to the wrapping of the right one. The problem was the very same in the TemplaVoila DS, where LOAD_REGISTER was a proper solution. I tried to find a way for register usage in gridelements for two days until I notices, that it can't work. Each column is handled individually – including RESTORE_REGISTER.
Is there currently any - maybe undocumented - feature to check for availability of content in another column? If not, a feature like that is urgently required.
History
Updated by Jo Hasenau 8 months ago
- Category set to Frontend rendering
- Status changed from New to Needs Feedback
- Assignee set to Jo Hasenau
Hi, Thomas.
If you can do it by means of a FLUIDTEMPLATE, why don't you just use it in your TypoScript setup?
Grid Elements don't force you to use a certain way of frontend rendering, since the output is based on pure TypoScript.
I never used the TypoScript based FLUIDTEMPLATE for a grid element though, so maybe I'm just missing the point here.
Updated by Jo Hasenau 5 months ago
- TYPO3 Version set to 4.5
BTW: An additional LOAD_REGISTER would help here as well.
Something like that
10 = COA
10 {
10 = LOAD_REGISTER
10.whatever = blah
10.somethingelse = blubb
20 = LOAD_REGISTER
20.somethingelse = test
30 = RESTORE_REGISTER
}
would keep whatever set to "blah" and somethingelse set to "blubb".
Updated by Jo Hasenau 5 months ago
- Status changed from Needs Feedback to Resolved
BTW: An additional LOAD_REGISTER would help here as well.
Something like that
10 = COA
10 {
10 = LOAD_REGISTER
10.whatever = blah
10.somethingelse = blubb
20 = LOAD_REGISTER
20.somethingelse = test
30 = RESTORE_REGISTER
}
would keep whatever set to "blah" and somethingelse set tu "blubb".
Updated by Jo Hasenau 5 months ago
- Parent task set to #44372