[ 
http://jira.magnolia-cms.com/browse/MGNLUI-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Federico Grilli updated MGNLUI-133:
-----------------------------------

    Description: 
We currently hardcode paths to jquery.js and jquery.transition.js used in 
{{m-ui-vaadin-common-widgets}} in 
{{info.magnolia.ui.vaadin.integration.servlet.MultipleBrowserWindowsApplicationServlet.writeAjaxPageHtmlVaadinScripts(..)}}.
 Of course, we need a more flexible way of including external js which could be 
provided by custom widget modules as well. 

Notes:
- place external js files into {{VAADIN/js}} (use gwt.public folder only for 
resources needed by GWT compiler, i.e. those used by ClientBundle)
- aggregate and minify all the external js files and ensure external js loading 
order
-- we could use require.js here http://requirejs.org/
- what if different modules provide the same js lib with different versions, 
e.g. jQuery?
   

  was:
We currently hardcode paths to jquery.js and jquery.transition.js used in 
{{m-ui-vaadin-common-widgets}} in 
{{info.magnolia.ui.vaadin.integration.servlet.MultipleBrowserWindowsApplicationServlet.writeAjaxPageHtmlVaadinScripts(..)}}.
 Of course, we need a more flexible way of including external js which could be 
provided by custom widget modules as well. 

To take into consideration:
- place external js files into {{VAADIN/js}} (use gwt.public folder only for 
resources needed by GWT compiler, i.e. those used by ClientBundle)
- aggregate and minify all the external js files and ensure external js loading 
order
-- we could use require.js here http://requirejs.org/
- what if different modules provide the same js lib with different versions, 
e.g. jQuery?
   


> Do not hardcode path to external javascripts
> --------------------------------------------
>
>                 Key: MGNLUI-133
>                 URL: http://jira.magnolia-cms.com/browse/MGNLUI-133
>             Project: Magnolia UI
>          Issue Type: Task
>      Security Level: Public
>            Reporter: Federico Grilli
>            Priority: Major
>             Fix For: 5.0 Alpha1 - Backlog
>
>
> We currently hardcode paths to jquery.js and jquery.transition.js used in 
> {{m-ui-vaadin-common-widgets}} in 
> {{info.magnolia.ui.vaadin.integration.servlet.MultipleBrowserWindowsApplicationServlet.writeAjaxPageHtmlVaadinScripts(..)}}.
>  Of course, we need a more flexible way of including external js which could 
> be provided by custom widget modules as well. 
> Notes:
> - place external js files into {{VAADIN/js}} (use gwt.public folder only for 
> resources needed by GWT compiler, i.e. those used by ClientBundle)
> - aggregate and minify all the external js files and ensure external js 
> loading order
> -- we could use require.js here http://requirejs.org/
> - what if different modules provide the same js lib with different versions, 
> e.g. jQuery?
>    

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to