In the past days I’ve had an interesting e-mail interaction with a appledoc 1.0 user who had trouble with extracting documentation for methods of the first named section. Whichever section he would put first, it’s methods were not extracted. It’s a strange bug I’ve never experienced before. He even sent me an example header file and it looked correct.

Not much activity online in the past month. This post talks about what was going on.

As I get more and more reports for issues related to appledoc, and I tend to reply with similar message each time, I decided to write a post about support and news :)

So you’d like to see what has been going on in our labs? We’re now opening Startupizer for beta testers. We’ve already described what the app will do here, so go ahead and read it and if interested, let us know through our contact form on the contact page.

I’ve checked several in-app user feedback frameworks, but found Tyler Hall’s OpenFeedback most usable - the code is very readable and consistent and it’s visually appealing as well. However I’ve been missing crash reporting option, so I’ve decided to roll my own.

We’re slowly approaching first beta of our first shareware product - Startupizer. It’s advanced login items handler for OSX. Besides handling login items startup, you’re used to, it allows you to change the order of items, enable or disable individual items and what’s even more important specify optional items startup based on time, modifier keys etc. All this allows you to drastically reduce system startup times while still enjoying automated startup of all items you need at specific time!

Recently I’ve come across Justin Williams and Martin Pilkingtons posts describing their solutions about working with Core Data in single-window multiple-view applications.

In this post I’m talking about appledoc and directions I’m taking it in the future based on feedbacks and suggestions from users.