[TYPO3-core] RFC: Moving foreign scripts/classes/frameworks to typo3/contrib
Oliver Hader
oh at inpublica.de
Fri Jan 26 14:26:22 CET 2007
FYI: All updates done!
* Updated prototype.js to version 1.5.0
* Updated script.aculo.us to version 1.7.0
* Created new directory for external contributions typo3/contrib/
and moved files:
- typo3/prototype.js -> typo3/contrib/prototype/prototype.js
- typo3/scriptaculous/* -> typo3/contrib/scriptaculous/*
- typo3/json.php -> typo3/contrib/json.php
* Changed paths to typo3/contrib in affected core files
see ChangeSet:
http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/changeset/6599
olly
PS: I just notices that my initial message on this issue accidentally
contained an old patch-file. Good that you ignored that! ;-)
Oliver Hader wrote:
> Hi,
>
> there are currently some foreign tools "living" in the typo3 directory:
> * ./typo3/prototype.js
> * ./typo3/scriptaculous/
> * ./typo3/json.php
>
> To avoid losing outline when updates are available to some of these
> frameworks and to provide a clean structure, wouldn't it be better to
> put these external non-TYPO3 files to a separate directory like
> ./typo3/contrib/?
> This was also suggested during the IRRE review meeting in November 2006
> at the University of Applied Sciences in Hof by Ingmar and Sebastian.
> Furthermore Benjamin Back (AJAX pagetree) suggested to have common
> methods like includePrototypeLibrary(). Of course existing modules have
> to be adjusted, that those among are:
> * Kasper's "New Backend"
> * AJAX pagetree
> * Inline Relational Record Editing
>
> What do you think?
>
>
> olly
More information about the TYPO3-team-core
mailing list