[Typo3-dev] Shared contents and several content area templates with TemplaVoila?

[tapio]

> It isn't more difficult. It's simply different. Basic instructions:

> 1. Build a TV page template. This should basically be s shell (i.e. it
> should be just the main container for the page)

I did, I have a little bit tested TV

> 2. Build an FCE where the DS contains the _maximum_ number of content
> areas that are possible to have on your site.
FCE?

> 3. Build multiple TOs to go with the DS from step. These will be
> your different content layouts, and by utilizing the same DS to make
> them, you can change which one is used without having to re-insert the
> actual content elements.

I did
> 4. Make sure to create icons to go with the different TOs (as shown in FTB).

I have not yet done them

> What I would _guess_ you haven't fully realized is that with FTB you
> can insert content elements INTO other content elements!

I have not done that. I have used content elements normally like in MTB.
Using content elements nested might be COMPLEX for people who just 
udpate contents. 'kb_conttable' has the possibility to use content 
elements inside content elements - but it is TOO COMPLEX!

> the first place. I'd also guess that you haven't fully grasped that
> you can use TS from TV page templates and FCE almost exactly as in any
> of the other Typo3 templating methods.

I have used TS creating some HEAD elements with TS.

>>Well the problem was that I didn't figured how to use several "columns"
>>with TV without making a new main table. 

I have figured it now. In fact the only irritating feature for
persons, whos task is just update contents is that when they want to
change the DS, they must first change DS ('Page Template Structure:') 
and after that they must select
'Use Template Design:'.
Using MTB it is necessary just to change the content area template.
Not a big difference - just a little bit irritating.

> Honestly, part of the problem is probably the use of tables for layout

yes I have used them for columns

> You'd better explain this better. You can share content in _exactly_
> the same ways with TV as with any other configuration in Typo3.
> 1. Using 'insert records' content element

I know referring by this way.
Doesnt' work-. Shared content must refer in every page manually - BAD!
Referring should be FULLY AUTOMATIC.

Lets say that I write using MTB for the pid '41' ordinary text with 
images. It will be show AUTOMATIC in all pages without any need to refer 
to it - it works like automatic generated main menu.
If customers adds new content element or deletes them, all effefs in all 
pages.
You have TWO LEFT columns, TWO NORMAL columns etc.
Shared is always visible, if the column is used.
<div id="colLeftCommon">
<div id="colLeft">This content ONLY in individual page</div>
<div id="leftsharedcontent">This content is ALWAYS visible, if the 
column 'LEFT' has been used</div>
</div>

id 'colLeftCommon' controls the layout - column has consitetn common 
layout settings.

> Available options:

> 2. Calling a TS content object from inside an (or every) FCE

???

> 3. Calling a specific content element (probably stored in a sysfolder)
> from a FCE with TS.

Doesnt' work - you can't know what it the content element. Custormer has
the possibility to delete content elements.

> 4. Calling a TS content object from inside a TV page template

Doesnt' work - you can't know what it the content element. Custormer has
the possibility to delete content elements.

> 5. Calling a specific content element from inside a TV page template with TS.


Doesnt' work - you can't know what it the content element. Custormer has
the possibility to delete content elements.