I introduced a really stupid bug with 1.1.2 where System Preferences would show a blank window if you were using either the French or Dutch localizations. That’s been fixed with 1.1.3. The bug was introduced due to negligence on my part.
I’m really sorry about this. I’m still working out the kinks in my bug-testing.
I just released AppTrap 1.1.2. The biggest addition would have to be the French localization, contributed by Ronald Leroux (Thanks!). The background process is also 32/64 bit and now uses Garbage Collection.
For the next version, 1.2, I’d like to get in a better updating mechanism, where the background process checks for updates as opposed to the preference pane, and I’d also like to build an uninstaller for AppTrap. An AppleScript seems like the best way to go about achieving that last change, but I’ll have to learn that language.
I’d also like to mention that my classes will be starting on Thursday. That will restrict the amount of time that I’m able to devote to AppTrap. I won’t be able to work on the code as much as I’d like and I won’t necessarily be able to respond to emails in a timely manner. I’ll start a Google Group, that way everybody can post their suggestions and issues and help each other out.
AppTrap for Snow Leopard is pretty much done. I just need to get my hands on a copy of the OS to do some final testing. If there aren’t any crazy last-minute bugs, it should be released sometime between Friday and early next week, depending on when I get my copy. The current version should work fine on Snow Leopard, so you’ll be OK while I get the next release ready.
The main improvement for the Snow Leopard version of AppTrap, henceforth known as 1.1.1, is 64 bit support. Specifically, 64 bit prefpane support. The change isn’t for the imperceptibly small performance improvement, but for convenience’s sake. Snow Leopard’s System Preferences supports the loading of 32 bit preference panes, but, being a 64 bit application itself, it must restart in order to load them.
It’s akin to a 64 bit application requiring 64 bit plugins. If one of the plugins is 32 bit, then the application will run as a 32 bit process instead of as a 64 bit process. In the case of System Preferences, because it’s already running, it has to quit itself and then restart as a 32 bit process.
1.1.1 will also be dropping support for Tiger. That’s mostly because of the 64 bit-ness. Some of the code I’ve had to change to get AppTrap to compile as 64 bit also requires Leopard.
I’ve tried compiling the background process as 64 bit, and although it compiles, the warnings freak me out just a little. I’d like to learn a bit more before I start to delve into stuff that I’m not as familiar with.
Anyway, this post was longer than I expected it to be. I hope it gave you some clarification on what’s going on with AppTrap. Post in the comments if you have any questions or suggestions, or you can email me.
I am continuing the development of AppTrap, an open source uninstaller for Mac OS X. It runs in the background, so that when an application is put in the trash, AppTrap knows and asks the user if they also want to throw away the associated preference files.
AppTrap is simple from an implementation standpoint, which is important for me, considering that this is my first real application (a finished product that is meant for public release).
The code is available here. I’d be grateful for any tips*. It’s not that I don’t have any confidence, but that I’m in unexplored territory here. Oh, and the kqueue stuff? Right over my head. I’ll have to learn how to work with them as time goes on.
Anyway, this is all new to me. I’m sure I’ll make mistakes, but I’ll try my best to keep them from happening. And when they do happen, I’ll try my best to keep the users unaffected.
I’ll be starting class soon, so that will put a damper on development, but I’m committed to making AppTrap the best uninstaller for Mac OS X. Even though an uninstaller really isn’t all that necessary.
*Specifically, help on how to make a 64 bit prefpane would be awesome. I’ve been running into my usual set of bizarre problems in that area.
Overall I’m very pleased with Safari 4’s updated UI. The public beta’s tabs-on-top implementation is gone, where the tabs were in the titlebar. An interesting experiment, but one that ultimately proved that such a feature is really quite irritating. I would have liked to see it go the Chrome way, where the tab bar is between the titlebar and the toolbar, but this is fine.
Somet other things:
- I love the new tab button. It’s clicked vs unclicked state is very pleasing.
- The tabs still have that stacked feel to them.
- The Top Sites feature where you’re able to drag another website into your Top Sites while pinning it at the same time was broken in the public beta. It is now fixed. Finally.
- That reload button is still in the URL field. How annoying.
- I’m not entirely sure if this was possible with the public beta, but the Add Bookmark button that is attached to the URL field is only default behaviour. If you add the standalone Add Bookmark button to the toolbar from the Customize Toolbar sheet, the attached Add Bookmark button will be replaced with the standalone one. Then simply remove the standalone button. Yes, this is a very awkward workaround to just having an Add Bookmark-less URL field in the Customize Toolbar sheet.
- Yay, the hierarchical site structure contextual menu is back!
- A tab only shows its close button until you mouse over the tab. And they also have click-through. Blegh.
Both of these ads are the newest examples of Microsoft’s “I’m a PC” campaign. Setting aside some of the controversies, I’ve been wondering about a couple of things pertaining to these kinds of ads.
First, why is Microsoft making these ads? (not a rhetorical question) They hardly, if ever, mention Microsoft products and instead highlight things like price and hardware specifications. Isn’t it the responsibility of the computer manufacturer to do this? Shouldn’t Dell, HP and Acer be the ones making these commercials? The only answer I can come up with is that Microsoft is unsatisfied with the marketing response to Apple’s Ads.
Second, will this change anything? (kind of rhetorical, but do tell me what you think) Do these ads influence consumer’s perceptions of PCs? Wasn’t it already a well-known fact that you could buy almost any kind of PC at almost any price point?
I’m betting that those who are buying Macs are not going to be moved by this at all; For them, it isn’t a question of price but of design quality. Those who buy computers based on price are not going to be moved by this at all; They were always going to buy a Windows PC and were never considering a Mac in the first place. And those who are considering a Mac are not going to be moved by this at all; The fact that they are considering a Mac means that they’re not buying computers based on price anyway.
Very non-standard Mac OS X UI. Not a bad decision, but it makes me wonder what Snow Leopard will look like.
Although I’m not so sure about that reload button in the URL field. That makes sense on the iPhone, since it has a limited amount of screen real estate, but not so much on a desktop browser.
And there’s no progress bar, just like that other browser.