Login | Register
My pages Projects Community openCollabNet

Discussions > dev > ANT diagrams

antelope
Discussion topic

Hide all messages in topic

All messages in topic

Re: ANT diagrams

Author Bob Tarling <bob dot tarling at ntlworld dot com>
Full name Bob Tarling <bob dot tarling at ntlworld dot com>
Date 2004-04-12 15:48:01 PDT
Message > !!! That sounds like what I was talking about, but someone else did it
> better! Do you need any help implementing the change to commons logging
> in GEF? I'd volunteer if so.
By the looks of the user guide the code changes are an extremely simple
search and replace. See http://jakarta.apach​e.org/commons/loggin​g/guide.html

I simply haven't had time to look at yet. I have several projects going on
and this hasn't really been high priority for me.

If you have time to spare then go ahead. Offer gratefully accepted. I've
given you developer status so you can commit directly back to CVS.

You'd have seen the message to Jason that I cc'ed you on. I wondered if in
my absence you may be interested in doing a piece on Antelope in his
newsletter and discuss the role of GEF/giANT in this.

Regards

Bob.


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
For additional commands, e-mail: dev-help at antelope dot tigris dot org

Re: ANT diagrams

Author Dale Anson <danson at germane-software dot com>
Full name Dale Anson <danson at germane-software dot com>
Date 2004-04-12 14:39:39 PDT
Message Hi Bob,

Please see my comments below.

Dale


Bob Tarling wrote:

> I'll have a go at building a prerelease so you can have take a look at giANT
> more easily. I'll let you know when I have it posted on the giant site.

Great! I'll keep an eye out for it.

>
>
> giANT is quite simple at the moment with imported targets. If it find a
> dependency to a target name it can't find it simply creates a 'virtual'
> target node in the graph in a different colour to a standard node, simply to
> allow all dependancies lines to be shown.

Good idea. That would also help point out "non-existant target" errors
in the build file.

>
> On logging plans see here - http://gef.tigris.or​g/issues/show_bug.cg​i?id=40
> I'd prefer logging in GEF went through commonly known logging mechanisms.
> The commons logging project seems to me to be the right way to go. I haven't
> found time to look at this as yet but luckily I may have to implement just
> the same for a project at work and so am planning to bring experience from
> this into GEF.

!!! That sounds like what I was talking about, but someone else did it
better! Do you need any help implementing the change to commons logging
in GEF? I'd volunteer if so.

>
> Bob.
>
> ----- Original Message -----
> From: "Dale Anson" <danson@germane-s​oftware.com>
> To: <dev at antelope dot tigris dot org>
> Sent: Monday, April 12, 2004 8:21 PM
> Subject: Re: ANT diagrams
>
>
>
>>Hi Bob,
>>
>>Thanks for the pointer to giANT. I didn't know about that project. It
>>looks like you're heading in the same direction I've been thinking of. I
>>have seen a few other projects doing similar graphing of Ant build
>>files, GRAND and AntGraph are two that look decent. They both rely on
>>platform specific code, though, which is what got me to looking at GEF
>>again.
>>
>>I haven't got too deep into it yet. I have 5 or 6 classes that read a
>>build file and use a JGraph to show the basic dependencies. I also want
>>to be able to recurse into <import>ed build files and to look inside
>>targets to recurse into any <ant> or <antcall> or relatives from
>>AntContrib. I'm not saving anything at all, my thought was to save the
>>graph as a build file, but it would need to be able to retain the
>>comments and formatting of the original file.
>>
>>Besides just showing a dependency graph, I also have on the roadmap the
>>ability to make build files by drag and drop. I had initially thought to
>>use a JTree and have done some preliminary work seeing if that is
>>feasible. It looks okay, it uses a tree constructed out of an Ant dtd to
>>make targets, types, and tasks and a JTree to construct the build file,
>>but I think that using a GEF approach may be a much nicer way to go.
>>
>>I haven't put any of this into cvs yet, I really should create a branch
>>and add it in, both the GEF stuff and the JTree stuff, that is.
>>
>>And for GEF, has anyone looked at abstracting the logging? It looks to
>>me like it would be fairly straight forward. There's already a package
>>for a LogManager. I think having a Logger interface that includes the
>>log4j Logger methods, then the LogManager could load the appropriate
>>logger from a configuration file setting. Another class meeting the
>>Logger interface could wrap the java.util.logging.Logger, so simply
>>changing the configuration file would be enough to use it.
>>
>>I'd like to look into your project a bit more, but off hand, it looks
>>like it would be a good fit to combine the projects. Like you, I really
>>don't want to spend a lot of time on something that you've already got a
>>good start on!
>>
>>Dale
>>
>>
>>
>>Bob Tarling wrote:
>>
>>
>>>Hi Dale
>>>
>>>I thought I'd follow up from your email on the GEF list.
>>>
>>>How are you progressing with producing dependancy diagrams in Antelope?
>>>Will any demonstration be available if I get latest CVS?
>>>
>>>I'd really like to know if my time is being wasted on the giANT project.
>>>I see no point in developing yet another ant editor myself and would be
>>>happy to combine projects.
>>>
>>>Had you put much thought into requirements of the diagram in antelope?
>>>Is it just a view or were you planning editing through the diagram also?
>>>
>>>How are you saving and retrieving diagrams? Is this as a namespace in
>>>the build script or as a seperate file?
>>>
>>>If you want to take a look at the giANT project you will have to build
>>>all of http://swidgets.tigris.org http://mdiworkbench.tigris.org and
>>>http://giant.tigris.org. I have yet to get any of these projects to
>>>their first release.
>>>
>>>Regards
>>>
>>>Bob.
>>
>>------------​--------------------​--------------------​-----------------
>>To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
>>For additional commands, e-mail: dev-help at antelope dot tigris dot org
>>
>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
> For additional commands, e-mail: dev-help at antelope dot tigris dot org
>

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
For additional commands, e-mail: dev-help at antelope dot tigris dot org

Re: ANT diagrams

Author Bob Tarling <bob dot tarling at ntlworld dot com>
Full name Bob Tarling <bob dot tarling at ntlworld dot com>
Date 2004-04-12 13:42:52 PDT
Message I'll have a go at building a prerelease so you can have take a look at giANT
more easily. I'll let you know when I have it posted on the giant site.

> to be able to recurse into <import>ed build files and to look inside
> targets to recurse into any <ant> or <antcall> or relatives from
> AntContrib.
I had planned that giANT would deal with multiple ant projects.
The plan was a screen with 3 main panels - WEST, CENTER, EAST
The WEST panel would hold the ant tree. There would be an invisible root
with a project node hanging off for each loaded project and obviously target
nodes etc under that.
The CENTER pane is a seperate diagram for each loaded project. The
http://mdiworkbench.tigris.org project allows this to be displayed either as
a set of tabbed pages or as internal frames within a JDesktopPane
The EAST pane would contain the text editor for editing the target. I had
plans to use http://syntalight.tigris.org as a simple text highlighter. This
is causing me some problems though (I prefer to call it a learning
experience).
A south panel was to hold any other properties of the current selected
target that couldn't be edited with the text editor.

giANT is quite simple at the moment with imported targets. If it find a
dependency to a target name it can't find it simply creates a 'virtual'
target node in the graph in a different colour to a standard node, simply to
allow all dependancies lines to be shown.

On logging plans see here - http://gef.tigris.or​g/issues/show_bug.cg​i?id=40
I'd prefer logging in GEF went through commonly known logging mechanisms.
The commons logging project seems to me to be the right way to go. I haven't
found time to look at this as yet but luckily I may have to implement just
the same for a project at work and so am planning to bring experience from
this into GEF.

Bob.

----- Original Message -----
From: "Dale Anson" <danson@germane-s​oftware.com>
To: <dev at antelope dot tigris dot org>
Sent: Monday, April 12, 2004 8:21 PM
Subject: Re: ANT diagrams


> Hi Bob,
>
> Thanks for the pointer to giANT. I didn't know about that project. It
> looks like you're heading in the same direction I've been thinking of. I
> have seen a few other projects doing similar graphing of Ant build
> files, GRAND and AntGraph are two that look decent. They both rely on
> platform specific code, though, which is what got me to looking at GEF
> again.
>
> I haven't got too deep into it yet. I have 5 or 6 classes that read a
> build file and use a JGraph to show the basic dependencies. I also want
> to be able to recurse into <import>ed build files and to look inside
> targets to recurse into any <ant> or <antcall> or relatives from
> AntContrib. I'm not saving anything at all, my thought was to save the
> graph as a build file, but it would need to be able to retain the
> comments and formatting of the original file.
>
> Besides just showing a dependency graph, I also have on the roadmap the
> ability to make build files by drag and drop. I had initially thought to
> use a JTree and have done some preliminary work seeing if that is
> feasible. It looks okay, it uses a tree constructed out of an Ant dtd to
> make targets, types, and tasks and a JTree to construct the build file,
> but I think that using a GEF approach may be a much nicer way to go.
>
> I haven't put any of this into cvs yet, I really should create a branch
> and add it in, both the GEF stuff and the JTree stuff, that is.
>
> And for GEF, has anyone looked at abstracting the logging? It looks to
> me like it would be fairly straight forward. There's already a package
> for a LogManager. I think having a Logger interface that includes the
> log4j Logger methods, then the LogManager could load the appropriate
> logger from a configuration file setting. Another class meeting the
> Logger interface could wrap the java.util.logging.Logger, so simply
> changing the configuration file would be enough to use it.
>
> I'd like to look into your project a bit more, but off hand, it looks
> like it would be a good fit to combine the projects. Like you, I really
> don't want to spend a lot of time on something that you've already got a
> good start on!
>
> Dale
>
>
>
> Bob Tarling wrote:
>
> > Hi Dale
> >
> > I thought I'd follow up from your email on the GEF list.
> >
> > How are you progressing with producing dependancy diagrams in Antelope?
> > Will any demonstration be available if I get latest CVS?
> >
> > I'd really like to know if my time is being wasted on the giANT project.
> > I see no point in developing yet another ant editor myself and would be
> > happy to combine projects.
> >
> > Had you put much thought into requirements of the diagram in antelope?
> > Is it just a view or were you planning editing through the diagram also?
> >
> > How are you saving and retrieving diagrams? Is this as a namespace in
> > the build script or as a seperate file?
> >
> > If you want to take a look at the giANT project you will have to build
> > all of http://swidgets.tigris.org http://mdiworkbench.tigris.org and
> > http://giant.tigris.org. I have yet to get any of these projects to
> > their first release.
> >
> > Regards
> >
> > Bob.
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
> For additional commands, e-mail: dev-help at antelope dot tigris dot org
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
For additional commands, e-mail: dev-help at antelope dot tigris dot org

Re: ANT diagrams

Author Dale Anson <danson at germane-software dot com>
Full name Dale Anson <danson at germane-software dot com>
Date 2004-04-12 12:21:11 PDT
Message Hi Bob,

Thanks for the pointer to giANT. I didn't know about that project. It
looks like you're heading in the same direction I've been thinking of. I
have seen a few other projects doing similar graphing of Ant build
files, GRAND and AntGraph are two that look decent. They both rely on
platform specific code, though, which is what got me to looking at GEF
again.

I haven't got too deep into it yet. I have 5 or 6 classes that read a
build file and use a JGraph to show the basic dependencies. I also want
to be able to recurse into <import>ed build files and to look inside
targets to recurse into any <ant> or <antcall> or relatives from
AntContrib. I'm not saving anything at all, my thought was to save the
graph as a build file, but it would need to be able to retain the
comments and formatting of the original file.

Besides just showing a dependency graph, I also have on the roadmap the
ability to make build files by drag and drop. I had initially thought to
use a JTree and have done some preliminary work seeing if that is
feasible. It looks okay, it uses a tree constructed out of an Ant dtd to
make targets, types, and tasks and a JTree to construct the build file,
but I think that using a GEF approach may be a much nicer way to go.

I haven't put any of this into cvs yet, I really should create a branch
and add it in, both the GEF stuff and the JTree stuff, that is.

And for GEF, has anyone looked at abstracting the logging? It looks to
me like it would be fairly straight forward. There's already a package
for a LogManager. I think having a Logger interface that includes the
log4j Logger methods, then the LogManager could load the appropriate
logger from a configuration file setting. Another class meeting the
Logger interface could wrap the java.util.logging.Logger, so simply
changing the configuration file would be enough to use it.

I'd like to look into your project a bit more, but off hand, it looks
like it would be a good fit to combine the projects. Like you, I really
don't want to spend a lot of time on something that you've already got a
good start on!

Dale



Bob Tarling wrote:

> Hi Dale
>
> I thought I'd follow up from your email on the GEF list.
>
> How are you progressing with producing dependancy diagrams in Antelope?
> Will any demonstration be available if I get latest CVS?
>
> I'd really like to know if my time is being wasted on the giANT project.
> I see no point in developing yet another ant editor myself and would be
> happy to combine projects.
>
> Had you put much thought into requirements of the diagram in antelope?
> Is it just a view or were you planning editing through the diagram also?
>
> How are you saving and retrieving diagrams? Is this as a namespace in
> the build script or as a seperate file?
>
> If you want to take a look at the giANT project you will have to build
> all of http://swidgets.tigris.org http://mdiworkbench.tigris.org and
> http://giant.tigris.org. I have yet to get any of these projects to
> their first release.
>
> Regards
>
> Bob.

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: dev-unsubscribe@ante​lope.tigris.org
For additional commands, e-mail: dev-help at antelope dot tigris dot org

ANT diagrams

Author Bob Tarling <bob dot tarling at ntlworld dot com>
Full name Bob Tarling <bob dot tarling at ntlworld dot com>
Date 2004-04-12 09:20:47 PDT
Message Hi Dale

I thought I'd follow up from your email on the GEF list.

How are you progressing with producing dependancy diagrams in Antelope? Will any demonstration be available if I get latest CVS?

I'd really like to know if my time is being wasted on the giANT project. I see no point in developing yet another ant editor myself and would be happy to combine projects.

Had you put much thought into requirements of the diagram in antelope? Is it just a view or were you planning editing through the diagram also?

How are you saving and retrieving diagrams? Is this as a namespace in the build script or as a seperate file?

If you want to take a look at the giANT project you will have to build all of http://swidgets.tigris.org http://mdiworkbench.tigris.org and http://giant.tigris.org. I have yet to get any of these projects to their first release.

Regards

Bob.
Attachments
Messages per page: