-
Do I ask for too much?
For my latest beta version of ReceiptWallet, I've specifically disabled the auto update mechanism by putting in a bogus link in the Sparkle feed for the actual update. Instead, in the text of the dialog, I tell people that clicking the Install Update button will fail, to read the text, and then have the real link in the text. I've done this on purpose as the new beta has some major changes and I really, really want people to back up their data before installing. If they can't install the update, then their data can't get hosed. This seems to be working. So far I've had 3 reports that people couldn't install the update. This means that they didn't read the text and just hit "Install Update". Furthermore, whatever text I put in the dialog, no matter how large, it won't be read. I even made the text real large as shown below. Even in the smallest window size, I think the large text would get people's attention and then maybe they'd scroll down.
-
ReceiptWallet 1.6.0 b2 Ready to Go
I'm extremely pleased to say that ReceiptWallet 1.6.0 b2 (and DocumentWallet 1.2.0 b2) are now ready for testing (b1 had 2 bugs in it). This version brings a huge change to the product in that you now can have more than 1 library. For users that don't want more than 1 library, there will be few changes.
-
UI Feedback needed
I've spent a significant amount of time working on the new version of ReceiptWallet. One of the changes is that information about a Library is now in a floating panel. However, I'm not happy with the buttons/look of the panel. I'm looking for ideas that people may have. Please feel free to post comments on send me email with ideas. Thanks!
-
Love/hate relationship with Cocoa Bindings
I have a love/hate relationship with Cocoa Bindings. On the surface, bindings look really cool. Write less code and get a program running faster. This is great in theory, but in reality, it can be tricky. Bindings in Interface Builder work OK (however, there seems to be annoying Interface Builder bugs that change the focus when you try to bind an object). The problem arises when you remove an object from a nib, run the app and find out that your get an exception that the object is not key/value compliant. So, you have to search through the nib looking for the bindings that are no longer relevant. If you have a lot of objects, this can be time consuming and problematic.