[Typo3-dev] Make configuration simple
dan frost
dan at danfrost.co.uk
Thu Oct 13 13:23:40 CEST 2005
> Have a look at those XML files that are used to configure the flexforms in
> the BE, compare them to a clean notation of some basic TypoScript snippets
> and you see what I mean.
> I think it's just vice versa: TypoScript should replace other systems in the
> near future.
>
Unlikely - TypoScript has no structure (it has
syntax) whereas a XML with a good Schema / DTD
does. Having a strong, check-able structure makes
in much, much easier to learn something and debug it.
Anyway, my point was going to be: I think that the
TYPO3 community are guilt of a little too much "i
know this, and i'm quick at it, therefore it's
best". TypoScript IS brief and neat. However,
Python is more brief than PHP (or Java), but Php
is often nicer to do things in than Python simple
because the verbosity helps us read it.
Also, I think that the TYPO3 community needs to
get away from the idea that the interface should
be the same as the language. Why not create (or
adopt) an XML-based configuration language which
is used via a graphical interface; or make the
TypoScript syntax sit over a more standard (ok, by
standard I mean XML) language which can be checked
by existing tools (xmllint, dtds etc) for
validity/correctness.
Regards,
dan
More information about the TYPO3-dev
mailing list