[MGNLUI-133] Provide a dynamic mechanism for including external javascripts Created: 01/Nov/12  Updated: 27/Jun/13  Resolved: 27/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0

Type: Task Priority: Major
Reporter: Federico Grilli Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 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 - ensure external js loading order
  • what if different modules provide the same js lib with different versions, e.g. jQuery?

Generated at Mon Feb 12 08:33:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.