- We can use babel to ensure browser compatibility
- Some styling errors may occur on edge cases, but I don’t think that’s a problem, really
- Electron adds a 80+ MB (if I recall correctly) executable size, that’s really bad: It’s a browser that runs in a desktop environment after all.
- We can have a script that automates the installation – pip is not that easy to use really
- starting Yukon can fire up the default system browser as well as the python service and what not
- Packaging & updating is not really an issue: Updates in general should happen when someone NEEDS new features. If you want this to happen blazingly fast, we can serve the tool from a separate online server (which is always up to date), which communicates with the localhost (or any configured) address.
- The desktop environment is not really an issue. We now have service workers, good support for browser local storage and a variety of other APIs we can use on the browser (from file system to gyroscope access).
For sure, we will have a python service ontop of pyuavcan. We have to look into potential auto-generated cli from the endpoints, so this part gets automated (like many CLIs do – ex. Google APIs do this generation thing all the time)
Also: Use swagger for the rest api documentation