[TYPO3-english] DIR include of TypoScript

[Nico Deblauwe]

Hi Ralf, Soeren,

*>> ... it could be very useful to standardize the file extensions that
are normally to be used.*
+1 for this idea. Actually anything that helps differentiating "visually"
between the different kinds of TypoScript that are available, is welcome.
E.g. something as simple as a different color in the margin (easy to
realize with the different file extensions I guess, more difficult if it
should be deducted from the content dynamically, e.g. in mixed files).

*> ... it's already known under the same name: TypoScript*
.. exactly that all four types of TS have the same name (namely TypoScript)
leads to a lot of confusion for beginning (and semi-experienced) TYPO3
developers. It has cost me already a lot of lost time, trying to track the
subtle differences when trying to get something done. Especially when it is
put in a file and no longer is added to a page, or user record in the
backend.

*> I will much more hope that people can structure there files in to
directories*
This is also a very useful suggestion, but I prefer it in combination with
Ralf's suggestion as this ads a more rigid structure possibility.

My five cents,

Nico



On Tue, Oct 8, 2013 at 8:42 AM, Søren Malling <soren.malling at gmail.com>wrote:

> Hi Ralf,
>
> Interesting suggestion. I will much more hope that people can structure
> there files in to directories ex.
>
> Resources/Private/TypoScript/Frontend/[Content,Extensions,Page]
> Resources/Private/TypoScript/Backend/[Rte,Tables]
>
> Or something similar.. And have them included inside a organized "main"
> file.
>
> Introducing many new file extensions is not really helping anything, as the
> syntax is 90% the same (God, I would love stdWrap in the backend!) and it's
> already known under the same name: TypoScript
>
> Best regards
>
> Søren
>
>
> On Tue, Oct 8, 2013 at 12:48 AM, Ralf-Rene Schröder <ralf.rene at online.de
> >wrote:
>
> > hello together...
> >
> > for the upcomming 6.2 not only individual files can be included as
> > typoscript, but whole directories (even recursively) could be used, and
> > thereby then a file extension (such as txt or ts) can be selected to
> > used to be ...
> >
> > i think at this time it could be very usefull to standardize the
> > fileextension that are normaly to be used... so everybody can realize
> > for what target the TypoScript is...
> >
> > for every type of use (and for the upcoming ts2) an own filetype
> > (theese types could be registered as alowed file types by standard)
> >
> > .ts ... Typoscript (no special type)
> > .ts1 ... Typoscript normal style, without any include target
> > .ts1c ... Typoscript for files targeting to be included in TSconstants
> > .ts1s ... Typoscript for files targeting to be included in TSsetup
> > .ts1p ... Typoscript for files targeting to be included in pageTSconfig
> > .ts1u ... Typoscript for files targeting to be included in userTSconfig
> > .ts2 ... Typoscript-2 upcoming style for flow,
> > .ts2c ... if there ist somthing comparable for constants
> > .ts2s ... if there ist somthing comparable for setup
> > .ts2p ... if there ist somthing comparable for pageTSconfig
> > .ts2u ... if there ist somthing comparable for userTSconfig
> >
> > if i get here some +1 i will post a feature request for the upcoming 6.2
> > LTS version...
> >
> > --
> > image[FORMAT] - Ralf-René Schröder
> > http://www.image-format.eu ... Wir geben Ihrem Image das richtige Format
> > _______________________________________________
> > TYPO3-english mailing list
> > TYPO3-english at lists.typo3.org
> > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>