[Ijsql-devel] Re: Tasks and the like

[William G. <ww...@ts...>]

Hello, Peter --

> Yes, the cross-db stuff, xml, metadata and the like are probably a lot for
> the first release.

Well, the expansion of the metadata querying (task 3) should be easy; I've
already been thinking on that, and will add it in shortly.  Jukka already
has the code for switchable multiple db connections.  What other "major"
function or functions do you think we should target for initial release?

> I would like to see code generation as well, and possibly options like
pool
> managers ... etc., but certainly for v.2

Once we define what's in this release, let's rough out a release list for
the next couple of versions.

> I tried out the gui code in the CVS project, but only got the connect
panel.
>   The code looks like it has a JTree and the like, but could not get it up
> and running ... have you ?

Not recently: I know that it does require a class from the borland jar file
that's also in cvs.  Did you get that & put it in the classpath?  I can try
to get it running myself soon, too.  Also, I can get the "author", my friend
Stefan, to give us a hand   ;-)

> Task distribution - how would this be done ?

Not totally sure.  I'd like to see if anyone has any areas they prefer to
work on.  One area I want to keep working on is the basic console version,
since that's what I originally wrote, and what I use day-to-day at my work.
I'm hoping that others will just make their preferences / interests known,
and we can go from there.

> I have 5+ databases at my office to work with, on Linux and NT (Oracle,
> SQL-Server, MySQL, Interbase (Inprise), JDataStore, MSAccess as well as
> other xBase type databases.  I can do some development on these as well as
> testing.

Cool.  I have Oracle and Mysql on Linux, and InstantDB on Linux and Windows.
Sounds like we have a good range if things -- you just about have it all!
Anyone else have any other dbms or platforms available for test?

> Should there be anything as elaborate as class diagrams, modeling and the
> like being done here?  I have all the tools necessary and would offer my
> services as documenter if others want to do upfront design or want to
lead.
> I can do the design of these things as well, but wonder if this is
overkill
> (at least a few high-level diagrams would be good I think).

A class diagram, basic design, and perhaps a message flow diagram, will be
very nice as we separate into a MVC architecture (assuming that's the
approach we use to separate view from core code: other architecture
suggestions, anyone?), and as we add the sort of things you and Jukka are
talking about.  I don't want us to go too "design-crazy", but don't want to
make the opposite mistake either.  Let's see if anyone else has any comments
about design, then we'll add some basic design tasks into the release tasks.

One thing I do want to do is get us to agree on some coding conventions.
I'd also like to go back and comment the code, and then require javadoc at
the beginning of each class and method.  This will make maintenance and
expansion much easier in the future ...

Thanks again for the input!  Anyone else have comments / ideas /
objections??

Regards,
Bill Graham