...
- Use the standard webAPI as much as possible (developer.mozilla.org)
- It should be easy to write a plug-in
Interaction with the SCL should be easy
- Libaries for specfic taks
- Do and undo functionality
Integrate small functionality within wider platform quickly (easy to deploy)
Clear API's for plug-in
authorsauthors with sufficient quality
Plug-in authors can use components to speedup the development and give a consistent look and feel (optional)
Technical implications:
Modular and loosely coupled
Limit dependencies
General functional aspects of OpenSCD next
- Embed OpenSCD next as embedded application is not foreseen yet. It might be possible with an iframe. The current technology might already allow it.
- Support multiple OpenSCD instances is not supported
- OpenSCD provides: front-end for graphical interaction
Solution: OpenSCD-core architecture overview
...
OpenSCD-core is the main application of OpenSCD-next. OpenSCD-core will be loaded once people open the application. OpenSCD-core sets the requirements and API's for the plug-ins.
Functionality should should be stable and long lasting in order to have stable ecosystem.
Selection criteria for incorporate stuff into OpenSCD-core:
...