You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Korbinian Bachl (JIRA)" <ji...@apache.org> on 2007/08/31 21:35:19 UTC

[jira] Created: (WICKET-912) shink of resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js // general JS in wicket // JS loading by loaderclass

shink of resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js // general JS in wicket // JS loading by loaderclass
-----------------------------------------------------------------------------------------------------------------------------------------

                 Key: WICKET-912
                 URL: https://issues.apache.org/jira/browse/WICKET-912
             Project: Wicket
          Issue Type: Improvement
    Affects Versions: 1.3.0-beta3, 1.3.0-beta2, 1.3.0-beta1
         Environment: general all wicket 1.3+
            Reporter: Korbinian Bachl


Currently, when using basic ajax, a JS resource like "resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js" is included in head and called - this should short and/ or be replaced by fewer JS calls.

An aproach like the one the YUI team made would be much nicer in regards to header-size and downloaddata. So i would recommend to have wicket taken the same way as YUI and instead of adding several JS paths to the header only 1 loader class and this class then could feed the rest (same as for YUI in 2.3.0 now).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (WICKET-912) shink of resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js // general JS in wicket // JS loading by loaderclass

Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524297 ] 

Matej Knopp commented on WICKET-912:
------------------------------------

And what would be the benefit of this? What's the difference between rendering multiple references or having one reference and load the other using XmlHttpRequest. Actually, this approach is even more expensive. Also by default, there is only one javascript file - wicket-ajax.js, unless you are in development mode, but in development mode it doesn't matter.

Such approach might make sense for Javascript only toolkits, such as YUI, but it's not really justified for web framework like wicket.

> shink of resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js // general JS in wicket // JS loading by loaderclass
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-912
>                 URL: https://issues.apache.org/jira/browse/WICKET-912
>             Project: Wicket
>          Issue Type: Improvement
>    Affects Versions: 1.3.0-beta1, 1.3.0-beta2, 1.3.0-beta3
>         Environment: general all wicket 1.3+
>            Reporter: Korbinian Bachl
>
> Currently, when using basic ajax, a JS resource like "resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js" is included in head and called - this should short and/ or be replaced by fewer JS calls.
> An aproach like the one the YUI team made would be much nicer in regards to header-size and downloaddata. So i would recommend to have wicket taken the same way as YUI and instead of adding several JS paths to the header only 1 loader class and this class then could feed the rest (same as for YUI in 2.3.0 now).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (WICKET-912) shink of resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js // general JS in wicket // JS loading by loaderclass

Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp resolved WICKET-912.
--------------------------------

    Resolution: Won't Fix

> shink of resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js // general JS in wicket // JS loading by loaderclass
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-912
>                 URL: https://issues.apache.org/jira/browse/WICKET-912
>             Project: Wicket
>          Issue Type: Improvement
>    Affects Versions: 1.3.0-beta1, 1.3.0-beta2, 1.3.0-beta3
>         Environment: general all wicket 1.3+
>            Reporter: Korbinian Bachl
>
> Currently, when using basic ajax, a JS resource like "resources/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax.js" is included in head and called - this should short and/ or be replaced by fewer JS calls.
> An aproach like the one the YUI team made would be much nicer in regards to header-size and downloaddata. So i would recommend to have wicket taken the same way as YUI and instead of adding several JS paths to the header only 1 loader class and this class then could feed the rest (same as for YUI in 2.3.0 now).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.