The four key players of an Equo application are:
Chromium for displaying web content.
Java for developing the backend application.
Developing a traditional Equo application is like building a web interface or building web pages, and seamlessly integrate them with a Java backend.
In an Equo application, the web pages are rendered in processes that are independent of the Java processes. That keeps the Java UI thread always responsive, as well as the web pages.
Communication between the web and the Java part is possible via the Comm API, this allows real-time bi-directional communication.
Structure of an Equo Application
Once the Equo application has been created with the CLI tool and the environment is ready, the next step is to start developing the application. You will need to import it in your favorite IDE.
An Equo application is just a Java application, so its project structure is the same as the one you will find in a traditional Java application.
. ├── pom.xml └── src ├── main │ ├── resources │ │ └── index.html │ └── java │ └── samplename │ └── SampleNameApplication.java └── test └── java └── samplename └── SampleNameApplicationTest.java
src/main/java folder contains the Java code of your application and the starting class which builds and starts an Equo Application.
It can actually include a complete web application.
In the same files you can add code to modify your existing web application (this happens in the case of a web wrapper application).
New UI elements can be easily added to or removed from the existing web application, and they will only be shown in your desktop Equo application.
The generated application also contains a property file which can be used to define the configuration of you application. For example, the application branding can be defined in this properties file.