RE: [DQSD-Users] DQSD installer/uninstaller (WAS: ANN: DQSD 3.1.8 goes final!)

2004-01-21 Thread Kim Gräsman 
Ed  Monty,

 IMHO config files actually belong under \documents and 
 settings\username\... so that you can have multiple configs 
 for multiple users.

That's true... They really _should_ be in there, not just for user affinity,
but also to comply with security guidelines.
DQSD won't run, for example, on a locked down NT/2000/XP workstation, where
write access has been denied to Program Files.

I'm personally not very fond of \Documents and Settings\...\ because it's so
hard to navigate to, and find app settings in, but it's really the only
correct way to go.

I think we'll toss around some ideas at the Devel list, and see what we come
up with on this matter.

Thanks for bringing it up,
Kim



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
To unsubscribe visit:
https://lists.sourceforge.net/lists/listinfo/dqsd-users
[EMAIL PROTECTED]
http://sourceforge.net/mailarchive/forum.php?forum_id†01

Re: [DQSD-Users] DQSD installer/uninstaller (WAS: ANN: DQSD 3.1.8 goes final!)

2004-01-20 Thread Ed Greenberg 
IMHO config files actually belong under \documents and 
settings\username\... so that you can have multiple configs for multiple 
users.

/edg

--On Tuesday, January 20, 2004 3:35 PM -0600 Monty Scroggins 
[EMAIL PROTECTED] wrote:

This seems to pretty much be the behavior of most applications I have ever
dealt with...  If there is any user data stored with the application, the
directory and the user data is purposely left behind.   Its too risky to
wipe out everything...   Most applications dont do anything about the data
left behind, and a few I have seen display a quick note to the user that
they will manually have to delete the directory themselves...Of course
another way to handle it is to move user data to another location like My
Documents etc, and wipe the application directory clean on uninstall,
but I personally dont like the idea...
Its no big deal IMO...

FWIW

Monty

- Original Message -
From: Kim Gräsman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 2:41 PM
Subject: [DQSD-Users] DQSD installer/uninstaller (WAS: ANN: DQSD 3.1.8
goes final!)

Monty  all,

It turns out I was wrong; the uninstaller _does_ remove everything
(including local* files) after a reboot.
I've fixed it up so the following policy is:
- On install, create localsearch.css, localprefs.js, localaliases.txt and
mrumenu.txt, unless they already exist
- On install, create localsearches directory, unless it already exists
- On uninstall, remove everything but localsearches directory,
localsearch.css, localprefs.js, localaliases.txt, history.txt and
mrumenu.txt
This effectively means that the uninstaller never removes the install
dir, since it will never be empty (local*.* will always be trailing).
Are people OK with this solution? I think it works OK, and I'd much
rather have it this way, than losing my local settings, but I can
imagine some people wanting to get rid of it, without trailing files.
Maybe we should have an uninstall option to either fully remove DQSD, or
leave local*. Anyone know how to do that in NSIS?
Kim

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Kim Gräsman
 Sent: den 20 januari 2004 20:39
 To: [EMAIL PROTECTED]
 Subject: RE: [DQSD-Users] ANN: DQSD 3.1.8 goes final!

 Monty,

 It seems you're right, it already does all of this, except the
 localsearches.
 I'll see if I can fix that today...

 Thanks,
 Kim

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
  Monty Scroggins
  Sent: den 19 januari 2004 21:01
  To: Dqsd-Users
  Subject: Re: [DQSD-Users] ANN: DQSD 3.1.8 goes final!
 
  The installer might already have this behavior, but I dont
  know offhand...
  Its been a while since any of this was discussed on the group..
 
  IMO the installer should:
 
  Not over-write any local* file if one already exists..  I
  think the bundle
  comes with a couple of empty local* files  localsearch.css
  and localprefs.js
  ?
 
  Create the localsearches directory if it doesnt exist.
 
 
  The uninstaller should:
 
  Not delete any local* files at all..
 
  Not delete the mrmenu.txt and history.txt files..
 
  Again, I think this is largely the behavior anyway...
 
  FWIW
 
  Monty


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
To unsubscribe visit:
https://lists.sourceforge.net/lists/listinfo/dqsd-users
[EMAIL PROTECTED]
http://sourceforge.net/mailarchive/forum.php?forum_id?01


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
To unsubscribe visit:
https://lists.sourceforge.net/lists/listinfo/dqsd-users
[EMAIL PROTECTED]
http://sourceforge.net/mailarchive/forum.php?forum_id?01






---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
To unsubscribe visit:
https://lists.sourceforge.net/lists/listinfo/dqsd-users
[EMAIL PROTECTED]
http://sourceforge.net/mailarchive/forum.php?forum_id†01