Feature Request for AppTrap

21 views
Skip to first unread message

CodinJones

unread,
Nov 2, 2009, 1:33:51 PM11/2/09
to AppTrap
I just updated to AppTrap Version 1.1.3, and it was as simple as the
original install.

One feature I would like to see, would be to have AppTrap 'remember'
Applications that I do not want their associated files deleted.
The situation I run into is when an application such as Evernote gets
updated AppTrap asks if I would like to move the associated files to
the trash.
My answer is always no, but only for that app, so I would imagine
there could be choices like: Always Keep, Always Ask, Always Delete.

Then AppTrap could remember so next time Evernote is updated it does
not even ask me.

Thanks for all the great work!

ae3265

unread,
Nov 9, 2009, 4:27:04 AM11/9/09
to AppTrap
+1 on that!

Groxx

unread,
Nov 15, 2009, 6:08:09 PM11/15/09
to AppTrap
Overall, I'd agree too. There's an intrinsically hard problem where
Sparkle's updater is used... but for frequently updated apps (nightly
builds of WebKit, in my case), it'd be handy.

Perhaps a more complete option would be:
1) remember by name
2) remember by identical file (check filesize first, MD5 second if
less than, say, 100mb)

mrpi...@googlemail.com

unread,
Nov 25, 2009, 11:01:21 AM11/25/09
to AppTrap
would be nice to see more cleaning - lots of programs leave behind
more than just preferences (does app trap clean cache? not sure... ),
For instance, if you show hidden files almost all the key directories
have many many more files than you normally see - visual paradigm and
svn clients are particularly bad instances of this. (although I'm sure
there's some other much worse ones!)

However I can see this being a huge job, since it might require
constantly monitoring a program, just to be able to remove things,
which isn't what many people will want to see from what is such a nice
hidden program. also i guess finding a way to find all these 'loose'
files would be a monster of a task!

Groxx

unread,
Nov 26, 2009, 2:18:13 PM11/26/09
to AppTrap
I've debated building a system that does that, myself, but I'll
definitely vote "no" for AppTrap. It's too much of a break from the
original purpose, would eat up a lot more processing power, and it's
intrinsically pretty hard to do and be complete and not too greedy (to
not delete everything Adobe related because you deleted the PDF
reader, because it's all legitimately related to their reader).
AppTrap as it is works fairly well, and it's pretty minimal. This
would be way off in the other direction (not that that's a bad thing).

Maybe put in a forked / unrelated project? I've wanted something like
this, personally, and an easy place to start is to look at the
receipts installers (should) leave on your system. `lsbom` lets you
see all the files the installer creates or touches. Just beware that
that can include files that were on your system before the app was
installed, too.
Reply all
Reply to author
Forward
0 new messages