On the Sunday before WWDC 2013 was spent in good company, on a road trip to Cupertino. But before we took that, we got ourselves registered. Apple successfully pioneered a new system to streamline the registration process.
This year’s Pilgrimage to the Apple Headquarters at 1 Infinite Loop in Cupertino is of the DIY variety. In past years Apple would have updated the Company Store website with information about extra opening times for WWDC tourists, but this year they didn’t.
Traditionally there were several busses organized by Scott Knaster. I don’t know if his reason for not doing it this year was lack of a WWDC ticket or lack of confirmed opening times. Either way his professionally organized tour did not come to pass this year.
Last update before WWDC. This is a maintenance release fixing some pressing issues, some of which were causing crashing.
An editor has to deal with the user hitting the tab key on an external keyboard and then be able to persist these tabs. Thus the question arose how I would best represent tab characters (\t) in HTML. At first I tried to encode them as entities, but that is causing lots of trouble since on the parsing end it is difficult to know whether a tab came from this entity or if it came from the literal \t.
I could have done that with a very ugly hack of libxml2 (which powers my DTHTMLParser), but after having wasted half a day on this I relented. I previously reported my findings about Apple-converted-space which is the method NSHTMLWriter uses to preserve multiple spaces.
In this article I am documenting my findings related to how Apple conserves tabs for HTML output.
7 days (and change) before the WWDC 2013 Keynote presentation Apple released the official app to accompany the conference. Due to the (sudden, unexpected, surprising) sell-out of the conference Apple decided on several changes.
For starters the WWDC app allows all registered developers to log in and provides benefits even for developers who did not score a golden ticket. In previous years – if I remember correctly – the app would only let you see its contents if you had an activated WWDC to your name.
WWDC 2013 is even more highly anticipated than any previous Apple event due to the widespread notion that Apple is doomed if they don’t announce many big and impressive new things. For lack of anything better to pick apart, let’s do a bit of tea-leaf-reading on the WWDC 2013 app.
The update was necessary because I had forgotten to add DTSidePanelController to any static library. Without that you could only compile it directly into your app, instead of being able to link in the lib and use it from there.
When I added it to the iOS Static Library and Static Framework targets I found out that I had already coded the delegate to use weak references. The general deployment target (minimum OS version) is still iOS 4.3 which did not support zeroing weak references.
So I also added zeroing weak references support in DTFoundation, via DTWeakSupport.h.
There will most likely not be an iWatch this year, the Pebble is what comes closest to it. It does have an internal ARM-based CPU and it can communicate with iOS devices over bluetooth. There are two kinds of of things you can build for it: watch faces (which don’t have any interaction) and apps.
For today’s project I want to try to put together a watch face that shows the WWDC 2013 Logo and a countdown to the keynote on Monday, June 10th.
Update June 2nd: I made the UTC offset changeable and released a build of the app via mypebblefaces.com
This maintenance update improves Reachability handling. It implements the improvements in DTFoundation made to DTReachability.