[TYPO3-ect] Alternatives to TS

[Ries van Twisk]

Hey Elmar,

bij this email you assume that we continue using this configuration array,
only stored in a different format. If it's about that, we really cares 
about how it's stored.
However, most people I know today have problems with the configuration 
itself

The 'if' condition mentioned below is really cryptic, people would love 
to see something like this)

myMenu = HMENU
myMeny.1 = GMENU
if (myMenu.isEmpty) {
    myMenu = TEXT
    myMenu.value = sorry, emty menu
}

Also what's a big problem is the inconsistency between different 
typoscript ojects.
a stdWrap is wrap but more powerfull, yet why didn;t we change all 
normal wraps
to stdWrap? That sort of things.

Peronally it's time to make a TS2 while keeping the current TS however.
But TS2 is a real simpel scripting language. With if/then/else features 
and object oriented
for access like the ifEmpty as shown above.

Most people really understand the above method, als by re-making every 
TS object we
currently have we can clean it out and make it more consistent.



Ries




>Hello,
>
>let's proceed one of the neverending discussions "TS successor".
>
>By idea TS configures a plain PHP array. A PHP array can also be configured
>by other configuring languages i.e. YAML, XML, plain PHP, etc.
>
>Conditions:
>
>One problems of most of this languages is, that they have no structures
>that directly compares with TS conditions. The difficult thing with
>conditions is that they works on a completely differnt level. It alters not
>only one subpart of the PHP array like if-functions do, but all parts of
>the array you put between the condition. You can't do this with YAML or
>XML. You can do it with plain PHP by organizing the PHP array with
>if-else-structures.
>
>In YAML or XML you would need to spread the altering information all over
>the tree in every points that you can put between one condition in TS.
>
>How could this be soleved?
>
>A solution could be to avoid TS like conditions at all and to use TS like
>if-functions instead.
>
>
>
>Organization in templates:
>
>This is a second point discuss. TS can be organized in different templates.
>If transform the whole TS to a PHP tree first and then to XML we lose the
>Organization in templates.
>
>TS -> PHP -> XML   or   TS -> PHP -> YAML
>
>Could we technically transform template by template instead of generating
>the whole tree first?
>
>
>The trick with the dotted pair:
>
>The most typical characteristic of TS are the "dotted string array pairs".
>
>example = value 1
>example.subexample1 = value 2
>example.subexample2 = value 3
>
>This leads to a pair of string and arrray in PHP:
>
>$TS['example'] = ... some string ....
>$TS['example.'] = ... some array ...
>
>How would this pair be configured in YAML?
>
>I guess the dot can't be used in the same way as part of a name.
>
>
>Could anybody give an example.
>
>How would this pair be configured in XML?
>
>
>Regards
>
>Elmar
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>_______________________________________________
>TYPO3-team-extension-coordination mailing list
>TYPO3-team-extension-coordination at lists.netfielders.de
>http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
>
>  
>


-- 
Ries van Twisk
Freelance Typo3 Developer
=== Private:
email: ries at vantwisk.nl
web:   http://www.rvantwisk.nl/freelance-typo3.html
skype: callto://r.vantwisk
=== Work:
email: ries at livetravelguides.com
web:   http://www.livetravelguides.com