[TYPO3-core] RFC: Extend TypoScript values

Michael Stucki michael at typo3.org
Thu Feb 23 09:32:41 CET 2006


Hi Ingmar,

thanks for pushing this topic up again.

> After thinking about this for some time, I actually think we should drop
> the whole feature. I guess it would be too confusing for a lot of
> TypoScript users to understand what the difference between parser-level
> properties and interpreter-level properties are. I think it's already
> pretty difficult to explain things like "You can use all stdWrap
> properties for the TEXT content object as well, but you can't use it on
> IMAGE, only on the .stdWrap subproperty of IMAGE cObjects" and so forth...

Hmm, I'm not sure if this can be the reason for dropping new features.
Otherwise, there would probably not be any TYPO3 after all...

> IMHO adding such superglobals would just increase confusion...

Why? Even if: What do you do if something confuses you? Can only speak for
myself, but I would simply ignore it!

Those "superglobals" (call them however you like) are something that can't
be realised in a much different form. It needs to be done inside the
parser, otherwise it won't affect all properties. So there is no other way
to do it.

> I would prefer something that is clearly distinguishable from normal TS
> properties.
> 
> Maybe something like this:
> 
> <PARSER_INSTRUCTIONS>
>   addToList(plugin.tx_myext_pi1.pidList, 15,37)
>   appendString(plugin.tx_myext_pi1.logInMessage, "Regards, the staff")
> </PARSER_INSTRUCTIONS>

Hmmm. Well I'd say that this is much more complicated than the other
suggestion. It's a completely new syntax!

So, since the feature happens inside the parser, I have my next suggestion
which hopefully fits your usability requirements better:

lib.myList = 4,5,6
lib.myList.__TSparser__.addToList = 7,8

Looking forward to see your comments.

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



More information about the TYPO3-team-core mailing list