[TYPO3-dev] alwaysActivePIDlist

Michael Stucki michael at typo3.org
Wed Oct 25 00:43:16 CEST 2006


Ingmar Schlecht wrote:

> Martin Kutschker wrote:
>> Maybe we could add a "value-copy" into TS. Or we could create a function
>> for it:
>> 
>> obj1.prop := objVal(obj2)
> 
> Good idea, this would be much faster then executing stdWrap on all
> properties.
> 
> I'd call it cObjVal() though.

I like the idea but think this won't be possible:

TypoScript arrays are compiled by t3lib_tsparser. It does not create any
content, but just creates a huge array with keys ([page], [page.], ...) and
values.
This is the _only_ place where every TypoScript code is parsed by, so the
value-copy feature (or global stdWraps, whatever) needs to be placed right
here.

Much later, after the TSparser has finished his work, the tslib_content
object or some extension are going to request a certain part of this array
(eg. "plugin.tx_myext") and translate it into content.

Now imagine that you would like to copy the output value of
"plugin.tx_myext" into "lib.myobj". This will fail because the plugin
object is not parsed at that time.

I even think that the whole tslib_cObj is not loaded at that time, but I
didn't check this now...


There is a limited possibility for implementing common stdWrap features like
"wrap", "override" or "crop". The := operator provides a basic framework
for this, but it is far from being complete.

Anyway, a complete stdWrap support at TSparser stage is not possible without
completely changing the way how TypoScript code is parsed into content.

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/




More information about the TYPO3-dev mailing list