Re: Maven Diagram Maker

[Ralph Goers]

Piotr Tabor wrote:

OK. Thanks. In fact I had switched to JAI ( Java Advanced Imaging API
https://jai.dev.java.net/) - but I didn't corrected all places in my
proposal. It's licensed on Java Reasearch License and Java Distribution
License (JDL) . I don't know how
about compatibility with ASL (JDL & JRL are not listed on the 3party
page). JAI is  already in Maven Repository (javax.media:jai_core) and I
would like to use its binary version only (no source modifications).

If mustn't, I will use another graphic "writer" -> any propositions ?

Piotr Tabor

  
The site says the link above is for commercial use of the source code. 
The download for version 1.1.3 has a binary license at 
http://download.java.net/media/jai/builds/release/1_1_3/LICENSE-jai.txt. 
This license isn't on the approved list and would need to be submitted, 
but I'd be surprised if there were any problems with it.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Jason van Zyl]

On 12 May 07, at 9:31 AM 12 May 07, Ralph Goers wrote:


Piotr Tabor wrote:

Done: http://docs.codehaus.org/display/MAVENUSER/Maven+Diagram+Maker



I'm not sure that Jimi's license is acceptable according to http:// 
people.apache.org/~cliffs/3party.html. You would need to get  
verification that it's inclusion is approved before using it.




If we have a good tool and can't use it because of licensing  
restrictions then we'll put it somewhere else.


Jason.


Ralph

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Jason van Zyl]

On 12 May 07, at 4:28 AM 12 May 07, Piotr Tabor wrote:


Done: http://docs.codehaus.org/display/MAVENUSER/Maven+Diagram+Maker



Great, thanks.

Jason.


Piotr Tabor

Jason van Zyl pisze:

I still think a summary in the wiki is the best place to start. This
will get lost amidst the noise.


On 11 May 07, at 4:22 AM 11 May 07, Piotr Tabor wrote:

I will create this summer (as a Google Summer of Code participant  
- with

Jason van Zyl as a mentor)
a software system that will allow, during the build process of a
project, to automatically generate
diagrams of chosen aspects of the project.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Jason van Zyl]

On 11 May 07, at 11:25 PM 11 May 07, Milos Kleint wrote:


On 5/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:




i'm not sure about the IDE integration usefulness. The workflow in IDE
is a bit different from the proposed one.

(Speaking of dependency graph only now)
In the IDE you want interactivity with the optional persistence of the
visual data. You want filters, finding specific artifacts in the tree,
getting more information about them, answering questions like "why was
this artifact included? why it changed scope or version?". And you
want to take corrective action, like forcing a different version or
excluding a certain transitive dependency.



Right, that's what I'm talking about. A diagram by itself is not all  
that useful if you can't do anything with it.


Jason.


On top of that layouting complex dependencies  with a lot of
transitivity is extremely difficult even if you use some advanced
algorithms. (I've done experiments layouts coming with jung, jgraph
etc) so I'm somewhat sceptical towards the practical usefulness of an
automated generation of jpeg pictures apart from being nice demoware
in simple projects.

Regards

Milos

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Piotr Tabor]

Peter Kolbus wrote
> First: My experience so far has been that Prefuse can create simple
> shapes (boxes, ellipses, etc) and does an excellent job with those in
> forced ("spring-loaded") layouts, but won't be appropriate for shapes as
> complex as UML classes and components, since Prefuse shapes are defined
> via enumeration (Constants.SHAPE_*) rather than subclassing.
>   
I know. In fact:
a) Boxes are enough to generate simple graphs (of classes, of
dependencies, of xml schema).
b) I think - I can write my own Renderer class - that will support
UML-like borders (the CONSTANT.SHAPE_ - is mostly too
inform prefuse about area of the object  - for collisions
c) We can use only "simple" renderer to prepare only outline. And
then (in far feature) use the coordinates to prepare UML (XMI) file.
> A second concern that I have for Piotr with the use of Prefuse for
> static diagrams is that Prefuse uses the AWT for rendering; this may
> cause problems on a UNIX build host that doesn't have a running X
> server.  This is based on a vague memory, but it bears testing if this
> sort of environment is a priority.
>   
I hope I can use the layout algorithms without any display (swing) - but
calculate
the coordinates - and use them - to render image.
> Finally, in static diagrams, there is a certain polish provided by
> snapping shapes to a grid, and having shapes that align with each
> other.  With Prefuse, the user immediately gets the sense that edges in
> the graph are springs, so the smoothness of the animation gets a higher
> priority.
>   
If user don't like the automatic layout - he will have to lock all
nodes...  - and he
will get exactly what he want.
> I can't say that I have any better toolkits in mind, though, so I'm not
> going to argue whether Prefuse is the best platform available for the job. 
>
> Peter
>   
Piotr

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Piotr Tabor]

Ralph Goers pisze:
> Piotr Tabor wrote:
>> Done: http://docs.codehaus.org/display/MAVENUSER/Maven+Diagram+Maker   
> I'm not sure that Jimi's license is acceptable according to
> http://people.apache.org/~cliffs/3party.html. You would need to get
> verification that it's inclusion is approved before using it.
>
> Ralph
OK. Thanks. In fact I had switched to JAI ( Java Advanced Imaging API
https://jai.dev.java.net/) - but I didn't corrected all places in my
proposal. It's licensed on Java Reasearch License and Java Distribution
License (JDL) <https://jai.dev.java.net/jdl-jai.pdf>. I don't know how
about compatibility with ASL (JDL & JRL are not listed on the 3party
page). JAI is  already in Maven Repository (javax.media:jai_core) and I
would like to use its binary version only (no source modifications).

If mustn't, I will use another graphic "writer" -> any propositions ?

Piotr Tabor

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Milos Kleint]

you might want to consider

http://graph.netbeans.org/
http://graph.netbeans.org/screenshots.html

it doesn't have any of the advanced graph layouts by it's own. Not
sure if they are planned. However it handles complex shapes, UI
interaction and effects quite well.

it's independent of netbeans and can be used in any swing app. (not
based on swing though) not sure about awt only.

Milos

BTW: I've done some experiments with dependency graph within netbeans
using this library at the mevenide project.

On 5/12/07, Peter Kolbus <[EMAIL PROTECTED]> wrote:

I've been spending the last couple of days with Prefuse with the
intention of creating a Maven plugin to implement the Dependency
Graphing proposal
(http://docs.codehaus.org/display/MAVEN/Dependency+Graphing), also for
Google Summer of Code.  I have three concerns about the appropriateness
of Prefuse for generating static UML-like diagrams.

First: My experience so far has been that Prefuse can create simple
shapes (boxes, ellipses, etc) and does an excellent job with those in
forced ("spring-loaded") layouts, but won't be appropriate for shapes as
complex as UML classes and components, since Prefuse shapes are defined
via enumeration (Constants.SHAPE_*) rather than subclassing.

A second concern that I have for Piotr with the use of Prefuse for
static diagrams is that Prefuse uses the AWT for rendering; this may
cause problems on a UNIX build host that doesn't have a running X
server.  This is based on a vague memory, but it bears testing if this
sort of environment is a priority.

Finally, in static diagrams, there is a certain polish provided by
snapping shapes to a grid, and having shapes that align with each
other.  With Prefuse, the user immediately gets the sense that edges in
the graph are springs, so the smoothness of the animation gets a higher
priority.

I can't say that I have any better toolkits in mind, though, so I'm not
going to argue whether Prefuse is the best platform available for the job.

Peter

Evan Worley wrote:
> As for the graph and layout, I can attest that the Piotr has selecting
> the
> best graphing platform available.  Prefuse has been able to do leaps and
> bounds more than jung or jgraph, so I would be optimistic about his
> ability
> to manage the layout.
>
> Evan
>
> On 5/11/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
>>
>> On 5/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>> >
>> > On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote:
>> >
>> > > On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:
>> > >> I would like to provide two components: a graphical editor and a
>> > >> Maven
>> > >> plug-in.
>> > >> 'The Graphical Editor will offer live (WYSIWYG) preparation of a
>> > >> graphical presentation of the project by setting such properties
>> as:
>> > >>  - Type and subset of data, we want to present,
>> > >>  - What part of the data is to be presented,
>> > >>  - The method of presenting of each type of diagram nodes
>> > >> (that is,
>> > >> what attributes of the item will be displayed), and the general
>> > >> 'style'
>> > >> of the presentation. I would like to provide UML-like design.
>> > >> - The general layout algorithm
>> > >> - The positions of selected locked nodes – which we want to
>> > >> put in a
>> > >> fixed area. All other nodes will be positioned automatically.
>> > >> The schema of the diagram created by the editor will be saved to
>> > >> an XML
>> > >> file.
>> > >> Additionally the editor may be used as a graphical browser
>> > >> (explorer) of
>> > >> chosen aspects of the project. The editor will use the Prefuse
>> > >> library
>> > >> (http://prefuse.org).
>> > >>
>> > >> The Maven Plug-in (maven-graph-plugin) – will be using the XML file
>> > >> prepared by the Graphical Editor and the current state of
>> project to
>> > >> prepare images in various graphic formats (JPG, TIFF, PNG and
>> others
>> > >> supported by the Sun JAI library
>> > >> (http://java.sun.com/javase/technologies/desktop/media/jai/). The
>> > >> plug-in will be able to prepare
>> > >> the HTML  tag for the picture too (to create an active area
>> > >> on web
>> > >> page containing the image). The resulting file will be ready  to
>> > >> use in
>> > >> the next Maven phases by Doxia or other documenting tool.
>> > >
>> > > Does this mean we can export the graph of dependencies in a UML
>> > > format?
>> >
>> > It's not a priority, but I'm sure it could be done. It's just going
>> > to be a general graph model that can be attached to various sinks, or
>> > a sink model (for ui tools) so you can easily add it. IDE integration
>> > is the primary target.
>>
>>
>> i'm not sure about the IDE integration usefulness. The workflow in IDE
>> is a bit different from the proposed one.
>>
>> (Speaking of dependency graph only now)
>> In the IDE you want interactivity with the optional persistence of the
>> visual data. You want filters, finding specific artifacts in the tree,
>> getting more information abou

Re: Maven Diagram Maker

[Peter Kolbus]

I've been spending the last couple of days with Prefuse with the
intention of creating a Maven plugin to implement the Dependency
Graphing proposal
(http://docs.codehaus.org/display/MAVEN/Dependency+Graphing), also for
Google Summer of Code.  I have three concerns about the appropriateness
of Prefuse for generating static UML-like diagrams.

First: My experience so far has been that Prefuse can create simple
shapes (boxes, ellipses, etc) and does an excellent job with those in
forced ("spring-loaded") layouts, but won't be appropriate for shapes as
complex as UML classes and components, since Prefuse shapes are defined
via enumeration (Constants.SHAPE_*) rather than subclassing.

A second concern that I have for Piotr with the use of Prefuse for
static diagrams is that Prefuse uses the AWT for rendering; this may
cause problems on a UNIX build host that doesn't have a running X
server.  This is based on a vague memory, but it bears testing if this
sort of environment is a priority.

Finally, in static diagrams, there is a certain polish provided by
snapping shapes to a grid, and having shapes that align with each
other.  With Prefuse, the user immediately gets the sense that edges in
the graph are springs, so the smoothness of the animation gets a higher
priority.

I can't say that I have any better toolkits in mind, though, so I'm not
going to argue whether Prefuse is the best platform available for the job. 

Peter

Evan Worley wrote:
> As for the graph and layout, I can attest that the Piotr has selecting
> the
> best graphing platform available.  Prefuse has been able to do leaps and
> bounds more than jung or jgraph, so I would be optimistic about his
> ability
> to manage the layout.
>
> Evan
>
> On 5/11/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
>>
>> On 5/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>> >
>> > On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote:
>> >
>> > > On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:
>> > >> I would like to provide two components: a graphical editor and a
>> > >> Maven
>> > >> plug-in.
>> > >> 'The Graphical Editor will offer live (WYSIWYG) preparation of a
>> > >> graphical presentation of the project by setting such properties
>> as:
>> > >>  - Type and subset of data, we want to present,
>> > >>  - What part of the data is to be presented,
>> > >>  - The method of presenting of each type of diagram nodes
>> > >> (that is,
>> > >> what attributes of the item will be displayed), and the general
>> > >> 'style'
>> > >> of the presentation. I would like to provide UML-like design.
>> > >> - The general layout algorithm
>> > >> - The positions of selected locked nodes – which we want to
>> > >> put in a
>> > >> fixed area. All other nodes will be positioned automatically.
>> > >> The schema of the diagram created by the editor will be saved to
>> > >> an XML
>> > >> file.
>> > >> Additionally the editor may be used as a graphical browser
>> > >> (explorer) of
>> > >> chosen aspects of the project. The editor will use the Prefuse
>> > >> library
>> > >> (http://prefuse.org).
>> > >>
>> > >> The Maven Plug-in (maven-graph-plugin) – will be using the XML file
>> > >> prepared by the Graphical Editor and the current state of
>> project to
>> > >> prepare images in various graphic formats (JPG, TIFF, PNG and
>> others
>> > >> supported by the Sun JAI library
>> > >> (http://java.sun.com/javase/technologies/desktop/media/jai/). The
>> > >> plug-in will be able to prepare
>> > >> the HTML  tag for the picture too (to create an active area
>> > >> on web
>> > >> page containing the image). The resulting file will be ready  to
>> > >> use in
>> > >> the next Maven phases by Doxia or other documenting tool.
>> > >
>> > > Does this mean we can export the graph of dependencies in a UML
>> > > format?
>> >
>> > It's not a priority, but I'm sure it could be done. It's just going
>> > to be a general graph model that can be attached to various sinks, or
>> > a sink model (for ui tools) so you can easily add it. IDE integration
>> > is the primary target.
>>
>>
>> i'm not sure about the IDE integration usefulness. The workflow in IDE
>> is a bit different from the proposed one.
>>
>> (Speaking of dependency graph only now)
>> In the IDE you want interactivity with the optional persistence of the
>> visual data. You want filters, finding specific artifacts in the tree,
>> getting more information about them, answering questions like "why was
>> this artifact included? why it changed scope or version?". And you
>> want to take corrective action, like forcing a different version or
>> excluding a certain transitive dependency.
>>
>> On top of that layouting complex dependencies  with a lot of
>> transitivity is extremely difficult even if you use some advanced
>> algorithms. (I've done experiments layouts coming with jung, jgraph
>> etc) so I'm somewhat sceptical towards the practical usefulness of an
>> automated generation of jpeg pictures apart fro

Re: Maven Diagram Maker

[Carlos Sanchez]

yep, it's here http://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/grafo/

samples in http://people.apache.org/~carlos/grafo/

I'm copying Peter Kolbus as he's going to be working on this in the
Summer of Code program under my mentorship


On 5/12/07, Brett Porter <[EMAIL PROTECTED]> wrote:

Sorry, I was horribly vague. A few people have been toying with
graphing libraries and there is some code in the sandbox that uses
prefuse already, which it would be great to reuse.

- Brett

On 12/05/2007, at 11:03 AM, Evan Worley wrote:

> While I don't know all the details of prefuse, I don't believe so.
> It seems
> to be a fresh approach and I think the layout algorithms were the
> result of
> one of the developer's Ph.D thesis.
>
> I have done a few prototypes with prefuse and I was extremely
> impressed.
> This was after trying a handful of other java graphing libraries.
>
> Evan
>
> On 5/12/07, Brett Porter <[EMAIL PROTECTED]> wrote:
>>
>>
>> On 12/05/2007, at 12:31 AM, Evan Worley wrote:
>>
>> > As for the graph and layout, I can attest that the Piotr has
>> > selecting the
>> > best graphing platform available.  Prefuse has been able to do
>> > leaps and
>> > bounds more than jung or jgraph, so I would be optimistic about his
>> > ability
>> > to manage the layout.
>>
>> Is this re-using the existing attempts already made for graphing?
>>
>> - Brett
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Brett Porter]

Sorry, I was horribly vague. A few people have been toying with  
graphing libraries and there is some code in the sandbox that uses  
prefuse already, which it would be great to reuse.


- Brett

On 12/05/2007, at 11:03 AM, Evan Worley wrote:

While I don't know all the details of prefuse, I don't believe so.   
It seems
to be a fresh approach and I think the layout algorithms were the  
result of

one of the developer's Ph.D thesis.

I have done a few prototypes with prefuse and I was extremely  
impressed.

This was after trying a handful of other java graphing libraries.

Evan

On 5/12/07, Brett Porter <[EMAIL PROTECTED]> wrote:



On 12/05/2007, at 12:31 AM, Evan Worley wrote:

> As for the graph and layout, I can attest that the Piotr has
> selecting the
> best graphing platform available.  Prefuse has been able to do
> leaps and
> bounds more than jung or jgraph, so I would be optimistic about his
> ability
> to manage the layout.

Is this re-using the existing attempts already made for graphing?

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Evan Worley]

While I don't know all the details of prefuse, I don't believe so.  It seems
to be a fresh approach and I think the layout algorithms were the result of
one of the developer's Ph.D thesis.

I have done a few prototypes with prefuse and I was extremely impressed.
This was after trying a handful of other java graphing libraries.

Evan

On 5/12/07, Brett Porter <[EMAIL PROTECTED]> wrote:



On 12/05/2007, at 12:31 AM, Evan Worley wrote:

> As for the graph and layout, I can attest that the Piotr has
> selecting the
> best graphing platform available.  Prefuse has been able to do
> leaps and
> bounds more than jung or jgraph, so I would be optimistic about his
> ability
> to manage the layout.

Is this re-using the existing attempts already made for graphing?

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Brett Porter]

On 12/05/2007, at 12:31 AM, Evan Worley wrote:

As for the graph and layout, I can attest that the Piotr has  
selecting the
best graphing platform available.  Prefuse has been able to do  
leaps and
bounds more than jung or jgraph, so I would be optimistic about his  
ability

to manage the layout.


Is this re-using the existing attempts already made for graphing?

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Ralph Goers]

Piotr Tabor wrote:

Done: http://docs.codehaus.org/display/MAVENUSER/Maven+Diagram+Maker


  
I'm not sure that Jimi's license is acceptable according to 
http://people.apache.org/~cliffs/3party.html. You would need to get 
verification that it's inclusion is approved before using it.


Ralph

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Piotr Tabor]

I know that there are *big* problems with automatic layout with nearly
every tool. So it is the reason
why I am going to provide possibility to "lock nodes". The "locked" node
will be assigned to final position - and layout
strategy mustn't move it. 

It will be difficult - i think - in prefuse to get possibility of
locking nodes - but I will try. At least it is possible with
ForceDirectedLayout *
*(I can add very strong force from "fixed position" to the node) .

Thanks,
Piotr*

*Evan Worley pisze:
> As for the graph and layout, I can attest that the Piotr has selecting
> the
> best graphing platform available.  Prefuse has been able to do leaps and
> bounds more than jung or jgraph, so I would be optimistic about his
> ability
> to manage the layout.
>
> Evan
>
> On 5/11/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
>>
>> On 5/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>> >
>> > On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote:
>> >
>> > > On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:
>> > >> I would like to provide two components: a graphical editor and a
>> > >> Maven
>> > >> plug-in.
>> > >> 'The Graphical Editor will offer live (WYSIWYG) preparation of a
>> > >> graphical presentation of the project by setting such properties
>> as:
>> > >>  - Type and subset of data, we want to present,
>> > >>  - What part of the data is to be presented,
>> > >>  - The method of presenting of each type of diagram nodes
>> > >> (that is,
>> > >> what attributes of the item will be displayed), and the general
>> > >> 'style'
>> > >> of the presentation. I would like to provide UML-like design.
>> > >> - The general layout algorithm
>> > >> - The positions of selected locked nodes – which we want to
>> > >> put in a
>> > >> fixed area. All other nodes will be positioned automatically.
>> > >> The schema of the diagram created by the editor will be saved to
>> > >> an XML
>> > >> file.
>> > >> Additionally the editor may be used as a graphical browser
>> > >> (explorer) of
>> > >> chosen aspects of the project. The editor will use the Prefuse
>> > >> library
>> > >> (http://prefuse.org).
>> > >>
>> > >> The Maven Plug-in (maven-graph-plugin) – will be using the XML file
>> > >> prepared by the Graphical Editor and the current state of
>> project to
>> > >> prepare images in various graphic formats (JPG, TIFF, PNG and
>> others
>> > >> supported by the Sun JAI library
>> > >> (http://java.sun.com/javase/technologies/desktop/media/jai/). The
>> > >> plug-in will be able to prepare
>> > >> the HTML  tag for the picture too (to create an active area
>> > >> on web
>> > >> page containing the image). The resulting file will be ready  to
>> > >> use in
>> > >> the next Maven phases by Doxia or other documenting tool.
>> > >
>> > > Does this mean we can export the graph of dependencies in a UML
>> > > format?
>> >
>> > It's not a priority, but I'm sure it could be done. It's just going
>> > to be a general graph model that can be attached to various sinks, or
>> > a sink model (for ui tools) so you can easily add it. IDE integration
>> > is the primary target.
>>
>>
>> i'm not sure about the IDE integration usefulness. The workflow in IDE
>> is a bit different from the proposed one.
>>
>> (Speaking of dependency graph only now)
>> In the IDE you want interactivity with the optional persistence of the
>> visual data. You want filters, finding specific artifacts in the tree,
>> getting more information about them, answering questions like "why was
>> this artifact included? why it changed scope or version?". And you
>> want to take corrective action, like forcing a different version or
>> excluding a certain transitive dependency.
>>
>> On top of that layouting complex dependencies  with a lot of
>> transitivity is extremely difficult even if you use some advanced
>> algorithms. (I've done experiments layouts coming with jung, jgraph
>> etc) so I'm somewhat sceptical towards the practical usefulness of an
>> automated generation of jpeg pictures apart from being nice demoware
>> in simple projects.
>>
>> Regards
>>
>> Milos
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Piotr Tabor]

Done: http://docs.codehaus.org/display/MAVENUSER/Maven+Diagram+Maker

Piotr Tabor

Jason van Zyl pisze:
> I still think a summary in the wiki is the best place to start. This
> will get lost amidst the noise.
>
>
> On 11 May 07, at 4:22 AM 11 May 07, Piotr Tabor wrote:
>
>> I will create this summer (as a Google Summer of Code participant - with
>> Jason van Zyl as a mentor)
>> a software system that will allow, during the build process of a
>> project, to automatically generate
>> diagrams of chosen aspects of the project.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Evan Worley]

As for the graph and layout, I can attest that the Piotr has selecting the
best graphing platform available.  Prefuse has been able to do leaps and
bounds more than jung or jgraph, so I would be optimistic about his ability
to manage the layout.

Evan

On 5/11/07, Milos Kleint <[EMAIL PROTECTED]> wrote:


On 5/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote:
>
> > On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:
> >> I would like to provide two components: a graphical editor and a
> >> Maven
> >> plug-in.
> >> 'The Graphical Editor will offer live (WYSIWYG) preparation of a
> >> graphical presentation of the project by setting such properties as:
> >>  - Type and subset of data, we want to present,
> >>  - What part of the data is to be presented,
> >>  - The method of presenting of each type of diagram nodes
> >> (that is,
> >> what attributes of the item will be displayed), and the general
> >> 'style'
> >> of the presentation. I would like to provide UML-like design.
> >> - The general layout algorithm
> >> - The positions of selected locked nodes – which we want to
> >> put in a
> >> fixed area. All other nodes will be positioned automatically.
> >> The schema of the diagram created by the editor will be saved to
> >> an XML
> >> file.
> >> Additionally the editor may be used as a graphical browser
> >> (explorer) of
> >> chosen aspects of the project. The editor will use the Prefuse
> >> library
> >> (http://prefuse.org).
> >>
> >> The Maven Plug-in (maven-graph-plugin) – will be using the XML file
> >> prepared by the Graphical Editor and the current state of project to
> >> prepare images in various graphic formats (JPG, TIFF, PNG and others
> >> supported by the Sun JAI library
> >> (http://java.sun.com/javase/technologies/desktop/media/jai/). The
> >> plug-in will be able to prepare
> >> the HTML  tag for the picture too (to create an active area
> >> on web
> >> page containing the image). The resulting file will be ready  to
> >> use in
> >> the next Maven phases by Doxia or other documenting tool.
> >
> > Does this mean we can export the graph of dependencies in a UML
> > format?
>
> It's not a priority, but I'm sure it could be done. It's just going
> to be a general graph model that can be attached to various sinks, or
> a sink model (for ui tools) so you can easily add it. IDE integration
> is the primary target.


i'm not sure about the IDE integration usefulness. The workflow in IDE
is a bit different from the proposed one.

(Speaking of dependency graph only now)
In the IDE you want interactivity with the optional persistence of the
visual data. You want filters, finding specific artifacts in the tree,
getting more information about them, answering questions like "why was
this artifact included? why it changed scope or version?". And you
want to take corrective action, like forcing a different version or
excluding a certain transitive dependency.

On top of that layouting complex dependencies  with a lot of
transitivity is extremely difficult even if you use some advanced
algorithms. (I've done experiments layouts coming with jung, jgraph
etc) so I'm somewhat sceptical towards the practical usefulness of an
automated generation of jpeg pictures apart from being nice demoware
in simple projects.

Regards

Milos

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Milos Kleint]

On 5/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:


On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote:

> On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:
>> I would like to provide two components: a graphical editor and a
>> Maven
>> plug-in.
>> 'The Graphical Editor will offer live (WYSIWYG) preparation of a
>> graphical presentation of the project by setting such properties as:
>>  - Type and subset of data, we want to present,
>>  - What part of the data is to be presented,
>>  - The method of presenting of each type of diagram nodes
>> (that is,
>> what attributes of the item will be displayed), and the general
>> 'style'
>> of the presentation. I would like to provide UML-like design.
>> - The general layout algorithm
>> - The positions of selected locked nodes – which we want to
>> put in a
>> fixed area. All other nodes will be positioned automatically.
>> The schema of the diagram created by the editor will be saved to
>> an XML
>> file.
>> Additionally the editor may be used as a graphical browser
>> (explorer) of
>> chosen aspects of the project. The editor will use the Prefuse
>> library
>> (http://prefuse.org).
>>
>> The Maven Plug-in (maven-graph-plugin) – will be using the XML file
>> prepared by the Graphical Editor and the current state of project to
>> prepare images in various graphic formats (JPG, TIFF, PNG and others
>> supported by the Sun JAI library
>> (http://java.sun.com/javase/technologies/desktop/media/jai/). The
>> plug-in will be able to prepare
>> the HTML  tag for the picture too (to create an active area
>> on web
>> page containing the image). The resulting file will be ready  to
>> use in
>> the next Maven phases by Doxia or other documenting tool.
>
> Does this mean we can export the graph of dependencies in a UML
> format?

It's not a priority, but I'm sure it could be done. It's just going
to be a general graph model that can be attached to various sinks, or
a sink model (for ui tools) so you can easily add it. IDE integration
is the primary target.



i'm not sure about the IDE integration usefulness. The workflow in IDE
is a bit different from the proposed one.

(Speaking of dependency graph only now)
In the IDE you want interactivity with the optional persistence of the
visual data. You want filters, finding specific artifacts in the tree,
getting more information about them, answering questions like "why was
this artifact included? why it changed scope or version?". And you
want to take corrective action, like forcing a different version or
excluding a certain transitive dependency.

On top of that layouting complex dependencies  with a lot of
transitivity is extremely difficult even if you use some advanced
algorithms. (I've done experiments layouts coming with jung, jgraph
etc) so I'm somewhat sceptical towards the practical usefulness of an
automated generation of jpeg pictures apart from being nice demoware
in simple projects.

Regards

Milos

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Jason van Zyl]

I still think a summary in the wiki is the best place to start. This  
will get lost amidst the noise.


Then I will go from there with a response.

Thanks for putting the material together though, a great start.

Jason.

On 11 May 07, at 4:22 AM 11 May 07, Piotr Tabor wrote:

I will create this summer (as a Google Summer of Code participant -  
with

Jason van Zyl as a mentor)
a software system that will allow, during the build process of a
project, to automatically generate
diagrams of chosen aspects of the project.

I would like to start community discussion about the details -
to provide very useful tool. I know - the mail is very long,
but decisions  made now will be essential. So:
*please read and constructive comment*.

I would like to provide two components: a graphical editor and a Maven
plug-in.
'The Graphical Editor will offer live (WYSIWYG) preparation of a
graphical presentation of the project by setting such properties as:
 - Type and subset of data, we want to present,
 - What part of the data is to be presented,
 - The method of presenting of each type of diagram nodes (that  
is,
what attributes of the item will be displayed), and the general  
'style'

of the presentation. I would like to provide UML-like design.
- The general layout algorithm
- The positions of selected locked nodes – which we want to put  
in a

fixed area. All other nodes will be positioned automatically.
The schema of the diagram created by the editor will be saved to an  
XML

file.
Additionally the editor may be used as a graphical browser  
(explorer) of

chosen aspects of the project. The editor will use the Prefuse library
(http://prefuse.org).

The Maven Plug-in (maven-graph-plugin) – will be using the XML file
prepared by the Graphical Editor and the current state of project to
prepare images in various graphic formats (JPG, TIFF, PNG and others
supported by the Sun JAI library
(http://java.sun.com/javase/technologies/desktop/media/jai/). The
plug-in will be able to prepare
the HTML  tag for the picture too (to create an active area on  
web
page containing the image). The resulting file will be ready  to  
use in

the next Maven phases by Doxia or other documenting tool.

The maven-graph-plugin will cope with changes in the project made  
after

generating the schema XML file.  This means that if an object from the
XML file is no longer exists in the project, it won't be visible in  
the

picture. It also means that if the object is new, it will be placed in
the picture (in a place calculated by the general layout strategy  
set in

the XML file).
Additionally the user will be warned about any discrepancies  
between the

expected and actual data and problems with finding space for a new
object. The diagram generation will not modify the XML file, but will
only try to interpret it for the current situation.

During Google Summer of Code time I wish I prepare two connectors
(possibilities to visualize an aspect of project):
- Dependencies diagram connector – to visualize the chosen  
project's

subset of the dependencies (internal or external, up to a configured
depth or/and included in a given scope). It will be also possible to
exclude some dependencies from the diagram.
- Class diagram – to visualize the inheritance and composition
aspects of the class hierarchy. The information will be obtained by
reflection.

Of course the mechanism of the connectors will be universal enough to
make the addition of a new aspect of a project as simple as possible.

    Why „Maven Diagram-Maker"?
There are no good, free tools to prepare diagrams –
especially such that would automatically generate diagrams from the
source code and project descriptors. On the other hand, good and
up-to-date documentation is a very important part of software
development process – particularly in the Open Source world, where
documentation is critical to help many people work on projects. On the
other hand, nobody likes preparing documents and diagrams.
To make the matters worse, using standard one-time diagrammers  
helps
only for a short period of time. In fast growing projects, the  
pictures

become obsolete very quickly. They start to mislead. Therefore I think
that adding possibility to generate actual up-to-date diagrams in the
build process is a very important idea – and Maven is the perfect
environment to do that.

Java developers can nowadays use very good text documenting tools,
such a JavaDoc and Doxia, but the lack of methods to prepare and
incorporate actual visual information in the documents is a very  
serious

shortcoming of those tools.

Planned editor features

The Graphical Editor will help the user create and edit the
visualization schema XML file. The file will contain two types of
information:
- The  section will describe which data will be  
presented,

that is - how to acquire the information to present. The classes and
attributes of conn

Re: Maven Diagram Maker

[Rahul Thakur]

This is interesting.

Might be a good idea to post these notes to the Wiki and keep the 
consolidated the discussion consolidated in one place.


Rahul

- Original Message - 
From: "Piotr Tabor" <[EMAIL PROTECTED]>

To: "Maven Developers List" 
Sent: Friday, May 11, 2007 11:22 PM
Subject: Maven Diagram Maker


I will create this summer (as a Google Summer of Code participant - 
with

Jason van Zyl as a mentor)
a software system that will allow, during the build process of a
project, to automatically generate
diagrams of chosen aspects of the project.

I would like to start community discussion about the details -
to provide very useful tool. I know - the mail is very long,
but decisions  made now will be essential. So:
*please read and constructive comment*.

I would like to provide two components: a graphical editor and a Maven
plug-in.
'The Graphical Editor will offer live (WYSIWYG) preparation of a
graphical presentation of the project by setting such properties as:
- Type and subset of data, we want to present,
- What part of the data is to be presented,
- The method of presenting of each type of diagram nodes (that is,
what attributes of the item will be displayed), and the general 
'style'

of the presentation. I would like to provide UML-like design.
   - The general layout algorithm
   - The positions of selected locked nodes – which we want to put in 
a

fixed area. All other nodes will be positioned automatically.
The schema of the diagram created by the editor will be saved to an 
XML

file.
Additionally the editor may be used as a graphical browser (explorer) 
of

chosen aspects of the project. The editor will use the Prefuse library
(http://prefuse.org).

The Maven Plug-in (maven-graph-plugin) – will be using the XML file
prepared by the Graphical Editor and the current state of project to
prepare images in various graphic formats (JPG, TIFF, PNG and others
supported by the Sun JAI library
(http://java.sun.com/javase/technologies/desktop/media/jai/). The
plug-in will be able to prepare
the HTML  tag for the picture too (to create an active area on 
web
page containing the image). The resulting file will be ready  to use 
in

the next Maven phases by Doxia or other documenting tool.

The maven-graph-plugin will cope with changes in the project made 
after

generating the schema XML file.  This means that if an object from the
XML file is no longer exists in the project, it won't be visible in 
the

picture. It also means that if the object is new, it will be placed in
the picture (in a place calculated by the general layout strategy set 
in

the XML file).
Additionally the user will be warned about any discrepancies between 
the

expected and actual data and problems with finding space for a new
object. The diagram generation will not modify the XML file, but will
only try to interpret it for the current situation.

During Google Summer of Code time I wish I prepare two connectors
(possibilities to visualize an aspect of project):
   - Dependencies diagram connector – to visualize the chosen 
project's

subset of the dependencies (internal or external, up to a configured
depth or/and included in a given scope). It will be also possible to
exclude some dependencies from the diagram.
   - Class diagram – to visualize the inheritance and composition
aspects of the class hierarchy. The information will be obtained by
reflection.

Of course the mechanism of the connectors will be universal enough to
make the addition of a new aspect of a project as simple as possible.

   Why „Maven Diagram-Maker"?
   There are no good, free tools to prepare diagrams –
especially such that would automatically generate diagrams from the
source code and project descriptors. On the other hand, good and
up-to-date documentation is a very important part of software
development process – particularly in the Open Source world, where
documentation is critical to help many people work on projects. On the
other hand, nobody likes preparing documents and diagrams.
   To make the matters worse, using standard one-time diagrammers 
helps
only for a short period of time. In fast growing projects, the 
pictures

become obsolete very quickly. They start to mislead. Therefore I think
that adding possibility to generate actual up-to-date diagrams in the
build process is a very important idea – and Maven is the perfect
environment to do that.

   Java developers can nowadays use very good text documenting tools,
such a JavaDoc and Doxia, but the lack of methods to prepare and
incorporate actual visual information in the documents is a very 
serious

shortcoming of those tools.

Planned editor features

The Graphical Editor will help the user create and edit the
visualization schema XML file. The file will contain two types of
information:
   - The  section will describe which data will be 
presented,

that is - how to acquire the information to prese

Re: Maven Diagram Maker

[Jason van Zyl]

On 11 May 07, at 2:08 PM 11 May 07, Barrie Treloar wrote:


On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:
I would like to provide two components: a graphical editor and a  
Maven

plug-in.
'The Graphical Editor will offer live (WYSIWYG) preparation of a
graphical presentation of the project by setting such properties as:
 - Type and subset of data, we want to present,
 - What part of the data is to be presented,
 - The method of presenting of each type of diagram nodes  
(that is,
what attributes of the item will be displayed), and the general  
'style'

of the presentation. I would like to provide UML-like design.
- The general layout algorithm
- The positions of selected locked nodes – which we want to  
put in a

fixed area. All other nodes will be positioned automatically.
The schema of the diagram created by the editor will be saved to  
an XML

file.
Additionally the editor may be used as a graphical browser  
(explorer) of
chosen aspects of the project. The editor will use the Prefuse  
library

(http://prefuse.org).

The Maven Plug-in (maven-graph-plugin) – will be using the XML file
prepared by the Graphical Editor and the current state of project to
prepare images in various graphic formats (JPG, TIFF, PNG and others
supported by the Sun JAI library
(http://java.sun.com/javase/technologies/desktop/media/jai/). The
plug-in will be able to prepare
the HTML  tag for the picture too (to create an active area  
on web
page containing the image). The resulting file will be ready  to  
use in

the next Maven phases by Doxia or other documenting tool.


Does this mean we can export the graph of dependencies in a UML  
format?


It's not a priority, but I'm sure it could be done. It's just going  
to be a general graph model that can be attached to various sinks, or  
a sink model (for ui tools) so you can easily add it. IDE integration  
is the primary target.


Jason.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Diagram Maker

[Barrie Treloar]

On 5/11/07, Piotr Tabor <[EMAIL PROTECTED]> wrote:

I would like to provide two components: a graphical editor and a Maven
plug-in.
'The Graphical Editor will offer live (WYSIWYG) preparation of a
graphical presentation of the project by setting such properties as:
 - Type and subset of data, we want to present,
 - What part of the data is to be presented,
 - The method of presenting of each type of diagram nodes (that is,
what attributes of the item will be displayed), and the general 'style'
of the presentation. I would like to provide UML-like design.
- The general layout algorithm
- The positions of selected locked nodes – which we want to put in a
fixed area. All other nodes will be positioned automatically.
The schema of the diagram created by the editor will be saved to an XML
file.
Additionally the editor may be used as a graphical browser (explorer) of
chosen aspects of the project. The editor will use the Prefuse library
(http://prefuse.org).

The Maven Plug-in (maven-graph-plugin) – will be using the XML file
prepared by the Graphical Editor and the current state of project to
prepare images in various graphic formats (JPG, TIFF, PNG and others
supported by the Sun JAI library
(http://java.sun.com/javase/technologies/desktop/media/jai/). The
plug-in will be able to prepare
the HTML  tag for the picture too (to create an active area on web
page containing the image). The resulting file will be ready  to use in
the next Maven phases by Doxia or other documenting tool.


Does this mean we can export the graph of dependencies in a UML format?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven Diagram Maker

[Piotr Tabor]

I will create this summer (as a Google Summer of Code participant - with
Jason van Zyl as a mentor)
a software system that will allow, during the build process of a
project, to automatically generate
diagrams of chosen aspects of the project.

I would like to start community discussion about the details -
to provide very useful tool. I know - the mail is very long,
but decisions  made now will be essential. So:
*please read and constructive comment*.

I would like to provide two components: a graphical editor and a Maven
plug-in.
'The Graphical Editor will offer live (WYSIWYG) preparation of a
graphical presentation of the project by setting such properties as:
 - Type and subset of data, we want to present,
 - What part of the data is to be presented,
 - The method of presenting of each type of diagram nodes (that is,
what attributes of the item will be displayed), and the general 'style'
of the presentation. I would like to provide UML-like design.
- The general layout algorithm
- The positions of selected locked nodes – which we want to put in a
fixed area. All other nodes will be positioned automatically.
The schema of the diagram created by the editor will be saved to an XML
file.
Additionally the editor may be used as a graphical browser (explorer) of
chosen aspects of the project. The editor will use the Prefuse library
(http://prefuse.org).

The Maven Plug-in (maven-graph-plugin) – will be using the XML file
prepared by the Graphical Editor and the current state of project to
prepare images in various graphic formats (JPG, TIFF, PNG and others
supported by the Sun JAI library
(http://java.sun.com/javase/technologies/desktop/media/jai/). The
plug-in will be able to prepare
the HTML  tag for the picture too (to create an active area on web
page containing the image). The resulting file will be ready  to use in
the next Maven phases by Doxia or other documenting tool.

The maven-graph-plugin will cope with changes in the project made after
generating the schema XML file.  This means that if an object from the
XML file is no longer exists in the project, it won't be visible in the
picture. It also means that if the object is new, it will be placed in
the picture (in a place calculated by the general layout strategy set in
the XML file).
Additionally the user will be warned about any discrepancies between the
expected and actual data and problems with finding space for a new
object. The diagram generation will not modify the XML file, but will
only try to interpret it for the current situation.

During Google Summer of Code time I wish I prepare two connectors
(possibilities to visualize an aspect of project):
- Dependencies diagram connector – to visualize the chosen project's
subset of the dependencies (internal or external, up to a configured
depth or/and included in a given scope). It will be also possible to
exclude some dependencies from the diagram.
- Class diagram – to visualize the inheritance and composition
aspects of the class hierarchy. The information will be obtained by
reflection.

Of course the mechanism of the connectors will be universal enough to
make the addition of a new aspect of a project as simple as possible.

    Why „Maven Diagram-Maker"?
There are no good, free tools to prepare diagrams –
especially such that would automatically generate diagrams from the
source code and project descriptors. On the other hand, good and
up-to-date documentation is a very important part of software
development process – particularly in the Open Source world, where
documentation is critical to help many people work on projects. On the
other hand, nobody likes preparing documents and diagrams.
To make the matters worse, using standard one-time diagrammers helps
only for a short period of time. In fast growing projects, the pictures
become obsolete very quickly. They start to mislead. Therefore I think
that adding possibility to generate actual up-to-date diagrams in the
build process is a very important idea – and Maven is the perfect
environment to do that.

Java developers can nowadays use very good text documenting tools,
such a JavaDoc and Doxia, but the lack of methods to prepare and
incorporate actual visual information in the documents is a very serious
shortcoming of those tools.

Planned editor features

The Graphical Editor will help the user create and edit the
visualization schema XML file. The file will contain two types of
information:
- The  section will describe which data will be presented,
that is - how to acquire the information to present. The classes and
attributes of connectors, which will extract the data from the project,
will be given. No actual data will be stored in the XML file itself.


-The  section will describe how to present data. In details it
will contain:
- Perspective (coordinates of the visible area in the picture)
or the information that the whole diagr