Hi Geert,
thanks for reply.
I should say that I would not want to have it in each and every project too.. but there are projects & use cases of EA where having the notes shown in the mode I described would be extremely helpful.
One from cases I am dealing with is representing of objects of IBM System i platform in UML models.
Name of an object on iSeries is restricted with 10 characters. Additionally, there is no notion of a hierarchical folder structure on the platform - only flat libraries structure, with libraries not possible to host other libraries. As such, the libraries (namespaces) usually contain a lot (thousands for mid size system) of objects (programs, data files and etc.).
To accommodate for the restrictions, naming standards for the objects are usually very cryptic. Therefore, the description attribute is used very extensively on System i to provide clues about purpose of an object. Native iSeries tools, allowing to browse objects (similar to project browser in EA), as a rule, display the description alongside of the object name to help to identify & differentiate the objects.
The notes attribute in UML is the perfect place for descriptions of the System i objects, but if the notes are not displayed in EA project browser, it makes it quite complicated to work with such EA model comparing to the use of native System i tools.
Alex