[Typo3-dev] Syntax / Error highlighting TypoScript
Kasper Skårhøj
kasper at typo3.com
Wed Apr 14 11:16:33 CEST 2004
I totally agree with you Georg
It would be great having such a thing and I have been thinking about it
often. It is probably one of the greatest helper applications for
newbees you could imagine - and it would even enable us to build a
fullfledged frontend for failure-proof construction of TypoScript
Templates.
However I don't have time to do it but I would support anyone wanting to
do this morally. I think the idea is great and the need is there.
You ask for a complete list of properties that can be used for the
evaluation. This should (in my vision) come from the manuals. Currently
there is for the "TS browser" thing (which allows you to select
properties in the backend via the "TS" icon) a database of properties
and some kind of notification placing them in the tree. This information
is already coming from the manuals and it comes from TER - which means
it will take all properties supplied from extensions with it! What we
need to make this complete is a more well defined notification so we can
actually code a semantic checker-routine.
In short, basing the semantic check on the property tables from the
manuals is great because:
- We already parse the property tables via TER and for all extensions
(which can all supply options for their own plugins and what-not)
- By using manuals there is ONE place to update the description and
property list (single-source)
What we need is:
- A strict definition of how the property tables is build, mainly the
first two columns is important
- A strict definition of how the nesting of objects can be defined in
these tables.
My 2-øres
- kasper
More information about the TYPO3-dev
mailing list