warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Not using AppData directory #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Run the tool

What is the expected output? What do you see instead?

"Well behaved" apps should not be writing data to their install-directory;
they should be writing into their own subdirectory within the Application
Data folder instead.  History.db, cache.db, saved block/allow lists, these
should all be located either under the system AppData or else the per-user
AppData (probably the former).

Original issue reported on code.google.com by peerbloc...@gmail.com on 23 Jun 2009 at 2:43

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 10 Jul 2009 at 1:27

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 13 Jul 2009 at 3:55

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 24 Jul 2009 at 5:43

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 24 Jul 2009 at 5:45

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 30 Jul 2009 at 6:18

GoogleCodeExporter commented 9 years ago
if you implement this functionality, please make it optional like foobar or
notepad++. i run peerblock on an embedded system from a network share with very
limited space on the c drive

Original comment by per...@gmail.com on 7 Aug 2009 at 7:47

GoogleCodeExporter commented 9 years ago
What I will probably do is include a command-line argument to run PeerBlock in
"portable mode".  Especially since at some point (post-1.0) I'd like to it into 
a
Windows Service so that we no longer need to worry about the requirements to 
run as
admin, among other benefits. 

Original comment by peerbloc...@gmail.com on 7 Aug 2009 at 9:55

GoogleCodeExporter commented 9 years ago
Don't think I'd hold up PeerBlock 1.0 for this one, so am downgrading its 
priority.

Original comment by peerbloc...@gmail.com on 17 Aug 2009 at 4:22

GoogleCodeExporter commented 9 years ago
PG3 already does this so we could port the code over. It probably break a lot 
of things 
in PB though.

Original comment by nightstalkerz on 19 Aug 2009 at 8:22

GoogleCodeExporter commented 9 years ago
Not going to get to this one by Release 1.0.

Original comment by peerbloc...@gmail.com on 12 Sep 2009 at 3:24

GoogleCodeExporter commented 9 years ago
Removing 'After1.0' release-targetting.

Original comment by peerbloc...@gmail.com on 29 Sep 2009 at 3:58

GoogleCodeExporter commented 9 years ago
Oh, please don't.
If there's one thing I hate about programmer's it's this ill-behaved mentality 
of
scattering their files all over my hard-drive without even asking me.

I own several games that bomb my system drive with savegames above 1GB...
This surely does not fit into "well-behaved".

I like it just as it is: I have specified one certain folder within my order 
upon
installation and everything is there. I wouldn't want to search all over the 
place to
find hidden config files, caches and logs..

Original comment by frederic...@gmail.com on 30 Sep 2009 at 7:16

GoogleCodeExporter commented 9 years ago
Another well-known example for that is any software by Adobe or my "special 
friend"
Spore, which creates a 4GB temp file right on my system drive without neither 
asking
nor giving me the option to move it.

Original comment by frederic...@gmail.com on 30 Sep 2009 at 7:17

GoogleCodeExporter commented 9 years ago
The issue here is that this is another thing which could force a UAC prompt in 
order
to run PeerBlock.  And once we've transitioned to a service, the base UI 
shouldn't
require any additional propmpts.  Windows expects apps to behave in a certain 
manner,
which includes using e.g. the %appdata% directory for program settings.  See 
this
link for some additional discussion:
(http://stackoverflow.com/questions/269893/best-place-to-store-config-files-and-
log-files-on-windows-for-my-program/269929#269929).

What I will do, though, is make it possible to override the setting via the 
Settings
panel.  And if you change this, make sure PeerBlock "cleans up after itself" and
moves all files from the default %appdata% directory (or wherever) into whatever
directory you specify.  I too prefer to have control over where apps place 
things on
my disk, but do think that following the Windows standards by default is a good 
idea.

Original comment by peerbloc...@gmail.com on 30 Sep 2009 at 9:09