Re: [Wpigdc-cms-development] Installation documentation available.

[Dan P. <dp...@WP...>]

Replies below.

On Mon, 6 Aug 2001, Liam Morley wrote:

> I was able to get ant to work without too much problem, but I think we
> need to include batch/shell scripts in CVS to make it easier on those who
> don't know what ant is (which, as far as I know, is most if not all people
> in the webdev team other than you and I).

This usually is added later in the dev cycle and as part of ZIP and
tarball distributions - it wouldn't hurt to write it out now, except that
it would require us to include ant.  This is probably something that best
waits until we write up a source distribution.

> We should also add the mysql.jar file in CVS as well I think, or at least
> give a link to where it can be found. People without JDBC experience will
> get 'invalid driver' exceptions without knowing what to do.

You don't add binaries into CVS - more on this later though.

> Also, I noticed the SQL script- that's great. I created a DB on my home PC
> (as well as work PC) and was able to get everything to run nicely using
> the RemoteConfig class. What I didn't see in CVS or the SF site is the
> XML code; I was wondering if I'm looking in the wrong places, or are you
> waiting to post that?

I started creating "default" XML pages on Saturday, and will probably be
posting them to CVS ... sometime this week.  Along with these are the
default XSL pages and CSS - it isn't very "pretty," but the idea is to
make people customize the system :)

> As far as RemoteConfig goes.. looks good so far. Maybe we can use this for
> officers to add things to the database as well (taking their
> usernames/passwords out of the conf file, we'll know what db rights to
> grant them). Or we go with the web-interface idea.. but both are a
> thought.

Eventually, the RemoteConfig program will be capable of initializing the
database - the actual code for setting up the tables is supposed to be the
DBEngine's responsibility, which is why the script isn't part of the CVS
repository.  (Actually, the idea is that the system will initialize the
database the first time it's started.)

The bottom line is that the database should be "engine independent" and
that each DBEngine has the freedom of creating the database however it
likes.

The RemoteConfig program currently isn't capable of posting stuff, it's
main use right now is testing the DBEngine :)

(Likewise, the overuse of System.out in the classes are more for testing
the way it works and will probably be removed permantently by the first
beta.)