Given that between iPhone, Android and Nokia, the last one is the only on which you had (have) to pay to develop for that's a big step forward ;)

Have you really tried the iPhone development? Maybe you can teach me how to deploy my Hello World application to my iPod Touch without having to "pay to develop" ...

In case you want to learn more have a look at http://tinyurl.com/iPayToDevelop

Hurray ..

In addition development for iPhone/iPod starts with visiting a shop and buying a Mac, at least as I know. The alternative is hacking the OS to a PC, in an illegal way. Of course this latter one is more or less "free".

And this current release is Carbide.c++ 2.0... Guess if there was eariler releases, including the free Express editions. A lot earlier than iPhone or Android have been even announced.

This is huge news!

Fantastic news :)

next: free from Publisher ID?!?!

When can man publish a Symbian App without a Publisher ID?

of course without limit of capabilities (e.g. except 3 important for OEM)?

A Publisher ID costs 200€ per year and not available for private developer...

The world is not perfect, however, today's announcements makes it a lot better than it was yesterday. From a Symbian developer perspective anyway :) Let's enjoy this moment and we can start asking for more tomorrow.

Finally, all versions became free. I believe this is a big step in the right direction. Great news!

1. Does the development on the Carbide C++ 2.0 will solve the certificate error? If no, how can we participate with our idea?
2. According to the forum, published by Mr. Tom Libretto, Nokia Forum VP, binaries developed on the SDK S60 5th can be deployed on phone systems S60 3 F1 ? is that correct?

"The versatile developer support offered by S60 5th Edition enables developers to write applications in a range of languages that they are already very familiar with; said Tom Libretto, Vice President, Forum Nokia. That familiarity and being able to arm developers with the tools and technologies that best suit their needs will allow for further innovation of new applications and services, not only for S60 5th Edition, but also for S60 3rd Edition"

1) I don't know abut what error are we talking about but in general, the IDE has little to do with signing, it just calls the signing tools with the certificate provided. There's nothing that Carbide.c++ 2.0 can do (either good or bad) about certificate errors. If you have an active discussion about this on the Discussion Board please post a link here and we can together analyse the issue.

2) I have to admit that I'm not familiar with this message from Tom Libretto, I will look for it. However, from what you quote above you must have misunderstood the message. Whether one can build with one SDK while targeting a device based on a different release that is governed by a basic rule: binary compatibility. In S60 we strive to maintain backward compatibility but forward compatibility should not be expected (although it might in fact exist). What this means is that you can expect applications built on old SDKs to run on newer devices but not the other way around.

Latest news of Carbide 2.0 says it runs over sdk 5th Ed.
Could it run over sdk 3rd Ed. FP1?

Yes, it works with all S60 3rd Edition SDKs and if you really put your mind to it you can also make it work with S60 2nd Edition or Series 80 SDKs (see my previous posts)