Short update of Softwarenaut port to Pharo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Short update of Softwarenaut port to Pharo

Dennis Schenk
Hi all,

Here's a short status update on the port of Softwarenaut to Pharo for those interested.

Here is a screenshot of Softwarenaut visualizing itself: http://cl.ly/image/073a0B0z3N15

We see all the classes as nodes, their size corresponds to their weights (which is LOC in this example). The Treemaps are constructed with the classes children, which are methods, their weight also based on LOC.
The relationships are the propagated invocations from each class to the others.

The nodes are manually laid out in the screenshot. One of the next steps will be to find some clever layouting mechanism for nodes of different sizes with relationships between them.

Here is another screenshot of FAMIX


Using the same parameters as the visualization used for the Softwarenaut screenshot but arranged in a circle layout.

If anyone has any question don't hesitate to ask.

Cheers,
Dennis

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Short update of Softwarenaut port to Pharo

abergel
Looks excellent!

Just some easy things to add with Roassal:
  - zoom in/out buttons
  - highlight of connected component by hovering the mouse
  - find button

Good work!
Alexandre

On Oct 9, 2012, at 9:49 AM, Dennis Schenk <[hidden email]> wrote:

> Hi all,
>
> Here's a short status update on the port of Softwarenaut to Pharo for those interested.
>
> Here is a screenshot of Softwarenaut visualizing itself: http://cl.ly/image/073a0B0z3N15
>
> We see all the classes as nodes, their size corresponds to their weights (which is LOC in this example). The Treemaps are constructed with the classes children, which are methods, their weight also based on LOC.
> The relationships are the propagated invocations from each class to the others.
>
> The nodes are manually laid out in the screenshot. One of the next steps will be to find some clever layouting mechanism for nodes of different sizes with relationships between them.
>
> Here is another screenshot of FAMIX
>
> http://cl.ly/image/1t3C2s0r3M3V
>
> Using the same parameters as the visualization used for the Softwarenaut screenshot but arranged in a circle layout.
>
> If anyone has any question don't hesitate to ask.
>
> Cheers,
> Dennis
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Short update of Softwarenaut port to Pharo

Tudor Girba-2
In reply to this post by Dennis Schenk
Excellent!

We should look into integrating it in the Moose Suite configuration.

Doru

On Tue, Oct 9, 2012 at 2:49 PM, Dennis Schenk
<[hidden email]> wrote:

> Hi all,
>
> Here's a short status update on the port of Softwarenaut to Pharo for those
> interested.
>
> Here is a screenshot of Softwarenaut visualizing itself:
> http://cl.ly/image/073a0B0z3N15
>
> We see all the classes as nodes, their size corresponds to their weights
> (which is LOC in this example). The Treemaps are constructed with the
> classes children, which are methods, their weight also based on LOC.
> The relationships are the propagated invocations from each class to the
> others.
>
> The nodes are manually laid out in the screenshot. One of the next steps
> will be to find some clever layouting mechanism for nodes of different sizes
> with relationships between them.
>
> Here is another screenshot of FAMIX
>
> http://cl.ly/image/1t3C2s0r3M3V
>
> Using the same parameters as the visualization used for the Softwarenaut
> screenshot but arranged in a circle layout.
>
> If anyone has any question don't hesitate to ask.
>
> Cheers,
> Dennis
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Short update of Softwarenaut port to Pharo

Dennis Schenk
Hi all,

@Alexandre: Find and Zoom in and out buttons are already there. Highlighting of single nodes and relationships is working. Other interactions I'm working on.
@Doru: Sounds good! But I'd like to make it a little bit more mature before gong there. But we should definitely look into it soon.

There are still some necessary steps to take - from the API side to the Front-End side. 
I'd like to offer some more basic interaction capabilities and also allow for more versatility when constructing the hierarchical graph. 

One of the goals of this hierarchical graph implementation is to make it as generic as possible to allow for visualization of systems not just related to software development.

Here is a screenshot of a hierarchical graph visualization of a directory: http://cl.ly/image/0o3Q3u2z1T1K
Its some PHP web site project inside a git repo. Weight used is size of files.

Thanks for the suggestions so far. Will keep you posted.

Cheers,
Dennis

On Tue, Oct 9, 2012 at 3:13 PM, Tudor Girba <[hidden email]> wrote:
Excellent!

We should look into integrating it in the Moose Suite configuration.

Doru

On Tue, Oct 9, 2012 at 2:49 PM, Dennis Schenk
<[hidden email]> wrote:
> Hi all,
>
> Here's a short status update on the port of Softwarenaut to Pharo for those
> interested.
>
> Here is a screenshot of Softwarenaut visualizing itself:
> http://cl.ly/image/073a0B0z3N15
>
> We see all the classes as nodes, their size corresponds to their weights
> (which is LOC in this example). The Treemaps are constructed with the
> classes children, which are methods, their weight also based on LOC.
> The relationships are the propagated invocations from each class to the
> others.
>
> The nodes are manually laid out in the screenshot. One of the next steps
> will be to find some clever layouting mechanism for nodes of different sizes
> with relationships between them.
>
> Here is another screenshot of FAMIX
>
> http://cl.ly/image/1t3C2s0r3M3V
>
> Using the same parameters as the visualization used for the Softwarenaut
> screenshot but arranged in a circle layout.
>
> If anyone has any question don't hesitate to ask.
>
> Cheers,
> Dennis
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Short update of Softwarenaut port to Pharo

Mircea Filip Lungu-2
> Here is a screenshot of a hierarchical graph visualization of a directory:
> http://cl.ly/image/0o3Q3u2z1T1K. Its some PHP web site project inside a git repo

So we can now analyze php projects with Softwarenaut 4! Cool ;)

Cheers,
M.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Does someone else see this?

FDominicus
In reply to this post by Dennis Schenk
Well I like the explore browser of Moose, and I try to use it wherever
and whenever I can. I know have found the following strange "thing"

I load an actual Moose, If I'm loading
an Nautilus Browser later and after the Nautilus Refactoring enging. the
Explorer browser field with the header Variable is messed up.

Before I have
array

after the messing up I got:
arra
y

And that's unfine.

So how can I persuade the browser to get "de" messed up?

Regards
Friedrich
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Does someone else see this?

Tudor Girba-2
It seems to be a Morphic problem. Unfortunately, I do not have time to look into this right now.

Cheers,
Doru



On Wed, Oct 10, 2012 at 11:05 AM, Friedrich Dominicus <[hidden email]> wrote:
Well I like the explore browser of Moose, and I try to use it wherever
and whenever I can. I know have found the following strange "thing"

I load an actual Moose, If I'm loading
an Nautilus Browser later and after the Nautilus Refactoring enging. the
Explorer browser field with the header Variable is messed up.

Before I have
array

after the messing up I got:
arra
y

And that's unfine.

So how can I persuade the browser to get "de" messed up?

Regards
Friedrich
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Short update of Softwarenaut port to Pharo

Stéphane Ducasse
In reply to this post by Dennis Schenk
really cool Dennis ;)

We will start one of these days on the configurationOfMoose. First I want a release of the new version of Versionner.

Stef

On Oct 9, 2012, at 5:37 PM, Dennis Schenk wrote:

> Hi all,
>
> @Alexandre: Find and Zoom in and out buttons are already there. Highlighting of single nodes and relationships is working. Other interactions I'm working on.
> @Doru: Sounds good! But I'd like to make it a little bit more mature before gong there. But we should definitely look into it soon.
>
> There are still some necessary steps to take - from the API side to the Front-End side.
> I'd like to offer some more basic interaction capabilities and also allow for more versatility when constructing the hierarchical graph.
>
> One of the goals of this hierarchical graph implementation is to make it as generic as possible to allow for visualization of systems not just related to software development.
>
> Here is a screenshot of a hierarchical graph visualization of a directory: http://cl.ly/image/0o3Q3u2z1T1K
> Its some PHP web site project inside a git repo. Weight used is size of files.
>
> Thanks for the suggestions so far. Will keep you posted.
>
> Cheers,
> Dennis
>
> On Tue, Oct 9, 2012 at 3:13 PM, Tudor Girba <[hidden email]> wrote:
> Excellent!
>
> We should look into integrating it in the Moose Suite configuration.
>
> Doru
>
> On Tue, Oct 9, 2012 at 2:49 PM, Dennis Schenk
> <[hidden email]> wrote:
> > Hi all,
> >
> > Here's a short status update on the port of Softwarenaut to Pharo for those
> > interested.
> >
> > Here is a screenshot of Softwarenaut visualizing itself:
> > http://cl.ly/image/073a0B0z3N15
> >
> > We see all the classes as nodes, their size corresponds to their weights
> > (which is LOC in this example). The Treemaps are constructed with the
> > classes children, which are methods, their weight also based on LOC.
> > The relationships are the propagated invocations from each class to the
> > others.
> >
> > The nodes are manually laid out in the screenshot. One of the next steps
> > will be to find some clever layouting mechanism for nodes of different sizes
> > with relationships between them.
> >
> > Here is another screenshot of FAMIX
> >
> > http://cl.ly/image/1t3C2s0r3M3V
> >
> > Using the same parameters as the visualization used for the Softwarenaut
> > screenshot but arranged in a circle layout.
> >
> > If anyone has any question don't hesitate to ask.
> >
> > Cheers,
> > Dennis
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev