[TYPO3-content-rendering] A new approach to Content Rendering

JoH info at cybercraft.de
Wed Jul 6 10:59:50 CEST 2005


> yes. I still dont understand how you want to do that when the user
> makes different "wraps" in the themplate.
>
> where are you going to apply what style? and I am not talking about
> the static CSS...
> how do you know what margin or padding goes where if you dont even
> know what the template looks like...you said its impossible with my
> "static" template, so now you even want to make the templates
> dynamic... :D

I don't have to "know" what goes where - I just have to deliver it and the
user will "know".
For each default template we will know exactly where each value has to be
placed since we will be the creators ot those templates.
But you are talking about situations where the user creates his own HTML
template manually.
In this case the user will be responsible for the manual creation of an
appropriate stylesheet too that still can use the same markers I described
before.
And he will have to take care that the HTML templates fits the needs of the
content element. i.e. for a textpic element he has to make sure that there
is at least one caption for each image possible and at least one place for
header, bodytext and imageblock together with a looped subpart for the
single images to make it work properly.
He creates the CSS file containing the basic classes and features and TYPO3
will happily deliver all the different widths, heights, border widths,
floats or whatever - but the user will decide which of them he needs and
where he wants to use them. Additionally he can use TypoScript to modify the
values before they are inserted or additional CSS files + TypoScript to add
parameters that are not generated by TYPO3. So any kind of additional
template will always be semiautomatic and the user will have to stick to
some basic rules.

I really don't see the problem here.
We just have to make sure that any possible numeric or boolean value is
created and filled into a special marker.
Numeric values would be things like width, height, margin and padding
Boolean values would be things like float:left, clear:left

If there is a marker in the CSS template the value is inserted and used -
else it will be ignored.
I don't see the complicated part here.
You say your approach for automatic calculation of even negative margins for
single elements can be realized.
Well - this one will be exactly the same ;-p

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
openBC: http://www.openbc.com/go/invuid/Jo_Hasenau





More information about the TYPO3-project-content-rendering mailing list