Plugins development modes

The DomeoClient is a Google Web Toolkit (GWT) application that can be extended by developing new plugins. Here are some instructions on how the Plugins can be created, integrated and enabled/disabled.

Domeo GWT Client can be ran in two modes:

1. hosted mode (preferred mode for developing Domeo Client plugins): The STS IDE runs a server that services the Domeo. HTML page, servlets with services mockups and the compiled GWT code. When you load Domeo.html in the browser the first time you will notice a 10 seconds delay as it is compiling all the Java code into JavaScript (JS). The hosted mode is helpful as basically you are running the GWT without the need to spin up an entire server. Most importantly, through the GWT browser plugin, you get incremental compilation of the GWT Jave code into JS. So every time you change some code, a reload is sufficient to test the new lines (see the compiled mode to notice the difference).

   • Setting up the DomeoClient development environment
   • Set up target pages to test annotation hosted mode
   • Plugins architecture
   • Plugins development
   • Once the hosted mode is running, one can use an empty scaffolding to develop plugins (more directions pending).

2. compiled mode: This is the mode that is used when the application is deployed in a real setting. It requires a full compilation of the code. As GWT compiles for all possible browsers, the compilation process might take up to 5 minutes according to the power of your machine. As you can imagine you don't want to do that when developing as you would spend more time compiling than writing code. When your plugin will be in a good shape in the 'hosted mode' you would make sure the little details for running also in the 'compile mode' are taken care of and then compile the project and link it into the larger Domeo framework (instructions pending).