[TYPO3] Just a naming convention or some functinality difference
Peter Klein
peter at umloud.dk
Thu Mar 9 12:56:18 CET 2006
Hi tapio. Some info from MTB:
"However we might expect seeing the "temp." TLO in the tree, but we don't.
The reason is that the TLOs named "temp." and "styles." are unset again
after parsing the TypoScript since they are reserved as temporary object
spaces available only during parsing - not after parsing."
And I think the "lib" prefix is required if you want to use your TS objects
in TemplaVoila..
--
Peter Klein/Umloud Untd
"tapio" <tapio.markula at dnainternet.net> skrev i en meddelelse
news:mailman.1.1141904466.20651.typo3-english at lists.netfielders.de...
> Hi
>
> In typo3 manuals for using of Modern Template Building
> object are named as temp.someObject.
>
> In TemplaVoila documents lib.someObject.
>
> I have just used sometimes someObject without any prefix,
> for example
>
> subparts.editpanel < editPanel,
>
> Where
> editPanel = COA
> editPanel{
> ...
> }
>
> Does Typo3 handle objects with prefix 'temp'
> or 'lib' or object without prefix somewhat differently?
> Or is this just an issue of naming conventions?
More information about the TYPO3-english
mailing list