A pattern is emerging where we use a "resources" public package to store "baked
in" resources, and /war/... for other resources. In the HTML platform there's
essentially no difference between these two kinds of resources (except that
baked-in resources get automatically added to your appcache manifest so that
they're more likely to be available offline).
For Flash and Android, however, we need to ensure that baked-in resources get
automatically bundled with the .apk/.swf.
Original issue reported on code.google.com by jgw@google.com on 27 May 2011 at 12:00
Original issue reported on code.google.com by
jgw@google.com
on 27 May 2011 at 12:00