A small demonstration of a dashboard clock replacement project for the DeLorean car. All settings can be changed using a single rotary encoder (that will replace the rheostat on my car).
Recently, Apple approved the latest update of SimplyStats, a free app for browsing Google Analytics data (bet you knew that). With this minor update, the app should be compatible with the upcoming iOS7 release.
I regret to say that it doesn't yet support the new white look and feel of iOS7.SimplyStats has quite a few subtle customisations and i don't have the hardware to fully test every edge case. I will tackle that later on, i promise! But at least your numbers and graphs should be ok.
Thanks for using my app!
I just pushed SimplyStats 1.4 towards Apple. This tiny update contains a little fix so the overview report should no longer crash on iOS7. I hope the fix is approved before everybody switches to the new OS. Also, i added an export function for table reports.
Both issues were reported by a few users. If you have an issue or questions about SimplyStats, please tell me.
I was working on a patch for appledoc, when i stumbled across a very annoying bug: The icon of the navigation tree in Xcode does not match with the type of the document. Whatever I tried, they just showed up as folders. I couldn't found anything in the official documentation, and even a good google session didn't help. There were no more excuses. Time to investigate!
First, I should give you a little background information. Apple Doc Sets are what Microsoft calls compiled help files (.chm), but in a different format. I've spent some time with .chm files back in the days and boy are they touch. Apple's format is actually much much simpler than that, once the veil of magic is lifted. In this article, i will try to explain everything there is to know (and perhaps a little more).
Welcome to part 2. In part 1 I talked about what AppleDoc is, what it does, and how to install it in your build setup. But to actually use it is a different subject. Not a lot of documentation on how to actually use appledoc is available.
The lack of documentation is partly there because new work on AppleDoc is going on behind the scenes, and the author decided to remove the little documentation to avoid mistakes and misinformation. I found out a lot of syntax stuff on my own (partly by browsing the apple doc source code). I'd like to share my findings here, and hope that someday the official documentation gets published again. I will be happy to help writing them when the time comes.
Let us skip the history lesson and rejoice that appledoc is free and open source. Then read on to find out how to document your classes, methods, categories and enums.
While developing SimplyStats I had to learn a lot of new stuff, and having integrated help certainly helps in those situations. Apple's Xcode comes with a good set of documentation for all its classes, and can be accessed right from your code. To look up a keyword, just opt-click and you'll get all the information you need (now if somebody integrates StackOverflow.com queries in the IDE he'd be my hero).
Wouldn't it be cool if that was possible for your own static libraries? Well you can! In these days and ages of open source and community development it's not a strange thing that others will use your excellent coding efforts, so providing a descent help set will certainly be appreciated.
The help system for Xcode is called a 'documentation set' (or docset for short). Constructing a docset manually is a hell of a job. Nobody wants to construct XML files and references by hand. Fortunately there are quite a few (free!) tools that can extract comments from your code and translate them into neat docsets. There's appledoc, doxygen and headerdoc just to name a few. I decided to go for appledoc for its simplicity.
In this tutorial i will explain the steps necessary to get your code documentation up and running. This is part 1 about installing appledoc and configuration a build target. In part 2 i will explain more about the options and documentation syntax.
On June 11 of 2013, my first app was released to the world. In the first week, i had an average of 10 visitors per day with about 15 screen views total. Clearly users were checking out the app but didn't make any significant use of it.
Now were are a little over a month further, you are clearly liking SimplyStats! Check out this graph today we topped 880 screen views and 170 visits daily!
SimplyStats 1.2 screenshot
Already the 3rd release! This is just a little update, with some graphical tweaks and cleanups, like icons and a more consistent look and feel. Oh, and it now comes with a daily overview so you can monitor how your day is doing.
Get your updates from the App store or check the SimplyStats page to get you directly there.
Tips, suggestions? Use the comments below or use the contact page!
While browsing through programmers questions on stackexchange i stumbled on this question about maintenance, and if it is acceptable to allow ugly code for performance reasons. This was one of the responses:
In layman's words:
Ask yourself if these statements apply to you and your product, and i hope you soon realize there is little excuse for ugly solutions.
What do you think?
When doing retina ready apps (is there any other way?), you need crisp graphics. I tried several alternatives until i found the excellent Mopishape Draw app for Mac.
Mopishape allows you to draw perfectly grid-aligned curves and export them to several formats. And with the latest 1.30 update it even can automatically export your @2x files for you. It's not expensive either.
It takes a little getting used to, and it doesn't have all the features that for example Sketch has, but it suits my needs. I am not a graphics designer you know!