[TYPO3-english] R: collaboration & typoscript & svn

[De Contardi Riccardo]

Hello!

I'm using nearly the same "philosophy" of yours!

I usually write the template TS into separate files with a naming convention like:

TSTYPE.PAGE.PURPOUSE.t3s
TSTYPE.PAGE.LIB.NAMEOFTSOBJECTINTEMPLAVOILA.t3s
TSTYPE.PAGE.EXT.NAMEOFEXTENSION.t3s

e.g.

setup.home.configuration_base.t3s
setup.home.lib.mainMenu.t3s
setup.home.ext.tt_news.t3s
config.home.crawler.t3s

And so forth.


**************************************
Riccardo De Contardi
 
B Human Srl - www.bhuman.it 
Via Canzio, 15 - 20131 Milano
Tel +39.02 20 23 271 - Fax +39.02 20 240 561
-----Messaggio originale-----
Da: typo3-english-bounces at lists.typo3.org [mailto:typo3-english-bounces at lists.typo3.org] Per conto di Krystian Szymukowicz
Inviato: venerdì 30 ottobre 2009 11.27
A: typo3-english at lists.typo3.org
Oggetto: [TYPO3-english] collaboration & typoscript & svn


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.

I am just on the beginning of collecting ideas. Right now I have:

1) SVN

2) Moving all "template typoscript" from template records to files.

3) Moving all "page typoscript" from template records to files.

4) Moving all "user typoscript" from template records to files.

5) Leaving one template record in database. This template record will 
contain constants with reference to page uids typical to page tree which 
can be different at local, development and production servers.
For example *constants* section could have:
a) at local server
plugin.tt_news.pid_list = 88
plugin.tx_myplugin.page_with_content_uid = 33
...
b) at development server
plugin.tt_news.pid_list = 884
plugin.tx_myplugin.page_with_content_uid = 334
...
c) at production server
plugin.tt_news.pid_list = 188
plugin.tx_myplugin.page_with_content_uid = 1243
...

6) I'd like also to separate default "page TS", "user TS", "template TS" 
as extension. Something like "cbstarter" extension of Michael Cannon.
So this will be standard piece of TS code used in all my projects and it 
will be extended/overwritten by TS settings specific to implementation.




Now my doubts are:
1) Do you put all "template TS" into one big file ? Or you have separate 
file for:
a) "config.ts"
b) "plugins/tt_news.ts"
c) "plugins/css_styled_content.ts"
d) "plugins/...
e) "subparts/main-menu.ts"
f) "subparts/footer.ts"
g) "subparts/...
etc.

Working with one big file is IMO not effective and could bring svn 
conflicts, but is there any drawback of separating "template TS" into 
10-15 small files ? What is your opinion?



What else do you propose to make that collaborative work more efficient?
Redmine? :)



--
grtz
Krystian Szymukowicz
_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english


Chi riceve il presente messaggio e' tenuto a verificare se lo stesso non gli sia pervenuto per errore. In tal caso e' pregato di avvisare immediatamente il mittente e, tenuto conto delle responsabilità connesse all'indebito utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso contenute, voglia cancellare l'originale e distruggere le varie copie o stampe.

The receiver of this message is required to check if he/she has received it erroneously. If so, the receiver is requested to immediately inform the sender and - in consideration of the responsibilities arising from undue use and/or disclosure of the message and/or the information contained therein - destroy the original message and any copy or printout thereof.