[Cronometer-development] Final application directory structure

[Chris R. <of...@gm...>]

With all of the runtime dependencies we're using here, we've got to
have some way of making this app run as painlessly as possible for the
end-user.

Right now, I've got user setup bits put in, although not assembled
into a usable, simple whole yet.  Possibly over this week.

However, the eventual installation is going to be a bit rougher.

We need, as I see it, two things:  One, we need to aggregate all of
our dependencies into ${CRON_HOME}/lib and two, we need to have some
kind of automatically-generated launcher for these things.  All of
this then needs to go in a tgz, a zip, and an installer.  An rpm would
be nice, too, if possible.  Plus whatever macs use (dmg?), which is
probably a higher priority than rpm, come to think of it :)

How close are we, in general?  At this point it looks to me like we
don't have any dependencies on the command line tool for database
loading, and I've removed the requirement to pre-initialize the
database schema, so I think the setup issues and the user model are
it, for now.  Some UI hackery would be good, too, but I think that if
we buckle down a bit over the week (time permitting) or two coming up,
we can probably see something we can ship Real Soon Now.

--=20
Chris R.
=3D=3D=3D=3D=3D=3D
Not to be taken literally, internally, or seriously.