[Typo3] Coding guideline: When en when NOT to use/build extensions?
dan frost
dan at danfrost.co.uk
Thu Apr 28 16:02:45 CEST 2005
It is quite slow!! Use php5 - it is much, much faster.
Meinte van't Kruis wrote:
> Hey, who said anything about sharing :) (j/k). I personally don't like
> the xml parser in t3lib much, but perhaps I should take a second look
> at it. It's just that the parser would be used for multiple
> extentions, and it seems making extentions that make use of other
> extentions(or extend it even) seems uncommon practice (or is it?).
>
> thx
>
> On 4/28/05, Kraft Bernhard <kraftb at gmx.net> wrote:
>
>>Meinte van't Kruis wrote:
>>
>>
>>>[...] building an XML parser [...]
>>
>>There's already a XML parser in Typo3:
>>
>>t3lib_div::xml2array($xml);
>>
>>t3lib_div::array2xml($array, ...)
>>
>>If you supply functionality which is not already in the T3 core you should most probaly code it as
>>extension as this is the only way how T3 software get's distributed ...
>>
>>Of course you could write a little script, put it on your website and tell the people: Take it, insert
>>this TS and it will work for you .... but that is far of from any T3 standars ...
>>
>>greets,
>>Bernhard
>>--
>>Kraft Bernhard
>>MOKKA Medienagentur <http://www.mokka.at>
>>T: +43 - 1 - 895 33 33 - 50
>>_______________________________________________
>>Typo3-english mailing list
>>Typo3-english at lists.netfielders.de
>>http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>>
More information about the TYPO3-english
mailing list