Community
Participate
Working Groups
Currently, if the user is looking at Host interactions and wants to see all the process interactions within a specific host, the only way to do it is to select that host in the profiling monitor and open-with process interactions. We should facilitate this as it can be a common activity; ideally, the user could right click on one or more elements (lifelines) in the sequence diagram and show the information for those elements. The next level of information down would be shown, and everything is filtered out automatically except for those things that were selected in the previous sequence diagram. This will allow the user to start at the top and trace the root cause of a problem; from host, to process, thread, and eventually class or object. The larger the system, the more useful this will be.
Also, as a final drill down step, the user should be able to open the source on a class/object or method by right clicking on it in and selecting "Open Source" in the sequence diagram.
I'm not sure I should be the owner of this defect. The sequence diagram view is generic, and this feature is specific to the Host interaction. In this case, this should be done by adding the Host inteaction controler. Ditto for the others similar feature you describe after this one.
Actually I meant to do this for all the trace sequence diagrams, I was just using Host interactions as an example. I agree this is not part of the sequence diagram UI but whatever is driving it. Who owns this part? (I thought it was Toulouse)
It is Toulouse. Note that Open Source has already been done from BlueRat for Atlantic. If we do it on the Hyades side, we must take care of the sync between Hyades and RDJ, in order to avoid having this contextual menu twice!
Fixed in HEAD. A new drop down menu allow to switch between the different trace interactions. A new contextual menu associated to lifelines allows to drill down on host, agent, process and thread interactions respectively to agent, process, thread and class interactions. Introduced positive and negative filters (filter in and filter out) to use the positive ones when drilling down.
Thanks, I think this is a great improvement. However, there's a problem with the way the view remembers its state. 1. Unfilter monitors from the profiling monitor. 2. Open host interactions from the profiling monitor (right click on monitor item). 3. Drill down to the class interactions level. 4. Close the sequence diagram. 5. Open the host interactions again from the profiling monitor. 6. Note: it opens the class interactions Also, I tried opening class interactions on a new trace in a new workspace for the first time, and it opens the host interactions. A few more comments: - I think we should have a more consistent way to switch between levels in all our views. The statistical tables have toolbar buttons, but the sequence diagram uses the view menu.. - I couldn't seem to drill down to the object level. The drill down item is not present, but there are instances of this object, and I can see them if I manually switch to the object level. - Not sure about the wording of "Drill down into such lifeline".. asked ID for comment.
Open with... has been fixed. This explains also why on a new workspace you're having host interactions, that is default trace interactions. I disagree about the buttons, we would need 6 new buttons. That's too much compared to the usual three buttons for Package/Class/Method in statistical views. I'm open to other arguments about this. As explained, drill down stops in class interactions, because class and objects are quite the same things, where processes, threads and so on are more obviously different. I'm open to other arguments about this too. Tell me about ID feedback when you have it.
About the buttons, I didn't mean to say we should be using buttons.. just that, whatever we use to switch between the different levels, it should probably be consistent throughout the views (i.e. not do the tables one way, and the sequence diagrams a different way). I think it still makes sense to drill down in a class.. at least in my mind. By drilling down in a class, it would show all the interactions between the instances of that class, just like clicking on a process shows all the interactions between the process's threads. I like the complete picture idea of drilling all the way down, even to the source level. I do agree that object interactions is a little different though, because they show classes in order to see the static methods. Any opinions Wayne/Valentina ?
Regarding a separate note on the terminolgy/wording (from Dec 1, 2004) Update all occurrences of the word 'such' to 'selected'. e.g. Drill down into such lifeline --> Drill down into selected lifeline.
Fixed wording (such->selected).
I'm trying to drill down from host interactions, and it skips process interactions and goes directly to agent interactions. When I continue drilling down on the agent, it brings me to an empty process interactions. So I think the order is incorrect here. Also, when I close the sequence diagram and try to start over at host interactions, I only see one host (the one I drilled down into). One more thing, I still can only drill down to the class level, and can't drill down to the object interactions.
close feature and opened bug 81525 to track bug identified
Verified. Closing bug.
