Repository node in Project browser

[Paolo F Cantoni]

Hi,

I'm developing some automation to do various jobs in the model.  I've developed a useful paradigm (for some functionality) that says: select one or more vertexes (either in the browser - unfortunately only one at a time - or on a diagram).  You can then do "functionality" to the selected items.  If the item is an element do it to the element.  If the item is a package, do it to the items in the package.  The functionality can also optionally recursively traverse the hierarchy.  This works really well!

However, there are often times when I want to do "functionality" to the entire repository.  However, there is no way to do this in the Browser.

I suggest the creation of a single "Repository" node (which will return ObjectType  = otModel) with the existing "project root" nodes as its children.

This may also help the generation of whole repository HTML reports as I understand that you can't generate HTML references across "project nodes".

If this idea has some popularity, I'll submit a formal request.

Paolo

[Geert Bellekens]

I can see this being usefull sometimes, so you have my vote.

Geert

[«Midnight»]

Please make the request. This sounds like a very good idea.

The Repository node could be 'virtual' in the sense that it would not (necessarily have to) be an element. It would also not need to show up in the Project Browser. This way there should be minimal disruption to the existing project hierarchy and visible interface.

David

[Geert Bellekens]

Well, I think it should show up in the project browser. Otherwise we can't select it as a starting point for reports or other tools.

[«Midnight»]

Oops...  

Perhaps if it showed up as something other than a package. That would be fine.

[Frank Horn]

There could be an option for showing it.

By the way, this reminds me of all the things which actually are UML elements and still do not show up in the project browser (like concurrent state regions or forks).