Can’t believe how time flies! Another spring is in full blossom, so there’s plenty of activity outside, from work in the garden to relaxing walks. But we are still coding - in fact, last month we were quite busy working on first Startupizer’s upgrade!
Every software has a story behind it and so does Startupizer. In this post, we’ll write about the store behind the Startupizer - from the idea to launching in the Mac App Store!
Those of you who follow us on twitter already know, but for the rest: Startupizer has finally been approved by Apple and is now available on the Mac App Store at a special introductory price! Go grab it until the price goes up!
Handling support and feedback is probably one of the most important things software developer teams face after releasing a product. The simplest way many of us use at the start is e-mail, but that soon becomes too difficult to manage. There are several online solutions available - FogBugz, Lighthouse or it’s “bigger” sister Tender are just few of those most often mentioned by developers.
We’re proud to announce we’ve released appledoc 2.0! It took several months of efforts, but the result is stable and easily extendable platform - what we envisioned for appledoc to be in the first place!
There are many applications we find invaluable and rely on them for our daily usage. In this post, we’ll write about some of them. Note that our selection of apps reflects our personal needs and tastes and this post is primarily intended to give tribute to these tools and perhaps show various options to our readers. We’re sure many of you have your own personal favorites and many of those would be different from ours. Keep this in mind when reading the article. This post will only cover generic utility apps, we won’t write about apps we use for developing - perhaps we’ll cover them in a future post…
The year is almost over. Looking back it’s been eventful for me personally as well as for Gentle Bytes.
Those of you who follow me on Twitter already know that I was using MGTemplateEngine for generating appledoc html files. I tweaked it a bit to make it work for me – the main point was to add ability of function-like sections that can be called with arbitrary parameters.
Some weeks ago my late 2007 MacBook Pro 15” started having issues during boot – it presented gray Apple logo with a bar graph underneath which went somewhere near 1/4th the way two times and then the computer would just turn off without any warning. I immediately checked various forums and tried all suggestions, but nothing worked. Luckily I had my Tech Tool Pro 5 DVD ready so I booted with it and performed all bunch of tests, even waited an hour for HD bad sectors search, however no problem whatsoever was reported. I also performed volume rebuild, restarted and voila – OS X booted (still preceded with gray bar graph though). Once there, I ran Disk Utility to repair permissions and it didn’t report any problem.
In this post, I’ll add links to documentation generated with appledoc 2.0 in time. The post will be updated accordingly.
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...
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.