Hi,
I built a new visualization that has two goals:
1. show how the architecture of a system is fluid rather than rigid. 2. look good and serve as advertisement device for Moose, Roassal and Pharo.
A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/
I already used it as a splash screen for a couple of presentations, and it catches the eye.
The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups).
Cheers, Doru
I think this is the nicest looking visualization made so far with Roassal. Consider it for the next Roassal contest next year.
Amazing job! Truly beautiful.
Alexandre
On Oct 3, 2013, at 6:34 PM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
I built a new visualization that has two goals:
- show how the architecture of a system is fluid rather than rigid.
- look good and serve as advertisement device for Moose, Roassal and Pharo.
A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/
I already used it as a splash screen for a couple of presentations, and it catches the eye.
The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups).
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
Indeed very very nice!! I will try here :)
On Thu, Oct 3, 2013 at 11:34 PM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
I built a new visualization that has two goals:
- show how the architecture of a system is fluid rather than rigid.
- look good and serve as advertisement device for Moose, Roassal and
Pharo.
A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/
I already used it as a splash screen for a couple of presentations, and it catches the eye.
The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups).
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
On Thu, Oct 3, 2013 at 11:34 PM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
I built a new visualization that has two goals:
- show how the architecture of a system is fluid rather than rigid.
- look good and serve as advertisement device for Moose, Roassal and Pharo.
A description of mainly point 1. can be found here: http://www.humane-assessment.com/blog/system-attraction/
I already used it as a splash screen for a couple of presentations, and it catches the eye.
The code can be found in Moose, in a separate tiny FAMIXSystemAttraction class. You can invoke it on any class group (note: it can take a long time to render for large groups).
I try to render the system attraction visualization. Nice work !
But very slow even on small examples ... Do you use a magic trick to enhance the performance ?
Regards,
But very slow even on small examples ... Do you use a magic trick to enhance the performance ?
Not really.
Alexandre
System Attraction is pretty, but slow due to the complexity of the force based layout.
Doru
On Wed, Oct 16, 2013 at 1:34 PM, Alexandre Bergel alexandre.bergel@me.comwrote:
But very slow even on small examples ... Do you use a magic trick to enhance the performance ?
Not really.
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
It would be great to have a domain specific force based layout.
For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class.
Alexandre
On Oct 16, 2013, at 11:09 AM, Tudor Girba tudor@tudorgirba.com wrote:
System Attraction is pretty, but slow due to the complexity of the force based layout.
Doru
On Wed, Oct 16, 2013 at 1:34 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
But very slow even on small examples ... Do you use a magic trick to enhance the performance ?
Not really.
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Does this make sense to you? I would like to have this as a student project for next semester
Alexandre
On Oct 16, 2013, at 11:27 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
It would be great to have a domain specific force based layout.
For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class.
Alexandre
On Oct 16, 2013, at 11:09 AM, Tudor Girba tudor@tudorgirba.com wrote:
System Attraction is pretty, but slow due to the complexity of the force based layout.
Doru
On Wed, Oct 16, 2013 at 1:34 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
But very slow even on small examples ... Do you use a magic trick to enhance the performance ?
Not really.
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Just floating a random idea that reoccurs to me over time.
For an object model you have a hierarchical structure for class inheritance and orthogonally you have a network structure with relationships between classes. It would be interesting to combine a radial tree for the hierarchical structure with a force layout that attracts classes along the circumferential lines to minimize the distance of relationships. Something like the attached pic. Where circumferential lines would otherwise overlap, they need to be offset.
Its not something I've got time to work on at the moment, but thought others might find the idea interesting.
cheers -ben
Alexandre Bergel wrote:
Does this make sense to you? I would like to have this as a student project for next semester
Alexandre
On Oct 16, 2013, at 11:27 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
It would be great to have a domain specific force based layout.
For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class.
Alexandre
On Oct 16, 2013, at 11:09 AM, Tudor Girba tudor@tudorgirba.com wrote:
System Attraction is pretty, but slow due to the complexity of the force based layout.
Doru
On Wed, Oct 16, 2013 at 1:34 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
But very slow even on small examples ... Do you use a magic trick to enhance the performance ?
Not really.
Alexandre
On Wed, Oct 16, 2013 at 4:27 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
It would be great to have a domain specific force based layout.
For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class.
I like the idea, but what do you mean by domain-specific ? Do you want to visualize something else than software ?
For example, if you want to connect methods with their defining classes, and have many classes on screen. It is more important to have a strong repulsion between the classes, than having the methods of a class repulsing from methods from another class.
I like the idea, but what do you mean by domain-specific ? Do you want to visualize something else than software ?
The force base layout gives to all the edges and nodes the same value. But maybe, if you can tell that some nodes are more important than other, then the complexity can be significantly reduced.
The algo can be used for anything that is represented as a graph.
Alexandre
-
Alexandre Bergel -
Andre Hora -
Ben Coman -
Serge Stinckwich -
Tudor Girba