In general web app development we want to concat and minimise our sources where possible to avoid excessive requests... When looking into the possibility of doing this with UI5 apps I came across the following section of the SDK about the Dependency Resolution Tool. It says that this tool does just what I require - concatenating and minimizing and taking care of ordering of modules and dependancies.
Except for one problem - it does not explain how to use this tool. It says it can be run as an ANT task and also as a Servlet.
I'm wondering if its possible to use this tool in our build process or if its for the internal SAP build process of the UI5 libraries only?
This would be great for our own modularised code; however with the actual UI5 libraries themselves; given they are rather large it may be better to somehow async load each bit as you need it. Not sure if thats possible... yet...
Regards... Jason
Excerpt from SDK:
"Dependency Resolution Tool
The previous section contained some explanations how dependencies between modules are resolved on the client at runtime. During development, this is the typical use case. Modules can be modified in the development environment and can be deployed as individual entities to some runtime. When the client then is refreshed - and if caching is configured properly - it will reload only the modified modules.
In productive systems however, it might be desirable to bundle again several modules into one single file. This helps reducing the number of necessary roundtrips and can thereby help to reduce the impact of network latency. However, one doesn't want to loose the flexibility and transparency of the dependency management.
The UI5 framework supports this with a dependency resolution tool. It analyzes a module file and all its dependencies and creates a new file containing the original module content, as well as any required modules. It automatically avoids double inclusion of modules. The tool can be used in two ways: Either via an Ant task at build time to create a merged super module which then can be referenced in any HTML page instead of the original file or at runtime, then using a servlet on server side."