I never managed to take a look at QCMagritte but it sounds as an extension. Why was it never integrated?
Norbert Von meinem iPad gesendet > Am 19.03.2017 um 10:06 schrieb Stephan Eggermont <step...@stack.nl>: > >> On 18/03/17 18:40, Mariano Martinez Peck wrote: >> Some answers below. But a general comment is that the typical case to >> customize magritte is by subclassing and then somehow use your own >> subclasses instead of magritte ones. > > Well, there are lots of ways to customize magritte. So many actually, that it > is definitely non-trivial to decide where to extend what. For your first > experiments with extending magritte, just subclassing is definitely the way > to go. You need a way to understand how the different parts in magritte > interact, and the easiest way is to change something and see what it does. > > In QCMagritte we've gone much farther. Some problems (access control, > translation) are much easier solved by modifying the visitor used to render > the html. By chaining multiple visitors, it becomes easy to translate all > labels and help-texts without polluting the magritte descriptions or the > domain objects. The same goes for access control. > > Stephan > > > >
