[TYPO3-v4] Idea to speed up the backend

Kay Strobach typo3 at kay-strobach.de
Thu Jun 16 12:22:46 CEST 2011


Hello Ernesto,

i had a small talk to Steffen - managedIframes is not an Option at all.

Just a quote:
> managedIframe kommt imho nicht in Frage - es löst auch nicht das problem mit dem Ext namespace. ich habe darüber mit den sencha jungs geredet
> [12:20:38] Steffen Kamper: hatte ich Ernesto aber erzählt

Regards
Kay


Am 16.06.2011 12:16, schrieb Kay Strobach:
> Hello Ernesto,
> 
> sounds good.
> 
> Hope you mean and it's the same like[1]:
> 
> - http://code.google.com/p/managediframe/
> - http://code.google.com/p/managediframe/wiki/ManagedIframeFAQ
> 
> This sounds good enough to give it a try.
> BUT this won't solve the main problem, that too much data is transfered
> in many modules which slows down the process (e.g.listmodule).
> 
> The license makes me gray hair [2]:
> 
>>  * License: ux.ManagedIFrame, ux.ManagedIFrame.Panel, ux.ManagedIFrame.Portlet, ux.ManagedIFrame.Window  
>>  * are licensed under the terms of the Open Source GPL 3.0 license:
>>  * http://www.gnu.org/licenses/gpl.html
>>  *
>>  * Commercial use is prohibited without a Commercial Developement License. See
>>  * http://licensing.theactivegroup.com.
> 
> Other Parts are simply licensed as MIT [3].
> 
> 
> I think the best solution for longterm evolution is to switch to
> extdirect with cards which do not contain any frames, but only panels
> ..., which should be easy enough for many modules ;)
> 
> Regards
> Kay
> 
> [2]
> http://code.google.com/p/managediframe/source/browse/trunk/source/exp/mif.js
> [3]
> http://code.google.com/p/managediframe/source/browse/#svn%2Ftrunk%2Fsource%2Fexp
> 
> Am 16.06.2011 12:01, schrieb Ernesto Baschny [cron IT]:
>> Kay Strobach schrieb am 15.06.2011 10:42:
>>> Hello guys,
>>>
>>> wouldn't it be very usefull, if the typical JS files used for the core
>>> ExtJS) are loaded at the end of the login page.
>>>
>>> This way the login can be done normally and as fast as current - while
>>> the JS files are loaded in the background ;)
>>> This way we should save up to 5s during the switch from typo3/index.php
>>> to typo3/backend.php ;)
>>
>> Hi Kay,
>>
>> have you talked to Steffen or though about trying to use
>> Ext.ux.ManagedIFrame to load ExtJS in the iFrames to speed their loading up?
>>
>> In the forums there is this post [1], with this quote:
>>
>> "Load the Extjs library (or any frameWork) once, and apply it to
>> multiple frames without modifying the iframes' source document."
>>
>> Which seems quite exactly what we need to still load our "old modules"
>> in the IFRAME and have them use ExtJS functionality but without the
>> burden to reload ExtJS on every single click.
>>
>> Any chance for an ExtJS expert (or maybe you, Kay) to take a closer look
>> at it?
>>
>> Thanks!
>>
>> Cheers,
>> Ernesto
>>
>>
>> [1]
>> http://www.sencha.com/forum/showthread.php?16590-ux.ManagedIframePanel-%281.05-1.0-baseline-closed%29&p=120384#post120384
> 
> 


-- 
http://www.kay-strobach.de - Open Source Rocks

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org


More information about the TYPO3-project-v4 mailing list