[TYPO3-core] RFC: Extend TypoScript values

[Sebastian Kurfuerst]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I just re-read the thread and I think as well that this feature is
quite important. However, I don't like the suggestions about the
markup too much yet...
I'll comment on each I find and say why I don't like them too much:

    * pidlist._addToList
      Could be mis-understood because we have _LOCAL_LANG as well for
      example. Else, I would prefer this possibility.
    * operators (+= ...)
      As already pointed out, there are very few possibilities with
      them as we are limited to += -= etc
    * xyz.pidList{addToList} = 20,21
      It is not possible to see that the action happens at parse-time.
    * xyz.pidList += (list)20,21
      This is a bit difficult to understand for the administrator why
      he needs to supply the datatype here (as it doesn't have to be
      supplied anywhere else)
    * xyz.pidList._addToList_ = 20,21
      I think it is bad practice to use an underscore at the end
    * xyz.pidList->addToList = 20,21
      It is not possible to see that this is action happens already at
      parse-time and it is hard to understand that there is no method
      called.
    * xyz.pidList.proc.addToList = 20,21
      Not bad, I think however that the "proc" directive looks
      currently too "common" - and as we already have this one in RTE
      TSconfig, it might be possible to mix it.

I would suggest the following:
    xyz.pidList.TSPROC.addToList = 20,21
Then it is clear that it is processed at parse-time, and it is not
possible to easily mix it with "proc" from RTE. And the capital
letters make sure it is not over-read easily as it is something special.

What do you think about it?
Greets, Sebastian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEAcLdygDVWNTabbkRAjh+AJ0eklc/chtgmWr29bBk2D1ZrisfSwCdERVB
4pXtZLRJhQzQdaOTaJmJjZg=
=VMf/
-----END PGP SIGNATURE-----