Begin forwarded message:
From: Henrik Johansen henrik.s.johansen@veloxit.no Date: June 18, 2010 10:01:53 AM GMT+02:00 To: Stéphane Ducasse stephane.ducasse@inria.fr Subject: Re: PDF of Software Metrics
What he was most interested in, was the C++ thresholds for the overview pyramid in Moose. Found those in an online presentation, so wasn't as pressing after all :) Is there any reason why only JavaThresholds are included/used by default, instead of being selected automatically based on what language your model originated from?
On the bright side, he's found the tools really useful (doing an architectural review of a large C++ program) after I tipped him of the existence of Moose :)
Mondrian visualizations do not scale very well for a project of this size though, the display model seems more geared towards traversing the model rather than culling what does not show up on screen, which turns into a problem when it redraws 50000 nodes each refresh rather than the 100 - 200 actually visible on screen... (ie. 8-10 seconds for one refresh after clicking scroll bars) (This was an enriched DSM chart for 20 namespaces)
The blueprint complexity visualization never even opened (as in, at least in the first minute), the algorithm for calculating edges is waaay too slow with 500 entities :)
Which is kind of a shame, since those large, complex systems are what it really would be nice to have good visualizations of... :/ Maybe better scaleability would be a good goal for Moose 4.1?
Cheers, Henry
Hi Stef,
How did they parse the C++ system?
Doru
On 18 Jun 2010, at 10:38, Stéphane Ducasse wrote:
Begin forwarded message:
From: Henrik Johansen henrik.s.johansen@veloxit.no Date: June 18, 2010 10:01:53 AM GMT+02:00 To: Stéphane Ducasse stephane.ducasse@inria.fr Subject: Re: PDF of Software Metrics
What he was most interested in, was the C++ thresholds for the overview pyramid in Moose. Found those in an online presentation, so wasn't as pressing after all :) Is there any reason why only JavaThresholds are included/used by default, instead of being selected automatically based on what language your model originated from?
On the bright side, he's found the tools really useful (doing an architectural review of a large C++ program) after I tipped him of the existence of Moose :)
Mondrian visualizations do not scale very well for a project of this size though, the display model seems more geared towards traversing the model rather than culling what does not show up on screen, which turns into a problem when it redraws 50000 nodes each refresh rather than the 100 - 200 actually visible on screen... (ie. 8-10 seconds for one refresh after clicking scroll bars) (This was an enriched DSM chart for 20 namespaces)
The blueprint complexity visualization never even opened (as in, at least in the first minute), the algorithm for calculating edges is waaay too slow with 500 entities :)
Which is kind of a shame, since those large, complex systems are what it really would be nice to have good visualizations of... :/ Maybe better scaleability would be a good goal for Moose 4.1?
Cheers, Henry
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Speaking louder won't make the point worthier."
no idea On Jun 18, 2010, at 10:46 AM, Tudor Girba wrote:
Hi Stef,
How did they parse the C++ system?
Doru
On 18 Jun 2010, at 10:38, Stéphane Ducasse wrote:
Begin forwarded message:
From: Henrik Johansen henrik.s.johansen@veloxit.no Date: June 18, 2010 10:01:53 AM GMT+02:00 To: Stéphane Ducasse stephane.ducasse@inria.fr Subject: Re: PDF of Software Metrics
What he was most interested in, was the C++ thresholds for the overview pyramid in Moose. Found those in an online presentation, so wasn't as pressing after all :) Is there any reason why only JavaThresholds are included/used by default, instead of being selected automatically based on what language your model originated from?
On the bright side, he's found the tools really useful (doing an architectural review of a large C++ program) after I tipped him of the existence of Moose :)
Mondrian visualizations do not scale very well for a project of this size though, the display model seems more geared towards traversing the model rather than culling what does not show up on screen, which turns into a problem when it redraws 50000 nodes each refresh rather than the 100 - 200 actually visible on screen... (ie. 8-10 seconds for one refresh after clicking scroll bars) (This was an enriched DSM chart for 20 namespaces)
The blueprint complexity visualization never even opened (as in, at least in the first minute), the algorithm for calculating edges is waaay too slow with 500 entities :)
Which is kind of a shame, since those large, complex systems are what it really would be nice to have good visualizations of... :/ Maybe better scaleability would be a good goal for Moose 4.1?
Cheers, Henry
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Speaking louder won't make the point worthier."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Apparently, they managed to find the info about using McC, getting it through inFusion and then in Moose :). They got to this solution through the !README-MOOSE.pdf that comes with inFusion.
Cheers, Doru
On 18 Jun 2010, at 14:58, Stéphane Ducasse wrote:
no idea On Jun 18, 2010, at 10:46 AM, Tudor Girba wrote:
Hi Stef,
How did they parse the C++ system?
Doru
On 18 Jun 2010, at 10:38, Stéphane Ducasse wrote:
Begin forwarded message:
From: Henrik Johansen henrik.s.johansen@veloxit.no Date: June 18, 2010 10:01:53 AM GMT+02:00 To: Stéphane Ducasse stephane.ducasse@inria.fr Subject: Re: PDF of Software Metrics
What he was most interested in, was the C++ thresholds for the overview pyramid in Moose. Found those in an online presentation, so wasn't as pressing after all :) Is there any reason why only JavaThresholds are included/used by default, instead of being selected automatically based on what language your model originated from?
On the bright side, he's found the tools really useful (doing an architectural review of a large C++ program) after I tipped him of the existence of Moose :)
Mondrian visualizations do not scale very well for a project of this size though, the display model seems more geared towards traversing the model rather than culling what does not show up on screen, which turns into a problem when it redraws 50000 nodes each refresh rather than the 100 - 200 actually visible on screen... (ie. 8-10 seconds for one refresh after clicking scroll bars) (This was an enriched DSM chart for 20 namespaces)
The blueprint complexity visualization never even opened (as in, at least in the first minute), the algorithm for calculating edges is waaay too slow with 500 entities :)
Which is kind of a shame, since those large, complex systems are what it really would be nice to have good visualizations of... :/ Maybe better scaleability would be a good goal for Moose 4.1?
Cheers, Henry
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Speaking louder won't make the point worthier."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
Mondrian visualizations do not scale very well for a project of this size though, the display model seems more geared towards traversing the model rather than culling what does not show up on screen, which turns into a problem when it redraws 50000 nodes each refresh rather than the 100 - 200 actually visible on screen... (ie. 8-10 seconds for one refresh after clicking scroll bars) (This was an enriched DSM chart for 20 namespaces)
Indeed. 50000 nodes is a lot.
This script takes some times to display. Dragging and dropping a node is very slow. -=-=-=-=-=-=-=-=-= view shape rectangle withText. view nodes: (1 to: 50000). -=-=-=-=-=-=-=-=-=
The blueprint complexity visualization never even opened (as in, at least in the first minute), the algorithm for calculating edges is waaay too slow with 500 entities :)
Yes. The model used for edges does not scale very well.
Which is kind of a shame, since those large, complex systems are what it really would be nice to have good visualizations of... :/ Maybe better scaleability would be a good goal for Moose 4.1?
:-)
Alexandre
-
Alexandre Bergel -
Stéphane Ducasse -
Tudor Girba