Magritte usage pattern

Hi, I'm dealing now quite a bit of time with Magritte to do a web application. It took a while to get into Magritte and I'm not sure how much I've grasped til now. But I'm quite impressed by the power of Magritte. It seems to be customiz- able at the right places which distinguishes it from others. At the moment I'm refactoring the code I hacked the last weeks. I have a few questions about best practice patterns using Magritte. For the demo, you have a model and you just need any component, the case is quite easy. aModel asComponent will do. But most of the tasks that have to be done for a web application aren't that trivial. You need to have a customized layout (which can be very complex), you need your own components etc. For customization I put every little bit in a wrapper class around the generated Magritte component. This is for customizing the generated component as well as to do some manual html if it isn't avoidable. I have the feeling that this is not the right way to do but I have no better idea. To minimize the effort to do a component for a model component I've built a base class which should ease the customization of the component. The parameters for the base component are: - descriptionSelector This is a symbol which is invoke on the model if you need a subset of the descriptions. The default value is #description - componentRenderer The visitor which is used to render the component - buttons A Collection of Associations (button label -> selector). MAForm- Decoration is only useful if you have save and cancel buttons. As the selectors are performed on the MAContainerComponent there is no way of extending it. I extendend MAFormDecoration to have associations for buttons (to distinguish the button label and the selector to use) and to be created with a delegator. The selector is than performed on the delegate which leads to a usage form component addDecoration: (WHFormDecoration delegate: self) buttons: #( #ok -> commit. #abbrechen -> abort) - validation There are three choices: * no validation * validation by MAValidationDecoration (or similar) I must confess that I never understood processChildCallbacks. * manual validation and error handling Using the form [self component validate] on: MAError do: [:anException | self exception: anException]. - answering Having a wrapper component I need to process answer in the wrapper. This can be customized by defining answerBlock. Default value is self component onAnswer: ( answerBlock ifNil: [ [:anAnswer | self answer: anAnswer] ] ) - readonly/readwrite I'm mimicking the behaviour in MAElementComponent having renderViewerOn:/renderEditorOn:. This is a good way to switch a component between readonly and readwrite mode. In my case the layout of the component is completely different between those two modes. So I use two different renderers for readonly and for readwrite mode. - really complex layout cases I have one case where it is necessary to put css classes to some of the components of a form. The best way I found so far (being dirty) is to use propertyAt:put: at description level and use this in a specialized renderer So far so good. I like to hear your oppions and experiences doing this kind of stuff. Another problem I have no solution til now is the mixture of models into one component. Sometimes you build your data model and then page layout forces you to edit two objects at the same time. I have no problem to mix descriptions in a desired way. But by invoking asComponentOn: they would have all the same model which is wrong for a subset of the descriptions. Is there any clever way to mix descriptions, set the model accordingly and then produce the component? thanks in advance, Norbert