Not much time has passed since the initial release of BarCodeKit. But time enough for Mr. Andy Qua to generously provide an implementation for the Interleaved 2of5 code.
This is a maintenance release addressing several crashing problems.
iOS7 will have the ability to scan 1D and 2D bar codes built-in. The same is true for generating 2D bar codes. Which begs the question why Apple opted to omit support for creating 1D bar codes. (rdar://14694904)
One second hand explanation I heard was that laser-based scanners might have trouble reading 1D codes from the screen of an iPhone, whereas 2D codes require a camera anyway and therefore can be easily scanned even from a display.
While this explains the omission to a certain degree, I don’t buy it. I can think of many scenarios where you would want to print a 1D bar code, or put it into a PDF that is supposed to printed. Also, as CCD-based scanners become more prevalent they will soon be available in larger numbers than laser-based scanners.
In short, I am seeing a niche that is not being served. Thus I’m announcing BarCodeKit.
Update: If you have trouble building via CocoaPods please make sure that you have version 0.23 and also refresh your pod specs. I had to – once more – modify the spec to fix a build problem. Sorry for the inconvenience.
It became apparent that we should have a standard method for logging in our frameworks. Some of use are happily using Cocoa Lumberjack in product apps, but not everybody might share this test. So there was a need to have some sort of looking hooks in our shared library code. This would allow everybody to hook up his own favorite logging framework or simply use NSLog.
In this blog post I am explaining the rationale behind DTLog, new in DTFoundation as of version 1.5.1.
There is no notification to be gotten if the user adds or removes files to your app’s documents folder. The only way to update your list of files in that case is to monitor the folder for changes. There are several different approaches to achieve this, the traditional one being the File System Events API.
But since iOS 4 – together with GCD – Apple added a simpler method for monitoring a vnode, dispatch sources.