Speaking of joint Module and Project development, my typical iteration of construction process consists of
- running the Designer,
- detecting an error in the Java code by testing out a part of the application within the Designer,
- fixing the problem through Eclipse, re-building and re-deploying the module using Ant,
- restarting the Designer,
- resuming to the point within the Designer I was working on,
- and testing if the changes work
which will take a while each time, all actual work excluded. And this is often between 20 and 200 times a day.
Most of the time is spent restarting and resuming Ignition Designer session and the only reason seems to be reloading the module (the one that contains my Java code) jar files into the Designer.
For comparison, it is quite slow compared to Eclipse/Java/Tomcat webapp development, where everything is pretty much integrated into the IDE.
Any ideas how to improve the situation?