We have done some work in the atomvm_lib to support the OTP application behavior, and it would be good to port this code and framework into the core AtomVM libraries.
Features would include:
- Allow users to implement the OTP
application behavior
- Allow users to define application and module dependencies using OTP .app files, and for the framework to auto-load and auto-start applications in a well-defined order
- Allow users to define applications that auto-start without having to write a
start module -- i.e., have the init framework auto-load applications
- Define a configuration model that is a close analog to the OTP
config feature, appropriate to the platform (e.g., NVS on ESP32).
- Support users who don't want to use the application framework so that "traditional" AtomVM applications can still run and be developed
We have done some work in the
atomvm_libto support the OTP application behavior, and it would be good to port this code and framework into the core AtomVM libraries.Features would include:
applicationbehaviorstartmodule -- i.e., have the init framework auto-load applicationsconfigfeature, appropriate to the platform (e.g., NVS on ESP32).