Hi Tim I think I double checked spring boot when I implemented this little hello-world webapp in the examples. I guess from the licensing side this should be ok ... or it slipped past Justin's legal eagle-eyes ;-)
Usually I would say that we shouldn't enforce any framework on our users. But I guess the simulated PLC is sort of a completely different use-case. I'd say the simulator is more a product that uses PLC4X than a framework. It is not meant for being integrated into something bigger. So in this case we should probably just use what's a good tool for this particular case and I think Spring (Boot) is quite well suited for being a valid candidate. So no objections from me for choosing it. Regarding the frontend technology, I would probably suggest not to use Royale ... it's not a Java framework ... Here you write code in ActionScript3 and MXML and have that transpiled to JavaScript & CSS. However I built this tiny app in the examples just because Royale was an Apache project and I wanted to try it. But when trying to do it again with another module, I failed miserably and wasn't able to find what was going wrong within a reasonable timeframe. I would probably choose it if it was just me working on the thing as I really know ActionScritp and MXML very well and I built the maven part of the Royale build-system. But if you're not already familiar with it I would probably suggest to use something more conventional. What I would like to make sure, is that the technology used should be integratable into our build without adding to much new tooling and setup complexity. I know it's possible to do this with TypeScript related projects. In the DukeCon project they also built the frontend using Vue and the project is built with Maven using the "frontend-maven-plugin" (https://github.com/dukecon/dukecon_pwa) So perhaps this would be an option? My thoughts on the topic. Chris Am 15.10.19, 13:54 schrieb "Tim Kläsener" <[email protected]>: Hi everyone again, We're currently looking into creating a frontend for interacting with the PLC Simulator, i.e. having an administration interface for changing properties/input/output and, if time allows, some fancier visual representations of the devices the PLCs control. As for the REST service, I've so far developed it with Spring Boot which should be okay from a licensing perspective (let me know if you have any concerns), now I'm looking into different options for developing the frontend: 1. Simple handwritten html+javascript (Jquery?) served by the Spring Boot backend (easy to start with but might get a bit messy over time) 2. Separate single page application using Vue/Angular/React/JS-Framework of the week (better separation of concerns but requires JS-toolset) 3. Java-based web UI framework like Vaadin or Royale Any other suggestions or reasons to choose one option over the others? Cheers, Tim
