Hi guys,
I'm thinking about open an issue to make put parseWidgets: false on djConfig
initial load. This would improve the performance so much.
The fact is that dojo walk through each DOM node in a document looking for
widgets to parse, so it makes the footprint very slow.
The solution is to tell to dojo what are our widget, based on widget id. A
simple solution would be put a line in each ftl template to render some dojo
widget. Something like that in FTL:
<div dojoType="struts:BindDiv"
<#if parameters.delay?exists>
delay="${parameters.delay?c}"<#rt/>
</#if>
<#if parameters.updateFreq?exists>
updateFreq="${parameters.updateFreq?c}"<#rt/>
</#if>
<#if parameters.autoStart?exists>
autoStart="${parameters.autoStart?string?html}"<#rt/>
</#if>
<#if parameters.startTimerListenTopics?if_exists != "">
startTimerListenTopics="${parameters.startTimerListenTopics?html}"<#rt/>
</#if>
<#if parameters.stopTimerListenTopics?if_exists != "">
stopTimerListenTopics="${parameters.stopTimerListenTopics?html}"<#rt/>
</#if>
<#if parameters.refreshOnShow?exists>
refreshOnShow="${parameters.refreshOnShow?string?html}"<#rt/>
</#if>
<#if parameters.separateScripts?exists>
scriptSeparation="${parameters.separateScripts?string?html}"<#rt/>
</#if>
<#include "/${parameters.templateDir}/ajax/ajax-common.ftl" />
<#include "/${parameters.templateDir}/simple/scripting-events.ftl" />
>
<script>djConfig.searchIds.push("${parameters.id}");</script>
>From what I've seen this would be a little change that would make us improve
the performance of Struts2.
What do you think guys?
Felipe
--
View this message in context:
http://www.nabble.com/-S2--parseWidgets-should-be-false-for-better-performance%21-tf4157653.html#a11828783
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
