Pierre Laborde

Hi @Eliott-Guevel, the PR #177 is now merged. This PR contains new components start/stop announcement system. You can test your dev with it. Some tests for P12 are not passing,...

@ELePors can I have your opinion ?

New proposition to be not ambigus with a possible unique instance: `MolComponentImpl>>startWithUniqueName`

Ok! We will do that for start and instantiate methods. We need to check, at the generation, if the name is not already used by another component implementation of the...

A similar test here: https://github.com/OpenSmock/Molecule/pull/146

@ELePors don't hesitate to expose your ideas on this function to brainstorm on it.

Edit: this is a reflexion. => I don't find an use case when 'componentName' is not suffisant to deploy a component stack :/ May be this feature is a reflect...

Two points of view: - static - list of implementors - dynamic - running instances

Hi @Eliott-Guevel, this code is the internal mecanism of Molecule to be notified when classes change. This is not related to component life-cycle but related to live-coding features. I think...

We have this: ``` MolHomeServices>>instantiateComponent: aComponentClass named: aName (...) component triggerEvent: #instantiateComponent with: component. (...) MolHomeServices>>activateComponent: aComponentClass named: aName (...) component triggerEvent: #activateComponent with: component. (...) etc. ``` This is...