I have decided that for the first JTIN module, I am
going to write out an interface hierarchy that will
cover most if not all the roadmap I have previously
posted. While there wont be any executable code, it
will be heavily javadocd.
In the process of laying out the interface structure,
all the global design decisions must be made. Once
this is done, and done right, implementation becomes
almost trivial.
This should fill the week, with most of the time
devoted to studying various libraries and frameworks
that will be needed. I love code reuse, but there is a
learning curve associated with each API utilized.
This is the most important part of the project, so
once I get the interfaces done, I would like as much
comment/criticism as I can get before I go forward
with implementation.
--Christopher
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
