[Moose-dev] Magritte confusion

I'm totally confused by magritte… So I can fix Moose somehow but I do not know how to manage it. I defined FM3Element class>>magritteDescriptionName <magritteDescription> ^ MAStringDescription new accessor: #name; default: 'noname'; label: 'Name'; priority: 100; beRequired; yourself FM3PropertyDescription class>>magritteDescriptionType <magritteDescription> ^ MASingleOptionDescription new accessor: #type; label: 'Type'; priority: 300; default: FM3 boolean; beRequired; options: [ {FM3 number . FM3 string . FM3 boolean} ] magritteDynamicObject; " reference: MAClassDescription new;" yourself and now Pragma allNamed: MAPragmaBuilder magritteDescriptionPragma from: FM3Element to: Object. -> #() because the description are defined on class side. I could define the descriptions on the instance side but to me it does not make sense. Pragma allNamed: MAPragmaBuilder magritteDescriptionPragma from: FM3Element class to: Object class. -> an Array(<magritteDescription>) ;) and Pragma allNamed: MAPragmaBuilder magritteDescriptionPragma from: FM3PropertyDescription class to: Object class. an Array(<magritteDescription> <magritteDescription>) Now the definition of uniqueDescriptionSelectors: or the build: method of MAPragmaBuilder look bogus to me. Either it should take a class as argument or move the class level. Is anObject a class? may be the correct definition is Object>>basicMagritteDescription ^ MAPragmaBuilder for: self class instead of basicMagritteDescription ^ MAPragmaBuilder for: self Then options: [ {FM3 number . FM3 string . FM3 boolean} ] magritteDynamicObject; Apparently there is no MADynamicObject anymore….. So can use the old version of magritte for moose because this is boring to run after bugs like that Stef