[#ENGAGE-349] All JavaScript and CSS resources for Engage should be concatenated and minified to reduce server round trips and bytes delivered - Fluid Project Issue Tracker

Details

Type: Sub-issue
Status: Open
Priority: Blocker
Resolution: Unresolved
Affects Version/s: 0.3b, 0.3
Fix Version/s: 0.5
Component/s: None
Labels:
None

Similar Issues:

Show 10 results

Description

At the moment, each screen in Engage links to around 20 individual external resources, consisting of JavaScript and CSS dependencies. We should be able to get a fairly significant speed boost by concating and minifying all our resources. We should also ensure we're using a custom build of Infusion.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Michelle D'Souza added a comment - 09/Mar/10 2:55 PM

The javascript is all concatenated now but the CSS still needs to be.

Show

Michelle D'Souza added a comment - 09/Mar/10 2:55 PM The javascript is all concatenated now but the CSS still needs to be.

Hide

Permalink

Colin Clark added a comment - 09/Mar/10 3:30 PM

CSS concatenation has been an issue in Infusion as well. The issue is image URLs in individual stylesheets. If we concat together multiple stylesheets, we'll also need to move all the images around so that they remain relative to the concatenated file. It should be possible, but will require some extra code in our build process.

Show

Colin Clark added a comment - 09/Mar/10 3:30 PM CSS concatenation has been an issue in Infusion as well. The issue is image URLs in individual stylesheets. If we concat together multiple stylesheets, we'll also need to move all the images around so that they remain relative to the concatenated file. It should be possible, but will require some extra code in our build process.

~~ENGAGE-107~~	Engage should use a single app/servlet approach to reduce duplication among handlers and resolve problems with URL routing.
~~ENGAGE-70~~	The fluid-all externals are named ambiguously and the Eclipse projects for engage-server and engage-client are incorrectly named
~~ENGAGE-548~~	Draft an Engage services layer proposal for the community, proposing the use of JavaScript on the server.
~~ENGAGE-117~~	Kettle should provide a means to parameterize all file paths so that applications can seamlessly run either in Eclipse or on a standalone server
~~ENGAGE-169~~	The project name for fluid-engage-kettle is named fluid-engage-server, which doesn't match with the name of the underlying directory.
~~ENGAGE-168~~	All the Engage modules in SVN should be inside an "engage" folder, rather than just floating inside /fluid/
~~ENGAGE-402~~	Prune unnecessary JavaScript and CSS dependencies from the application
~~ENGAGE-95~~	Create Engage build scripts
~~ENGAGE-105~~	Ensure that there is only a single copy of each of the required Engage component resources (i.e. One artifactView.html file, etc.)
ENGAGE-304	Exhibition browse styling is incorrect. Corners in the list should not be rounded.

All JavaScript and CSS resources for Engage should be concatenated and minified to reduce server round trips and bytes delivered

Details

Description

Activity

People

Dates