Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Cocoa is only available in Objective C. (It has never been supported in C++ IIRC.) It used to be supported in Java too, but Apple has deprecated that option.
For the iPhone maybe, but on Leopard Apple does support Cocoa in languages other than Obj-C such as Python (PyObJC 2.0 is included in Leopard) and Ruby.

Its a shame they couldn't have python supported on the iPhone, I would also prefer to develop code in python, I guess I'll be learning Obj-C.
 
What the hell, people?! Read, watch and learn, and post less BS..

Oh god, I just read on another site that Apple is restricting each app to only run while on screen. Once you change screens or take a call, etc...the app quits! What the hell? Every single phone, even the dumbphones can multi-task. What the hell, apple?

http://www.techcrunch.com/2008/03/07/iphone-sdk-some-of-the-details-arent-great/

"What the hell, Apple?" - What the hell people... :mad:

Before you spread silly rumors, perhaps you folks should educate yourself a tiny bit first. I have just watched the iPhone SDK developer intro videos (have you? do you understand them?) and can tell you that the Apple iPhone applications WORK THE SAME WAY. The trick is for your application to SAVE STATE. Rest your case, it will all be good... jeez.
 
"What the hell, Apple?" - What the hell people... :mad:

Before you spread silly rumors, perhaps you folks should educate yourself a tiny bit first. I have just watched the iPhone SDK developer intro videos (have you? do you understand them?) and can tell you that the Apple iPhone applications WORK THE SAME WAY. The trick is for your application to SAVE STATE. Rest your case, it will all be good... jeez.

What about an app that hits the network frequently? like fire eagle? What then?
 
I guess people will just complain regardless of what Apple does.
And plenty of fanboys will blindly defend everything Apple does. Look, the iPhone is fantastic. It has the potential to completely change the industry, and because of that I see danger in setting the precedent that Apple should have complete control over what runs on it. Personal computers and the web succeeded exactly because anybody could create anything they wanted, without begging anyone for permission. The iPhone restrictions aren't as bad as they could have been, but they will still stifle creativity, innovation, and freedom.

How is iTunes distribution bad?
It isn't. An official channel for Apple-approved iPhone apps is great. The problem is having it be the only option. Would you prefer that Apple lock down Mac OS X so you could only get apps through apple.com?
 
Oh god, I just read on another site that Apple is restricting each app to only run while on screen. Once you change screens or take a call, etc...the app quits! What the hell? Every single phone, even the dumbphones can multi-task. What the hell, apple?
Sounds like a good idea to me from a battery life point of view, you don't want apps sucking CPU time in the background while you're not using them. iPhone is really a one-app-at-a-time device like Palm Pilots used to be, which I think makes a lot of sense given the screen size.

Presumably apps will be sent a kill message so they can save relevant data when interrupted by a call, so I don't see why this should be a big deal.
 
What about an app that hits the network frequently? like fire eagle? What then?

I think this was well answered in a post in the previous link's comments:

"Allowing things to run in the background on a cellphone (a device so private) is worrysome.. sniffing data (if technically feasible).. eavesdropping calls.. (if technically feasible).. routing to different nets (if technically feasible)….."

And

"Reliability is king for mobile apps"

Just for the record, I am not saying that I know so much about mobile apps (definitely interested for sure, as of yesterday evening), but I just believe it might be a welcome change to the smart phone business if there is some control and stricter guidelines for a few things.

I've had a crappy Nokia E61 in the past and if you had as much as installed Tetris on it, Nokia was fast to point out that they would take not a single look at the crappy device as to why it kept jumping off WiFi networks and what have you. I've had dozens of Nokia horror stories. Not one glitch on my iPhone. That doesn't make me a fanboy more than the fact that I prefer things that work reliably. And it happens to be that my experience with Apple products far surpasses anything else tech-wise on the grand scale. Nothing is perfect, but show me a manufacturer that's closer.

I'll take a slightly slower adaption to new and "what's technically possible" anyday if it comes with reliability.

And for those mega-tweakers, I'm sure Microsoft and Yahoo will come up with something that makes you all happy dancers. Think - what's the name again... Zune-Phone or whatever... :D

http://video.google.com/videoplay?docid=1274983729713522403
 
One would have to assume MS will work on a mobile version of Office for the iPhone, right?

Otherwise, I guess things like NeoOffice could start popping up, so the iPhone can finally have word processing built in, to satisfy all the WM users.

Anyone heard any rumors to this effect?

PS- As an iPhone user, we are finally starting to realize the potential of these devices, and making it easy to forget the price tag. Name another company that supports their product SO WELL, even months or years after it was released!

Makes me proud to be an :apple: die hard.


Can you imagine Microsoft sharing 30% of iPhone Office revenue with Apple...

Not sure if that would happen...
 
I think this was well answered in a post in the previous link's comments:

"Allowing things to run in the background on a cellphone (a device so private) is worrysome.. sniffing data (if technically feasible).. eavesdropping calls.. (if technically feasible).. routing to different nets (if technically feasible)….."

And

"Reliability is king for mobile apps"

Just for the record, I am not saying that I know so much about mobile apps (definitely interested for sure, as of yesterday evening), but I just believe it might be a welcome change to the smart phone business if there is some control and stricter guidelines for a few things.

I've had a crappy Nokia E61 in the past and if you had as much as installed Tetris on it, Nokia was fast to point out that they would take not a single look at the crappy device as to why it kept jumping off WiFi networks and what have you. I've had dozens of Nokia horror stories. Not one glitch on my iPhone. That doesn't make me a fanboy more than the fact that I prefer things that work reliably. And it happens to be that my experience with Apple products far surpasses anything else tech-wise on the grand scale. Nothing is perfect, but show me a manufacturer that's closer.

I'll take a slightly slower adaption to new and "what's technically possible" anyday if it comes with reliability.

And for those mega-tweakers, I'm sure Microsoft and Yahoo will come up with something that makes you all happy dancers. Think - what's the name again... Zune-Phone or whatever... :D

http://video.google.com/videoplay?docid=1274983729713522403
In the very same link you quote from a poster brought up something interesting. If no app can run in the background how does mail do it? How is it supposed to know when to recieve Exchange Mail if there isn't a constant connection back to the server that can run even in the background?

That same poster claimed that Apple is using the same SDK that they released to the developers, but it looks like some restrictions just don't apply to them.

Or think of it this way, if someone wanted to make another Mail program for the iPhone (for whatever reason) they could never offer Push Mail capability because the program can't run in the background like how Apple's Mail does.
 
Sounds like a good idea to me from a battery life point of view, you don't want apps sucking CPU time in the background while you're not using them. iPhone is really a one-app-at-a-time device like Palm Pilots used to be, which I think makes a lot of sense given the screen size.

Presumably apps will be sent a kill message so they can save relevant data when interrupted by a call, so I don't see why this should be a big deal.

Yeah, that's pretty much the Palm model.... until they went cellular. Then the problems of 'always on' vs. saving state really upset the stability cart.

I've only just begun reading the documentation in the SDK, but I suspect that although all apps are built using the same SDK, there will be restrictions imposed by certificates (or similar) that will determine whether the app will run in kernelspace, userspace, phonespace, hell, ipodspace, for all I know. Each jail will then have its own restrictions.

I'll be interested to see how they've implemented scheduling in the kernel. Comments at the conference notwithstanding, I'd expect it to be different given the above.

BTW, this makes using SQLite even more intelligent. It's superfast, so the whole 'send interrupt, save state, switch out' process will be more or less seamless. Sure beats the pdb structure used by Palm. Side note: It seems like SQLite is taking over the embedded world.
 
And who is exactly forcing you to develop for the iPhone.

If you don't like the terms then **** off!

Yes, that's an intelligent comment. If anyone has any criticism, ostracize and make fun of him.

Certainly no progress can be made with such attitudes. I suppose by the same logic, if one criticizes the US at all, he will be told to "*** off" too. Everything is perfect and there can be no improvement. Come back to reality! Criticism and free thinking is the mother of progress.

BTW: Those telling me to develop my porn application elsewhere need to take a basic reading course.
 
noooooooooooooo! I'm not getting Leopard until Monday, and I can only get Internet on weekends. Another week without the SDK! Curse you Apple! :(
 
And plenty of fanboys will blindly defend everything Apple does. Look, the iPhone is fantastic. It has the potential to completely change the industry, and because of that I see danger in setting the precedent that Apple should have complete control over what runs on it. Personal computers and the web succeeded exactly because anybody could create anything they wanted, without begging anyone for permission. The iPhone restrictions aren't as bad as they could have been, but they will still stifle creativity, innovation, and freedom.

And the personal computing industry also had to spend trillions of dollars in protecting consumers from all the creativity, innovation, and freedom you speak of. How good do you think the iPhone will be if users had to have a mobile version of anti-virus or anti-spam on the device? Might as well have Windows Mobile.

It isn't. An official channel for Apple-approved iPhone apps is great. The problem is having it be the only option. Would you prefer that Apple lock down Mac OS X so you could only get apps through apple.com?

Mac OS X apps and iPhone apps are two entirely different beasts and should be treated as such. And just because your getting them THROUGH Apple doesn't mean their FROM Apple. Its a BIG difference and I think many people are getting confused. Aside from porn apps (which is completely pathetic IMHO), all the restrictions Apple is placing on app development are to keeping people from exploiting Apple, AT&T, and innocent consumers.
 
Might as well have Windows Mobile.

Might as well shoot yourself in the face as far as i'm concerned. Having to run anti-spam on an iPhone, that would be quite terrible.

Also like you said...
Do i really need a porn app on my iPhone?
Should i really be VOIPing on edge?

If you really want to have porn on your iPhone then just look some up in safari, and if you really need to VOIP then why the hell do you have an iPhone
 
In the very same link you quote from a poster brought up something interesting. If no app can run in the background how does mail do it? How is it supposed to know when to recieve Exchange Mail if there isn't a constant connection back to the server that can run even in the background?

That same poster claimed that Apple is using the same SDK that they released to the developers, but it looks like some restrictions just don't apply to them.

Or think of it this way, if someone wanted to make another Mail program for the iPhone (for whatever reason) they could never offer Push Mail capability because the program can't run in the background like how Apple's Mail does.

This is a problem but a good one to have. There is something to be said for "trusted" programs. Mail is an example of that. Because of its unique functionality, it has to continuously run. I believe programs like instant messaging from trusted developers will be given this same functionality. Not allowing programs to run in the background is a good way of protecting users. Just think about it. A phone has all your information connected to it. Your account, SSN, location, and much more. If malicious programs were running in the background, a user would never know if it were recording their conversation or stealing your identity. Yes DEVELOPERS (not people commenting on MacRumors who don't know what their talking) will have problems with this, but Apple and AT&T have millions of subscribers to think about.
 
What about an app that hits the network frequently? like fire eagle? What then?

The same way as you should on MacOS.
Well crafted Launchd plist.
use them to periodically call your app to do an update.
or use them to get the system to wake your app on data received.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.