The current way to open a multidimentionnal trace file relies on the default reflective tree editor
It would be convenient to have a slightly improved tree editor that use the internal data to improve the labels of the node and thus have a better understanding of its content.
for example: reuse the name of the dynamic property in the GenericDimension name
Note: currently the user may think that she uses a dedicated trace editor, but this is actually an editor from inria.aoste that is used and that ends up with the default reflective editor
The current way to open a multidimentionnal trace file relies on the default reflective tree editor
It would be convenient to have a slightly improved tree editor that use the internal data to improve the labels of the node and thus have a better understanding of its content.
for example: reuse the name of the dynamic property in the GenericDimension name
Note: currently the user may think that she uses a dedicated trace editor, but this is actually an editor from inria.aoste that is used and that ends up with the default reflective editor