From: Bill Kendrick <nbs@so...> - 2005-03-31 09:27:18
John and others, can you comment on any of this?
> In a Unix environment things are so much simpler, but currently the
> school uses Windows XP pro. I am able to get everything to work with
> some extra work and if I could talk them into producing a new image I
> would only have to tweak the image machine, but unfortunately that's low
> on their priority list right now, so I have to install and tweak it on
> every individual machine. Here are the things I wish the installer did:
> 1. It looks as if the installer was written for non pro versions of
> windows since it installs the program menu for the current user and not
> for all users. Many installers check for this and either install in the
> all user area on pro machines or have a check box to install for all users.
> 2. Because we severely limit the student accounts it would be nice if
> the userdata directory was open to all users. chmod 777 would take care
> of it, but I don't know what is available from the installer.
> 3. It would be nice to be able to control more of the default options
> from the installer. It's not a big deal to run the configure program or
> edit the config file after the install, but it would be more convenient
> to set these during the installation. Specifically we would like to
> disable printing.
> If I can help with any of this let me know. I have done some programming
> over the year, but most of it has been on Unix machines.
My comment on #2 was to try out the 'savedir' Python launcher I was
working on ( ftp://ftp.billsgames.com/unix/x/tuxpaint/savedir ) to see
if that could help.
For #3, I asked if it would be sufficient to, at the end of the
installation process, ask if the user wants to run Tux Paint Config next...
I have no idea about #1, since I've only ever used WinXP Professional.
(Well, that and Win95, which was one of my key reasons for switching to
Linux ;^) )
Get latest updates about Open Source Projects, Conferences and News.