Damien Marchal

Why removing the DefaultVisualManagerLoop ? It seems to everyone during sofadevmeeting it is better if it is explicit (despite there is no more warning to enforce that).

@hugtalbot here is the feature. I think it should be used at least in PR #173 and few other.

Oops, I missread "lifecycle" in the sofa code base (which is not related to componentState). Future is the common name in python...but as we already have a namespace for feature...

@hugtalbot I now rename everything so it match the sofa naming convention: lifecycle. I also renamed the contextmanager ```__feature__``` into ```__new_feature__```... in case one day we decide to have something...

Nice day, I Have questions about a pending PR Thanks @guparan Adding features in lifecycle::features ============================ Q: Why? What is considered a "new feature" and thus should be registered in...

Hello @jjcasmar, This is a very good question and making that part clear is a yet to do work. Data are binded to a SofaData python type or one of...

Thanks @jnbrunet for the feedback. Yesterday I made several tests to see the look and feel and made ```python def createScene(root): root.addObject("MeshObjLoader", filename="mesh/cube.obj", name="loader"); a = root.addObject("PointSetTopologyContainer", position=root.loader.position.linkpath, name="topo") b...

Another alternative could be to first deprecate (with a warning message) the existing implicit version then replace it with an exception saying that this ambiugous and force to replace it...

@guparan No, what we currently have is: ```python root.addChild("RequiredPlugin". "Sofa.Component") ``` Which is loading a single "special" plugin targets that loads other. To make that happens, we have hardcoded, for...

@hugtalbot so as there was no answer it will be time to plan updating and merging ;)