Enrique Rodriguez wrote:
This brings up a good point. Why should this directory be hidden and
in the user's home directory? Many Java applications create a
directory at startup for a database and they often create this
directory *inside* the directory the application is run out of. I
change this location, too, to create the directory inside the oscar
directory. I find this slightly easier for backing-up or moving oscar.
Oscar 1.0 is the only Java app I can think of that does this into the
user's home directory and hidden. Most Linux and Java clients do this
for config, but it's rare for servers.
I actually find it nicer to have it separate, because if I have multiple
versions of Oscar that I am messing with, they can all access the same
profiles. I am definitely in favor of a global profile directory,
whether or not it is hidden is something that I could go either way, but
I prefer hidden because I generally don't want to see it.
I am thinking of the typical user experience in this case, not someone
that is using it for a heavy-duty server project. The typical user
downloads and installs Oscar and wants to install some bundles. If they
later upgrade, by deleting the old install and installing the new
version, they probably would like to have their profiles still there. Or
if they have multiple versions to do testing before upgrading, etc.
For people that are setting up a real serious use case, they have simple
properties to configure Oscar to put the profile directory whereever
they want.
I think this makes the most sense for the typical "ease of use" case.
-> richard
