[TYPO3-50-general] extJS Library

[Nino Martincevic]

Hi Thomas!

+1

Although I'm not a javascript expert I do have experience with various 
JS frameworks, especially being implemented as add-ons for "rich" ui 
clients (most of it being YAGNI...).

In the last project for a company we wanted to use extJS, especially the 
UI guys were enthusiastic about it first.
But after a few weeks they went on using the good ole' JQuery again and 
some extensions.

A comment from the leading UI developer:
"It's like wanting to write a simple note and therefore first have to 
start Word 2007 and program some VBA script for being able to do it, 
just to have some cool memory-greedy widgets you'll never need..."

Nino

Thomas Allmer schrieb:
> Steffen Kamper wrote:
>> now we have extJS in core, and there are projects that want to integrate 
>> things with extJS like list-module, also some enhancements to tceforms etc.
> 
> I'm really really sorry - usually I don't like to bash something but I 
> was just trying to find out why ExtJS isn't working in any way with 
> progressive enhancement and then I found this...
> 
> http://blog.workaround.org/2008/10/22/extjs-impressive-for-the-user-painful-for-the-programmer/
> 
> I don't know ExtJS well enough to write something like this myself. But 
> this article just showed what my first impression on many things were.
> 
> Just my recapitulation of the article:
> 1) Applications do not degrade gracefully --- boomer I need that
> 2) CSS is really complicated -- bad; but just more work for me
> 3) generated HTML is huge -- bad; I need to understand it
> 4) works with pixel 0 that's ok
> 5) license - I don't know about it but it seems to be complicated
> 6) web-base forum + I like that as an additional support lvl
> 7) Lack of proper examples 0 don't know and I read js sourcecode
> 8) No customization --- boomer I want to easily modify
> 9) 90% client-side code -- I still want to do some php with FLOW3
> 10) Verbosity 0 I don't know
> 11) Debugging 0 I don't know
> 12) Size - ok it's huge I get that; it's bad, but not too bad
> 
> All in all I maybe would have stopped at the first point as this is 
> really important to me (as you can see from my article I posted)
> 
> I'm sorry but I don't think ExtJS is the right framework to build 
> TYPO3v5 - I mean its good for TYPO3v4 (nice things out of the box, 
> powerful data grids) - but to build the next best CMS the javascript 
> should be taken more seriously.
> 
> cheers
> 
> PS: I'm sure I will be flamed and if anyone can seriously negate the 
> points 1-3 and 8,9 I will apologize with all my heart. However until 
> then I hope TYPO3v5 will be build with something else.