Vincent Aranega

With @anneetien we got the impression that there is no more dependencies to GT/Glamour in Moose 10, at least on `MooseObject` (`mooseFinderNavgationIn:` and `mooseSpecificSpotterProcessorsFor:` don't exist anymore there).

Hi @AnNeub ! Indeed, the hash thing for proxies is tricky. The same problem occurs in EMF with unresolved resources, but in your case, it would be better to avoid...

Hi @AnNeub Thanks for your message! Sorry for the dealy, I had to go again in EMF documentation and implementation to check all of that as you made me doubt....

Hi again @AnNeub, Thanks again for the issue, I'll check that asap. So the scenario is that there is an external resource that is automatically loaded (let say there is...

Hi @AnNeub Sorry for the late answer... I started to try to reproduce your issue, but I cannot, mainly because I think the issue you have is directly related to...

@stefanq Thanks for your issue, you're right, PyEcore would really benefit from being able to be "understandable" by projects that generates code. At the moment, pyecoregen generates code for genmodel...

Hi @angelabr, At the moment, there is no validation methods for ecore metamodels, but that's definitely something that could be added easily. Thanks for the idea! I will see what...

Just some infos regarding this issue. I made some experiments which relies on the doSwitch like feature implemented from #23 . The result works great, but at the moment I'm...

Hi @mpekchri This project is still a WIP. I lack time to cover everything lately. I started to work on it, but I'm still not happy with the current design....

Hi @AnNeub Thanks so much once again for the issue :) ! You are definitely right, the automatique handling of keyword parameters should be equivalent to the generated code. This...