You are reading a single comment by @allObjects and its replies. Click here to read the full conversation.
  • @Kolban, the E.onInit() enables the composition of applications form independent modules and each of these modules may have some init code that has to run on (re-)power up (after having saved the code). So far, there was only one single onInit() function. That function would then have to be application composition specifically implemented. With the arrival of E.onInit(), this responsibility can now be delegated to the module itself by placing E.onInit() into each module.

    I though still have questions about how it is done when this E.onInit() code - process - needs configuration information - data - that is specific to the app - or the composition - of the set of modules. If sequencing matters - because one module may need references / data from antoher one and this reference / data becomes only available through onInit() - the old fashiioned single onInit() function may still apply. Promises can work too, but they do not have sequence in it. Therefore, I came up with a tasker as layed out in the Tasker - Task synchronizer - kind of a 'purposed' Promise conversation. The Tasker has retry options to allow for variations in timing of things....


Avatar for allObjects @allObjects started