[TYPO3-english] COA inside another COA - is it a wise thing?

[Riccardo De Contardi]

Hello Bernhard and thank you very much for your answer!
Well.. my requirements are quite simple: it all started when I realized  
that a lot of time ago, when I was a Typo3 rookie, I've defined a lot of  
objects in my Templavoila Data Structure:

For example, given an HTML  like this:
<h2>My menu title</h2>
<ul>
   <li><a href="">link1</a></li>
   ...
</ul>

I defined a lib.mymenutitle mapped on the <h2> AND a lib.mymenu mapped on  
the <ul>

As today I'm more skilled on T3, I'd like to have less objects defined in  
DS (I guess it should be better for performances, am I right?)
using  - of course - COA:

lib.mymenu = COA
lib.mymenu{
	#Title
	10 = TEXT
	10.value = My Menu Title
	10.wrap = <h2>|</h2>

	20 = HMENU
	20{
	#et cetera
}
}

Thanks again for your answer

In data 10 maggio 2010 alle ore 16:51:11, Bernhard Kraft  
<kraftb at think-open.at> ha scritto:

> Riccardo De Contardi wrote:
>> A little "odd" question about typoscript:
>>  Is it "wise" to have a COA inside another COA? I mean Something like:
>
> There's nothing which speaks against this - it depends on what you  
> required.
> It sometimes makes sense to put a COA_INT into a normal COA, so part of  
> the
> generated content does not get cached.
>
> It also makes sense to put a normal COA into a COA_INT, as you would  
> probably
> not want "double-caching" which is what you would get if you put a  
> COA_INT into
> another COA_INT (don't even know if this works flawlessly).
>
>
> greets,
> Bernhard


-- 
--------------------------------------------
Riccardo De Contardi - Web Developer
B Human Srl - www.bhuman.it
Via Canzio, 15 - 20131 Milano
TEL +39-02-20.23.271 - FAX +39-02-20.240.561
--------------------------------------------