[TYPO3-core] sysext FLUID might generate problems

[Thomas Hucke]

Hi Peter,

thank you for that summary. I tend to agree in all points.
Actually I see the point that requests for developing extension that should 
cope with AJAX will increase in the near future.

So from my point of view it would be best having a straight forward 
blueprint for those developers supported by a few examples.
It wouldn't be easy - yeah - and it surely wouldn't fit all needs.
But saying 80 percent coverage would be much better than 20 percent or lower 
that we've got at the moment.

The earlier we got something the lower would be muddle that an admin will 
get if trying to use multiple of those AJAX extensions within one site.

... just my 2 cents.

Greets
Thomas


"Peter Niederlag"  schrieb im Newsbeitrag 
news:mailman.1459.1381301887.588.typo3-team-core at lists.typo3.org...

Hi Thomas,

On 08.10.2013 21:47, Thomas Hucke wrote:
> Hi team,
[...]
> Am I wrong here with my statement?
> Does one have a solution using the default template?

Managing javascript dependencies (regardless of TYPO3) is a mess itself
as afaik no approach could be considered generally accepted and agreed on.

As it is already a mess in standalone it seems to be pretty tough to
find a solution for TYPO3. JS handling in TYPO3 is already quite
awesome, but it leaves the dependency and management of the load order
up to the developer. This is the root cause of the problem you are
pointing at here.

I agree the fluid template could probably improved but it could also be
considered an example/blueprint to come up with your own template that
matches your requirements best. After all your PAGE object doesn't even
need to be called 'page'. ;)

Greets,
Peter