[TYPO3-project-4-3] Inline JS in Backend

Peter Kuehn [wmdb>] peter.kuehn at wmdb.de
Sat Feb 7 00:09:53 CET 2009


hi steffen,

 > What do you think?

full ACK to all of your points!

plus if i could make a wish: would be great if you could point your 
interest first on tceforms.
in lots of projects if make use of user defined fields to get around the 
multiple limitations of the rendered forms. to get around the given js 
structure realy is pain in the a** from time to time...

lookin foreward to see more details of your thoughts
pekue



Steffen Kamper schrieb:
> Hi,
> 
> the situation with all the inline JS is really suboptimal. There are a 
> lot of functions only for comatibility reasons, fixing JS bugs is very 
> difficult, snippets are spreaded to many core files.
> 
> So i have an idea which one i would like to discuss.
> 
> What i suggest is a transparent solution:
> 
> * move inline scripts to external files
> * use 2 objects for inline:
> 
> TYPO3Backend.constants = {
>   var1 = xyz;
> };
> 
> TYPO3Backend.lang = {
>    label1 = xyz;
> }
> 
> These two obkjcts are easy to use inline in php without a big risk to 
> create new bugs.
> 
> The external files are easy to maintain, better to see what we have etc.
> Old functions could be changed with new method or calling new functions.
> Functions can be grouped by functionality like it is done in php classes.
> You get a better overview what is used, what can be reused etc.
> 
> 
> What do you think?
> 
> vg Steffen


More information about the TYPO3-project-4-3 mailing list