Re: [Wpg-proxy-development] project (re)structure

[John S. <jo...@we...>]

Alan,
I must admit to at first just sitting here shaking my head wondering why we
are going through all this, but it only took me four minutes to get ivy up
and running with your new build.xml and I sort of like it.  This is a
growing experience for me, and I will sit back and wait to look at your UML
stuff.   I have to admit never having gone through a UML design before, I
usually use the post-it note method of defining features and usage along
with my trusty wall.  

One thing I did notice, after reading your email from earlier again, you
want to use a callback mechanism rather than a registered class method?  I
believe registering a class can also be implemented as a callback method, by
simply implementing the interface in a more broad class, just as is
sometimes done in SWING, using an interface and registering it as we are
allows us to leave the implementation up to the developer, and I prefer that
to having just a callback method, which I do not personally enjoy.  I am
hoping you are using the UML design you are putting together to document how
the system currently is, rather than changing the design at the first
revision.  Can you clarify what you meant by the callback method?  I will
copy and paste it here as I see you did not send it to the mailing list:

"OK what I propose is that instead of the processor
approach we adopt a callback design using a template
method within the Proxy to do the high level stuff."

That is what confuses me, let me download and install skype as I have never
used it before either ;)
Thanks, John

 
 
-----Original Message-----
From: wpg...@li...
[mailto:wpg...@li...] On Behalf Of
Alan Moran
Sent: Tuesday, January 23, 2007 4:52 PM
To: wpg...@li...
Subject: [Wpg-proxy-development] project (re)structure

All,

I have made some reorganisation of the project
structure (the old stuff is still under version
control in case anyone thinks I've removed too much :)

First off you will need to install ivy
(http://incubator.apache.org/ivy/).  Ivy is a neat
depedency manager that retrieves JARs for you from the
internet (which it stores in a local cache in your
home directory, see ~/.ivy dir) and places copies into
your project lib directory - this means that we need
only cite which JARs are required (see ivy.xml) and it
does the rest (its uses well-known public repositories
to get the JARs for you.)  Since the JARs are cached
you can use ivy for all your other projects too
without having to download again.  See the website for
further marketing fluff.  I have added notes in
README.

To ensure Ant can work with Ivy you need to install
Ivy after downloading it and add the
~/.ivy/jars/ivy.jar to your CLASSPATH.  Then to see
ivy at work update your wpg-proxy project and issue
"ant libs" and your lib directory will be magically
filled - note that you do not need to check in these
JARs.  BTW to add a new JAR just reconfigure ivy.xml
and re-run the libs target. etc.

The new build.xml contains the usual targets with
"compile" (default) for our normal code and "test" for
unit test classes etc.  See ant -p for details.  Just
play around with the targets to see if I missed
anything.

I'll get back to the UML stuff now which is nearly
ready and have this checked in tomorrow.

Hope everything is understandable and the way we want
things - just let me know if there are any issues.

Thx,
A.








		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wpg-proxy-development mailing list
Wpg...@li...
https://lists.sourceforge.net/lists/listinfo/wpg-proxy-development