forcedotcom/idecore — pull request #59 by KeithClarke (2014-08-29 17:01:16+00:00)
Title: Edit and deploy contents of static resources

This pull request is an implementation of "Edit and deploy contents of static resources" #14.

Most of the work is in a new plug-in **com.salesforce.ide.resourcebundles** with minor changes to the core plugin to allow a couple of boolean project preferences to be saved. There is also a **com.salesforce.ide.resourcebundles.test** plugin that contains JUnit Plug-in Tests that hopefully your build framework can run.

Its not ideal to have this dependency, but these changes only make sense if **both of these are also done**:
* Race condition in OnlineBuilder for staticresources and perhaps other components #44
* Changes to monitor only SF files in `/src/` folder #57

The UI is affected in these ways:
* A new "Force.com" project property page called "Resource Bundles" provides the options to "Automatically un-ZIP static resources to resource bundles" and "Automatically ZIP resource bundles to static resources". When these are turned on (they presently default to on) changes to one format - the zipped or the unzipped - will result in the other format being generated to be consistent. So for example an edit and save of a JavaScript file in the resource bundle will update the static resource and if the online builder is turned on will deploy that static resource to the org.
* There are also context menu items for "Un-ZIP to Resource Bundle" and "ZIP to Static Resource" to force the process manually. If someone was building their resource bundle content from scratch, they may want to turn off the automatic updating and use the manual process at specific times.
* The unzipped version is always output in a folder called "resource-bundles" (the same name MavensMate uses) in the project root.
* Where a new resource bundle folder is added, a basic application/zip .resource-meta.xml file is automatically created.