[TYPO3-50-general] a JS framework for TYPO3 5.0 and FLOW3

Martin Kutschker martin.kutschker-n0spam at no5pam-blackbox.net
Sat May 3 10:47:22 CEST 2008

Robert Lemke schrieb:
> Hi Martin,
> Am 27.04.2008 um 11:52 schrieb Martin Kutschker:
>> I have thought a bit about the JS problem after UI discussion on the 
>> list.
>> My conclusion is that TYPO3 5.0 or FLOW3 would benefit from a JS
>> framework that accompanies it. The base JS code could be independent,
>> but there would be some add-on code that ties PHP and JS together.
> Generally I would like to create a JS code generating solution which
> decouples the consumer code (extensions etc.) from the actual JS framework.
> I fear that we won't be able to go so far as GWT but something smaller
> and more pragmatic, tailored to what we need could be the solution.
> What I would like to achieve is that a FLOW3 / TYPO3 v5 developer only
> has to cope with PHP and that all UI widgets exist as true PHP classes.
> Currently I don't think that it's possible to create a real live connection
> between the JS objects and the PHP objects (COMET-like) but I'm convined
> that some polling mechanism which creates a messaging channel between
> server and client will be good enough to solve our requirements.


> As for the client side I would like to create as few business logic and
> as few JS code as possible. Although it might have advantages 
> performance-wise,
> I think that it's more important for us to keep the whole logic at one
> (PHP) place.
> My favorized framework currently is ExtJS. I have tried out a dozen other
> frameworks during the last year and I think that ExtJS helps us most with
> what we need (a rich user interface for the backend).

Though I was (and I'm still) have the opinion that creating everything 
from scratch was overambitious (TYPO3 5.0 could have been produced 
faster with a more pragmatich approach), I feel now that adopting a 
frameset will lead to trouble.

The JS of widget frameset will be transparent to the PHP extension 
developer, but it won't be for the Core developer. New code will be 
integrated better (see paradigm discussion in my thread starter), it 
will grow with the PHP code (who know where the extJS devs head to) and 
it avoids any licening troubles (same licence end relicence option for 
all of the code).

Use extJS as a starter and pick the raisins from the others. Mix them 
well, adapt them to DDD etc and reformat them all according to the 5.0 
CGL and - tata - here you are. :-)


More information about the TYPO3-project-5_0-general mailing list