[TYPO3-ect] Documenting Typoscript

[Mark Stephenson]

If we can create a specific way to document TypoScript then would it be 
possible to create a robust backend interface that can provide a series of 
options and instructions, and then write the TypoScript in the background. 
Of course, the constant editor does this for simple constants but not for 
other TypoScript. As we consider documenting the TypoScript, does it make 
sense to create the document definition in a way that would support 
creation of a tool like this? Or is that what you were thinking already?

Mark

At 11:20 AM 5/29/2006, you wrote:
>Looking forward at version 4.5 I think it could be _the_ usability
>improvement for developers if _all_ TypoScript could be validated and
>documented inline:
>
>- Any TypoScript configuration (TS templates/TSconfig) is "somehow"
>defined in the actual code and can be extracted from there by some
>viewer.
>- Semantics are fixed without this definition so that any TypoScript
>can be validated!
>As a consequence:
>- All TypoScript documentation (TSref/TSconfig/Extension documents
>with tables) is removed because its obsolete. Documentation is
>completely inline in TYPO3, depends exactly on what extensions are
>installed and it all validates so no more guesswork!
>
>
>So, now its time to go to the HCI team and suggestion this!
>
>- kasper


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Stephenson                                               |
Ginghamsburg Church                             _    /||    --+--
Director of Cyber Ministry and Technology      ( }   \||      |
                                              | /\__,=[_]      |
Director of the Web-Empowered Church         |_\_  |---|
  a ministry of the                           |  |/ |   | Technology
Foundation for Evangelism                    |  /_ |   | for the Kingdom
http://WebEmpoweredChurch.com & org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~