Comments on: TouchXML for the Win! http://www.chewyapps.com/2008/09/25/touchxml-for-the-win/ Hi, I'm Henning, and I'm an iPhone developer. Sun, 29 Jan 2012 02:25:52 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Louis St-Amour http://www.chewyapps.com/2008/09/25/touchxml-for-the-win/comment-page-1/#comment-70 Louis St-Amour Wed, 15 Jul 2009 17:25:24 +0000 http://www.chewyapps.com/?p=28#comment-70 Cool, I figured as much. I was writing more to clue others in -- it's likely why TouchXML is read-only, you shouldn't use XML for your internal storage, but you may need to parse it from elsewhere. Cool, I figured as much. I was writing more to clue others in — it’s likely why TouchXML is read-only, you shouldn’t use XML for your internal storage, but you may need to parse it from elsewhere.

]]> By: henning http://www.chewyapps.com/2008/09/25/touchxml-for-the-win/comment-page-1/#comment-69 henning Wed, 15 Jul 2009 17:22:16 +0000 http://www.chewyapps.com/?p=28#comment-69 Yeah that's what I do now. Back then, I didn't know. :) Yeah that’s what I do now. Back then, I didn’t know. :)

]]> By: Louis St-Amour http://www.chewyapps.com/2008/09/25/touchxml-for-the-win/comment-page-1/#comment-68 Louis St-Amour Wed, 15 Jul 2009 17:19:18 +0000 http://www.chewyapps.com/?p=28#comment-68 If you're the only application to use the data, why not use a plist file instead of XML, it's built-in and works perfectly -- e.g. Save an NSDictionary, get one back. Plus on a Mac you can instantly create them with the Property List Editor and other languages also have plist modules, e.g. Ruby's plist gem. If targeting 3.0, I'd suggest Core Data also/instead, because NSFetchedResultsController is so much fun. One of these days, I should write a tutorial for an NSFetchedResultsController implementation of SearchResultsControllerDelegate, as I just figured it out yesterday, and it highlights the simplicity of using FetchedResultsController with Core Data instead of managing your own data source manually. If interested, feel free to email me at LSTA at yorku dot ca, which will encourage me to write it up. If you’re the only application to use the data, why not use a plist file instead of XML, it’s built-in and works perfectly — e.g. Save an NSDictionary, get one back. Plus on a Mac you can instantly create them with the Property List Editor and other languages also have plist modules, e.g. Ruby’s plist gem. If targeting 3.0, I’d suggest Core Data also/instead, because NSFetchedResultsController is so much fun. One of these days, I should write a tutorial for an NSFetchedResultsController implementation of SearchResultsControllerDelegate, as I just figured it out yesterday, and it highlights the simplicity of using FetchedResultsController with Core Data instead of managing your own data source manually. If interested, feel free to email me at LSTA at yorku dot ca, which will encourage me to write it up.

]]> By: Henning http://www.chewyapps.com/2008/09/25/touchxml-for-the-win/comment-page-1/#comment-3 Henning Wed, 01 Oct 2008 17:15:45 +0000 http://www.chewyapps.com/?p=28#comment-3 Thanks Dean, your tutorial helped a lot! Thanks Dean, your tutorial helped a lot!

]]> By: Dean http://www.chewyapps.com/2008/09/25/touchxml-for-the-win/comment-page-1/#comment-2 Dean Sat, 27 Sep 2008 11:05:17 +0000 http://www.chewyapps.com/?p=28#comment-2 Hey Mate, Dean here from over at dBlog.com.au… Glad to see that my TouchXML tutorial helped you out! Good to see other people blogging on their iPhone SDK experiences! Keep up the good work, -Dean Hey Mate,
Dean here from over at dBlog.com.au…

Glad to see that my TouchXML tutorial helped you out! Good to see other people blogging on their iPhone SDK experiences!

Keep up the good work,
-Dean

]]>