[TYPO3-english] DIR include of TypoScript
Philipp Gampe
philipp.gampe at typo3.org
Wed Oct 16 18:09:11 CEST 2013
Hi d.ros,
d.ros wrote:
> Nontheless the differentiation by filetype is plain not well thought.
> Even if it is implemented for now.
Ho ... who said this ;)
> A differentiation by usecase directive istead of an filextension would
> be something that makes sense here because of the problem with the
> CodeEditor software out there.
<sarcasm> Really? </sarcasm>
> so not to go with :
>
> <INCLUDE TYPOSCRIPT: source="DIR:fileadmin/default" extensions="ts-setup">
>
> but this:
>
> <INCLUDE TYPOSCRIPT: source="DIR:fileadmin/default" content="ts-setup">
>
> Would make sense.
Senseless ... you differentiate by DB field already. No need to tell the
system that it actually is inside a specific DB field.
> Someone made the comparsion to CSV files in the german list iirc. CSV is
> CSV and stays CSV. No matter what is in there.
Same is true for TypoScript. It does not matter if it is for constants,
setup, page or user, it is always parsed the same way with the very same
parser.
The only real difference is a different condition matcher for frontend and
backend.
That's is.
The parser parses the TypoScript into a PHP array and then hands it over to
the calling function, which in turn does something useful with it.
TypoScript does not care what you write there, as long as you can somehow
interpret it as TypoScript.
Same is true for CSV files. I can open any CSV file into my spreadsheet
application, because the format is important, not the content.
Best regards
--
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – Active contributor TYPO3 CMS
TYPO3 .... inspiring people to share!
More information about the TYPO3-english
mailing list