Seriously, though. If you’re doing iPhone development, sure you get the Cocoa framework and access to OpenGL and all that, but you don’t get such open access to the system and other applications (with Sync!) like you will with webOS. At least, that’s my hunch, I guess time will tell. But just the basic layout of the high-level architecture warms my heart.
You know what else is awesome? The API has “stages” and “scenes”! That rocks.
Jury is still out as to whether you can run processor intensive games in this platform, but honestly we’re not game programmers, and this does seem to uniquely enable easy development.
On a total tangent, I went to the Jelly NYC event at my workspace today and mentioned that next week we’ll be starting the beta for Strip on the iPhone (sign up for the mailing list over here, or just e-mail us). Of the 15 or so people there, one of them was a hard core, long-time user of Strip, and is still toting his Palm around waiting for a way to migrate to his iPhone. Can’t wait. Stay tuned!
We’re going to push out a couple of changes to the Tempo API tonight at 10pm EST. Last night we found a small bug that prompted us to address a pair of issues, and update our documentation:
A type attribute will be required for multi-value params in context search:
The /entries/search end-point allows you to post an XML document that we call a context. It’s a lot like the Tempo reporting interface, it allows you to specify a set of parameters and it will return the corresponding entries if the request is well-formed.
Certain parameters that you can send up in a context document are multi-valued and must be presented within a type=“array” set. These are tags, project-ids, user-ids, and exclude-tags. Here’s an example:
This has actually always been the case, but our documentation did not reflect this.
The interval parameter will be supported in context search:
As shown the example above, you can use an interval shortcut string to avoid having to specify start-date and end-date. The list of currently available intervals is:
XML output includes type attribute hints:
For all non-string data in output from our XMLAPI, a type attribute has been re-introduced. This shouldn’t break anybody’s compatibility with the API, as we haven’t had any attributes present in the past for you to look up, but please get in touch if you think this will be a problem for you. This is an example of what that looks like:
Zetetic LLC is a small company specializing in applied data security. As the developers behind the SQLCipher encrypted database library and Codebook Password Manager, hundreds of organizations and millions of users trust Zetetic’s software and frameworks.