[TYPO3-dev] collaboration work & typoscript & svn

[Thomas "Thasmo" Deinhamer]

Finally I implemented a way to automatically populate
the 'layout' field with layouts based on the layouts
defined in the directory hierarchy.

The directory structure e.g. is:

Layouts/
	Default/
		setup.txt
		constants.txt
	Home/
		setup.txt
		constants.txt


The following entries will be available inside the
layout field of every page:

* Default
* Home

Besides this, a TS condition is put inside the global TS,
which will include the setup.txt and constants.txt files of
the chosen layout, on each page.

Unfortunately this is not working correctly:

[globalVar = TSFE:page|layout = 5]
<INCLUDE_TYPOSCRIPT: source="FILE: 
typo3conf/ext/EXTKEY/Resources/Private/TypoScript/Layouts/Home/setup.txt">
[global]

It only works correctly if I'm not logged in to the backend. If I am 
logged in to the backend, the condition won't take effect - only if I
tick the condition-checkboxes under the object-browser tree.

Is this working as intended? Shouldn't the boxes at least be
checked by default in the backend when logged in? No?

Thank you for help!


Thomas "Thasmo" Deinhamer schrieb:
> I played around with dynamic/automatic TS setup/constants
> inclusion and created an extension which will iterate throu
> a predefined directory recursivly, finding all 'setup.txt'
> and 'constants.txt' files, and adding them via 'addStaticFile()'
> to the 'static template' section in the backend.
> 
> The directory structure looks like this:
> 
> ext/EXTKEY/Configuration/TypoScript/:
> Layouts
>     Default
>     Home
> Pages
>     Default
>     Print
>     XML
> Setup
>     Localization
>     Adjustments
> Views
>     Sitemap
>     News
>     Contact
> 
> Inside those directories I store the files 'setup.txt'
> and 'constants.txt', which will then get included, and
> displayed with this labels inside 'static templates':
> 
>     "EXTKEY: Layouts › Default"
>     "EXTKEY: Layouts › Home"
>     "EXTKEY: Pages › Default"
>     etc.
> 
> It's also possible to include the text files
> directly into 'Layouts' or 'Views', which will
> create the following static template entries:
> 
>     "EXTKEY: Layouts"
>     "EXTKEY: Views"
> 
> The stuff is kinda flexible this way, but I'm not sure
> if I like this; I am used to template records inside
> the backend - this solution seems a bit weird for me.
> 
> Especially I don't like my 'static templates' beeing
> totally "burried" under all the other static templates,
> it's kinda 'hard work' to find my static templates in the list.
> 
> Furthermore I'm thinking about a way to dynamically import
> specific 'layout' static templates (if available), based on
> the LAYOUT field of each page in the pagetree.
> 
> Looking into this any time later...
> 
> Greetings!
> 
> 
> Krystian Szymukowicz schrieb:
>> Michael Knoll wrote:
>>> Krystian Szymukowicz schrieb:
>>>>
>>>> hi
>>>>
>>>> I'd like to ask you if you could share your experience of how do you 
>>>> do  collaborative work on bigger TYPO3 projects where more than one 
>>>> person do the changes.
>>>>
>>>>
>>>
>>> Hi Krystian,
>>>
>>> perhaps this article from Fabrizio Branca can help you a little:
>>>
>>> http://www.fabrizio-branca.de/fablog/post/why-typoscript-should-go-into-files.html 
>>>
>>
>>
>> Many thanks for that Michael.
>>
>> I've spend whole weekend moving my default TYPO3 installation based on 
>> sys_template records to the version based on files. I've put all the 
>> typoscript in two extensions "base" and "local" (which Peter Russ 
>> refered to). Lots of fun with finding the best defaults for so much 
>> pieces.
>>
>> But I have it now. "Typoscript based on files", coago performance 
>> boosted my new TYPO3 base installation.
>>
>> Thanks all for sharing their experience.
>>
>> I hope that after some months as my experience in this matter will 
>> grow up with some projects, I will share my thoughts in some article.
>>
>> -- 
>> grtz
>> Krystian Szymukowicz
>>