sereko / theunarchiver

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

Implement prefpane? #163

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
The Unarchiver might possibly be more intuitive to use if it was implemented as 
a prefpane instead 
of as a standalone app. I am not entirely sure if this is the right way to go, 
though.

Original issue reported on code.google.com by paracel...@gmail.com on 3 Jul 2009 at 3:30

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I'd have to disagree with marcantoineboucher. The idea of a prefpane sounds 
nice to me - considering the 
application itself only launches a preference window when run. Seems to be a 
bit more appropriate place for 
such a thing, though it would change the installation from "drag to a folder" 
to "double click the .prefPane file". I 
don't imagine that would change the complexity of installation or use much.

Original comment by broken0chaos@gmail.com on 6 Jul 2009 at 7:39

GoogleCodeExporter commented 9 years ago
I also support moving it to a prefpane. I have my applications folder as a 
stack on my dock, so it would be nice 
to make it a bit smaller by moving an application that is never run directly by 
its icon.

Original comment by jarvik7 on 7 Jul 2009 at 3:17

GoogleCodeExporter commented 9 years ago
If it doesn't become a prefpane, I imagine you could fix that minor annoyance 
by dropping it into the Utilities 
folder, right? (That's where I've put it... I don't *think* there's a reason to 
not put it there - I haven't had any 
problems anyway. ;)

Original comment by broken0chaos@gmail.com on 7 Jul 2009 at 2:43

GoogleCodeExporter commented 9 years ago
Even Apple has removed the QuickTime preference pane in Snow Leopard. Since the 
Unarchiver is not a plugin, 
nor a MacFUSE FS, but a helper application, it makes no sense to implement it 
as a pref pane. It might make 
sense to package it as a disk image with a symlink to the Utilities folder to 
ease installation.

Original comment by yuan...@gmail.com on 15 Jul 2009 at 4:27

GoogleCodeExporter commented 9 years ago

Original comment by paracel...@gmail.com on 20 Jul 2009 at 4:25

GoogleCodeExporter commented 9 years ago
yuan0qi, Hazel, TextExpander, Growl, Automatic, Perian and other applications 
that mostly interact with the 
happenings of your system are all prefpane. This is a system wide replacement 
for most. The reason there is no 
prefpane for Apple's unzipper is because it's built into the system. The 
Unarchiver needs to be a prefpane app. 

Original comment by csuro...@gmail.com on 15 Sep 2009 at 10:49

GoogleCodeExporter commented 9 years ago
I agree with @yuan0qi. Very few applications /need/ to be a pref pane. The ones 
you mention are totally 
different from The Unarchiver and Apple's archive helper. In all those cases, 
the pref pane is about managing 
behavior of the application itself. I actually think a pref pane is much less 
intuitive than a standalone app. When 
set as the default app for various archive types, the app need not even be in 
/Applications — I put it in 
/Applications/Utilities, like broken0chaos. (The argument that BOMArchiveHelper 
is not a pref pane "because it's 
built into the system" is untenable — all of the default pref panes are 
"built in" as well.)

Original comment by quinntay...@mac.com on 24 Sep 2009 at 4:02

GoogleCodeExporter commented 9 years ago

Original comment by paracel...@gmail.com on 16 Sep 2012 at 7:18