Support for per-browser / per-locale manifest files to capture associated GWTapplication files

[GoogleCodeExporter]

Found in Release: 1.1.1

Detailed description:

Currently there is no way to specify a manifest file per-browser,
per-locale, axes which determine the number of generated GWT application files.

As a consequence, users who would normally visit a GWT application and only
download those files they need to run the app in their browser and locale
now have to download all GWT-generated files even if it's not the correct
version for their browser / locale.

This inconvenience is slightly softened by the fact that the Gears
LocalServer only takes up one connection of the browser's two connection
limit to issue GET requests to capture these resources, but the situation
still seems less than ideal.

Given the new linker redesign, would it be possible to add a linker that
could take a look at the generated GWT application files and generate
per-browser / per-locale manifest files?

Workaround if you have one:

Either force users to download all resources or manually handroll a
post-compile script that generates per browser / per locale manifest files
and create a servlet filter that serves up the correct page with an
embedded call to the Gears LocalServer.

Links to the relevant GWT Developer Forum posts:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/338d83820
372b256

Original issue reported on code.google.com by sumitcha...@google.com on 10 Nov 2008 at 9:20

[GoogleCodeExporter]

The primary linker would have to indicate to the manifest linker which 
SyntheticArtifact(s) is/are associated with 
which CompilationResult.  Maybe some kind of notion of a FileSet is necessary 
here, when you consider the 
impact of GWT.runAsync() and having multiple js files associated with any given 
CompilationResult.

Original comment by bobv%google.com@gtempaccount.com on 10 Nov 2008 at 9:28

[GoogleCodeExporter]

شكرا لك

Original comment by SALeH-...@HOTMAil.com on 1 Dec 2010 at 9:16

[GoogleCodeExporter]

The Gears API is now deprecated.

Original comment by zundel@google.com on 28 Oct 2011 at 3:43

• Changed state: NotPlanned