summaryrefslogtreecommitdiffstats
path: root/gerrit-plugin-gwtui
Commit message (Collapse)AuthorAgeFilesLines
* Set version to 2.7v2.7Dave Borowitz2013-09-181-1/+1
| | | | Change-Id: I49a7fc97fd6d4f199c25774faa50ec4a826ae64a
* Start 2.7 developmentShawn Pearce2013-03-211-1/+1
| | | | Change-Id: I08dc590bb1f62af67d88eb11313d5d4cfe2423c4
* Bump GWT version to 2.5.0Dariusz Luksza2012-11-171-2/+3
| | | | | | | | Additional minor changes to ChangesApi was required. This version bump could fix problems with IE9. Change-Id: I19af7125c696ef9a962f10260feb73c095d2b11d Signed-off-by: Dariusz Luksza <dariusz@luksza.org>
* Do not call onModuleLoad() second timeDariusz Luksza2012-11-121-6/+0
| | | | | | | | onModuleLoad() method is automatically called by GWT framework. Calling it once again in PluginGenerator cause double plugin initialization. Change-Id: I86b179f0a2da99121c74d1c095281bdd7de30636 Signed-off-by: Dariusz Luksza <dariusz@luksza.org>
* gerrit-plugin-gwtui/gerrit-war: Enable lifecycle plugin in pom.xmlDavid Pursehouse2012-10-291-0/+44
| | | | | | | | | | | | | | | | | Due to changes in the m2e Eclipse plugin for Indigo (3.7), plugin execution no longer happens directly, but rather must be configured through m2e's lifecycle-mapping plugin. In order for a plugin to be invoked within Eclipse, a pluginExecution must be defined in the lifecycle-mapping plugin corresponding to the execution tag in the plugin definition itself. To achieve this, a new section is added in the build section of the POM files. See http://goo.gl/2WCNW for details. Change-Id: Id37cd53bea434cb9ecf8f509de8da558516e8303
* JavaScipt and GWT based UI plugin supportDariusz Luksza2012-10-2110-0/+574
Adds support for extending Gerrit's web UI using either pure JavaScript or GWT compiled with a modified CrossSiteIframeLinker. To add code to the web UI plugins should bind WebUiPlugin to either GwtPlugin or JavaScriptPlugin in their plugin's Web-Module. This tells the UI bootstrap code where to find additional JavaScript to inject into the page before displaying content. For a GWT based plugin: * com.google.gerrit.client.Plugin class should be extended, * inheritance from com.google.gerrit.Plugin should be added to gwt.xml, * subclass of client.Plugin should be set as entry point, * dependency from com.google.gerrit/gerrit-plugin-gwtui should be added to pom.xml, * webappDirectory option for gwt-maven-plugin should be set to ${project.build.directory}/classes/static For JavaScript based plugins the source code should be put into the static/ directory of the plugin's JAR file. Currently there are no extension points for either JS or GWT plugins to interact with. Some will be added in a future commit. With this commit only simple modification of the UI is possible, for example calling window.alert() or adding extra elements to page contents based on the existing element ids. Change-Id: I3558991ba4a1477d6cde64eb0a761a7e4c399ec3 Signed-off-by: Dariusz Luksza <dariusz@luksza.org>