We should also provide a dedicated reflective tree-editor that supports
decoration. Therefore, we may provide a dedicated editor that is a subclass of
the reflective Ecore editor but which overwrites the image provider etc to
enable displaying stereotype applications. So when the tree-based Ecore editor
is opened and the user wants to load or apply a profile, we may ask the user if
he/she wants to switch to that extended reflective editor that provides
decoration support.
Original issue reported on code.google.com by
p.langeron 3 Mar 2013 at 9:41