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

[tapio]

> Well. The fact is that you don't need my extensions kb_cont_table if you 
> want to nest records with TV. TV already supports that ...
> TAKE A LOOK AT THAT SCREENSHOT (AGAIN IF YOU ALREADY DID):

> http://www.think-open.org/kraftb/fce.png

I have made that kind of template.
But I thouht that each content elements are just own records and
the templates gathers them into a page basically corresponding way as in 
MTB.
I didn't think this as using nested content elements.
Is the container of 'Ylance your Account!' also a content element?

> one Column named "Content" (gray background). This is the Content-Column 
> I created in TV for the Page DS/TO templates.

I understand this

> have something strange: You have the icon of a content elemnt but the 
> content of the
> content-elments seems to be (is) two Content-Areas again (Left and 
> Right) in which you can again insert Content-Elements.

> So this "replaces" the Content-Area template in some way. Of course you 
> can have different
> templates by selecting them in the Page-Header but this way you will 
> have to first select
> DS and then TO (which you already noted and probably is "to complex" for 
> your customer :)

The view of http://www.think-open.org/kraftb/fce.png
seems in fact clearer than the corresponding view in the normal page 
module - just changing templates is a little bit more difficult.
But normally customers don't need to change templates.
If some branches need different DS I wuold put them.
But if the customer needs new branches or special pages he must have 
himself to be able to select DS and TO.
I must think which is IN OVERALL simpler. This is not so simple.

> I will pherhaps write an extension somewhen which allows a User to 
select the wanted DS/TO combination out of a list of all possible 
combination ....

Ok. If there is not too many alternative this would be useful

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

> You probably mix up "TS content object" which is something like 
> or "lib.other = CONTENT"

I thinkt that "lib.other = CONTENT" and "lib.menu = HMENU" etc. are all 
"TS content objects".

I tried last time "lib.other = CONTENT" style definition

lib.normalcontentshared  = CONTENT
  lib.normalcontentshared {
      select {
        pidInList = 41
        where = colpos=0
        andWhere = deleted=0 AND hidden=0
      }
      table = tt_content
  }

But failed to get it work. The purpose was to get ALL content element 
from defined colpos and defined page - exactly what the plugin 
'sr_include_pages' does but using just a TS for that.

> what christopher meant is that you can make a field in your DS/TO which 
> is a Typoscrip Object Path (lib.something)

I did that. I understood later what he means.
But <TypoScriptObjPath>lib.something</TypoScriptObjPath>
needs also corresponding lib.something TO.

> and then write something like:

> lib.something = RECORDS
> lib.something.table = ....

I don't understand this approach

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

> Surely. Not a specific content element ... but your "shared" content 
> like "all content elemnts on that page (in the Normal/Left/etc. column)"

that was the purpose and which failed

> Did you have a look at my extension:
> kb_tv_cont_slide
> It allows you to insert a content element in a TV Content Column (field: 
> Content Elements) and
> then have this/those Content elements in this column get "inherited" to 
> all subsequent pages with that column.> 
> That means you can insert a content element in the root-page of your 
> site in a TV column and
> all pages below will also have it ... till you insert another ...

This seems reasonable and at least in some case solve problems.
Endeed the changing DS might cause problems.
>