Could someone provide a good link to book about how to develop iPhone application with the Perl programming language?
+7
A:
Generally Perl is not a good choice here. Without jailbreaking the iPhone, you will need to compile perl into a static library and link it against your byte-compiled code (or build a small app that glues the two together). This seems a lot of work for little benefit, since Perl has no bindings to the various Cocoa and UI elements you'll need to manage your run loop. Why do you want to use perl here?
Jailbroken development is outside the license agreement. Searching "perl iphone" will give you several links on the subject, but I really can't go much further into that.
Rob Napier
2009-12-11 15:39:58
Which langaues you suggest instead ?
dan
2009-12-11 15:53:39
@dan: The usual choice is Objective-C.
Adam Bellaire
2009-12-11 16:38:50
Why? Because it's Perl, duh! :)
Robert P
2009-12-11 18:35:44
+7
A:
Why would you want to use Perl? You'd miss out on everything the iPhone SDK gives you, and you wouldn't be in the iTunes App Store.
If you are trying to use Perl because it's the only language you know, just bite the bullet and learn Objective-C. Use the right tool for the right job. Despite how much I enjoy working in Perl, I don't think it's the answer to every problem.
However, if you did want to use the Perl route, you could use it to drive an HTML-based app. You end up installing a mini-website with local storage, etc, on the iPhone. Building iPhone Apps with HTML, CSS, and JavaScript is in O'Reilly's Open Feedback Publishing System, so you could see how to do that for free. Perl might be a tiny, server-side component of that.
brian d foy
2009-12-11 19:20:37
A:
If you mean backend to a iphone application (via XMLRPC), then we are all behind you I believe.
hpavc
2009-12-11 21:20:49
+3
A:
If you insist on Perl, relax your constraint on it being an iPhone "application". Make it a web application targeted for the iPhone!
Pros
- You can use all the Perl you want! Even Catalyst!
- Any version of Perl you want, in your own configuration.
- Cross platform with other mobile/Internet devices.
- Way easier to deploy updates and bugfixes.
Cons
- Requires a constant internet connection.
- Is accessible outside of the iPhone enviroment.
- Isn't in the iTunes store.
- Tradition breaker.
Mark Canlas
2009-12-11 21:26:33
Why is it a tradition breaker? Many of my favorite iPhone apps are just frontends to websites. Also, you can still put the client in the iTunes App Store.
brian d foy
2009-12-12 01:36:37