Hi Patrick,
The implementation of the new Architecture framework is globally nice and pleasant from a technical point of view.
We have implemented in few days our own architecture description language similarly to what it has been done for Papyrus editors. Thus, we have a better granularity to fully control which diagram can be created in a certain context. We can also propose just a subset of all the available diagram editors or propose a view point with a lightened palette.
It suits totally our needs.....but this setup (in our specific context) has required to own a 'Papyrus Black Belt'. Simply because many frameworks are involved in this tool chain (at least three) and require to be familiar with all these concepts and to well understand how they interact between them.
A remark not directly related to the architecture framework itself (already formulated by Ansgar): when defining a new palette item, it would be nice to consider by default the icon path of the element type definition (if defined). Of course, it should be possible to redefine this path in the palette item configuration is needed. But by default, the element type icon path should be considered as reference and so, used at runtime in priority.
Regards,