[Typo3-dev] Idea: Browser drivers

[dan frost]

I think this is a good idea.

you would have to do something like:

[typo3] -> [XML meta content] -> [transform for specific browser] -> 
[cache] -> [browser]


The meta content could be like

<?xml...?>
...
<table>
<tr><td>something here</td></tr>
<tr><td>
<mcml:filler-block
   height="100%" />
</td></tr>
</table>
...
<mcml:page-grid>
   <mcml:banner>..normal html..</mcml:banner>
   <mcml:row>
     <mcml:cell height="browser-height" >
       ...
        <ul>...(menu...)
	 <mcml:li
		style-class="my-class">
		Content for menu item</mcml:li>
        </ul>
       ...
     </mcml:cell>
   </mcml:row>
</mcml:page-grid>


Then, for the style classes (note that these will be implemented in CSS 
and JavaScript and whatever it takes!
<mcml:css>
<mcml:css-class name="my-class">
background-color : #123123;
</mcml:css-class>
<mcml:css-class name="my-class" ..."hover">
background-color : #f0f0f0;
</mcml:css-class>
</mcml:css>

mcml = meta content markup language!!

Actually, i think the best way to do this is outside TYPO3. Just use 
TYPO3 as standard platform for it.

It is complicated - but i think this is separating the concerns a bit more.
dan

Martin Ficzel wrote:
>> [Content for browser]-->[Browser driver]-->[Browser] 
> 
> 
> 
> 
> what do you think about making typo3 generate meta content ( maybe XML ) 
> and using standard technologies like xslt as a driver layer. i dont 
> think that creating more typoscript is a good idea.
> 
> that would mean something like this
> [ typo3 ]-->[ meta content ???XML??? ]-->[ content Transformation 
> ???XSLT???  ]-->[ Browser ]
> a structure like this would be usefull for many other cases
> 
> regards, martin