Yes, we use Netbeans IDE to develop Wandora. The Netbeans is used to compile Wandora sources and to build some of the UI (Swing GUI Builder). Compiling sources with Eclipse and other Java development tools is possible. I did some experiments after watching a short tutorial (
https://www.youtube.com/watch?v=ctNajC04BrY). To summarize the experiences:
- While adding the contents of lib to Eclipse, add only jar files to the build path. Any other file types cause problems.
- Wandora's webview panel (http://www.wandora.org/wiki/Webview) uses JavaFX. I had to copy the jfxrt.jar from JRE's lib folder to Wandora's lib and add the jfxrt.jar to Eclipse project as build path.
- Don't run Wandora from Eclipse. Just build everything.
- It seems Eclipse puts compiled classes to a bin folder by default. Wandora keeps all startup scripts in bin folder. To resolve the conflict I renamed Wandora's bin folder to bin2.
- Wandora's startup scripts assume all classes locate in build/classes folder. I created the folder manually and copied the contents of bin to build/classes (after successful build).
- Wandora's startup scripts assume all libraries locate in build/lib. I created the folder manually and copied the contents of lib to build/lib. As said above, the lib contains also non-jar files. These must be copied too.
- Wandora requires resource files (images, topic maps etc.) that locate in build/resources folder. I copied the resources folder manually to build/resources.
After these steps I was able to compile Wandora sources with Eclipse and to run compiled Wandora application. I am rather sure all manual copy/configuration steps can be automated/configured in Eclipse too. One could also adjust Wandora's startup scripts in bin2 (originally bin) to change the location of compiled classes, libs and resources.
Kind Regards,
Aki / Wandora Team