Kategoria: ohjelmointi (20 viimeisintä)

I've been trying to create test user accounts for the In-App Store stuff. I've never been successful in that. I've sent three support requests for Apple and never gotten any response. I really don't understand why is it so hard to tell me what I'm doing wrong, since clearly it can't be that Apple's whole test user creation thingy would be broken. That would get lots of developers angry. But no, they don't care, even though they'd get more money if I could get the purchasing working.

Second thing is that they rejected my application a couple of times. They said it didn't work. I told them I've tested it with a couple of devices and with the emulator. All work. Surprise surprise! The problem was at their end and suddenly they accepted the application with no changes!

Third problem, and this is a major one, is that they can't get their emails through to me. You know, I submit an app, they reject it, I never get any information about why. When I email them about this, all they can say is "we'll resend the email." They've tried that several times but the emails don't come through.

Now, I could suspect something wrong with my email severs, but here's the thing: they claim to send to two email addresses. They are on different servers. They are on different email server software. And neither show any emails even trying to come from Apple. But still their support emails come through. Strange. Oh, and I've asked them to copy the error information into the support emails, since they come through. Nope, they don't seem to be able to do that.

I've also tried to suggest to them that they could add a section to iTunes Connect where you could check the error information via the web. That way if the emails don't arrive, you can always check it there. But no. That would be too helpful. They can't do that.

And the most idiotic thing at the moment, and the reason I'm writing this: you can't test applications on devices with newer firmware than the SDK supports! Meaning that every time Apple updates iPhone OS, even a minor update, all developers MUST download the 3+GB SDK package, once again. No matter what you're targeting. You can't use the device unless you update.

I have 3.1.2 on my device. My XCode supports up to 3.1.1. My project is set to produce 3.0 binaries. You'd think I could test the application on my device, since 3.1.2 supports 3.0 binaries. But no, that won't do, since XCode doesn't support the firmware. Two choices: downgrade or install a new SDK. So I'm waiting for the download to finish. Nice. And naturally they can't just put up a diff/upgrade package. All 3+GB every time. Great job, Apple.

But then again, this is the case with Apple's updates too. Huge packages that replace the whole thing. A 160MB update just to fix a couple of security flaws in OS X? Is there something they're not telling us or are they just idiots and can't update the actual files that were changed? Also updating Java in Tiger was fun. Update, reboot. Another update, reboot. Another update, reboot. Why the hell couldn't I just install the latest update and be done with it?

I know, I've been quiet, the certificate is old and the source isn't available. I do apologize. I currently don't even have a machine that would have a working system for compiling mIRGGI, since Carbide sucks, the SDKs suck and Nokia doesn't care about compatibility. You know, the Symbian SDK emulators crash on most people on Win7. It's not like Nokia'd have had time to test them and fix the problems (since they knew they crash on Vista and they barely work on XP). And I'm saying Nokia, because they own Symbian. I'm not letting them use any more of this "it's not our fault, it's Symbian's" stuff.

So I'll try to get the certificate thingy fixed by compiling new versions and the source up somewhere so the interested parties can take a look. Beware: no comments. But that's normal, right?

I'm horribly busy with my studies and stressed out. If you want to cheer me up, send me a plain old postcard. That would be so nice. The address is:

Sami Kuhmonen
Suovatie 18A
FI-01660 Vantaa
Finland

But please, no pipe bombs or anything like that. Thanks!

Oh well, you really don't like me enough :( But as promised, I'll give you something. mIRGGI goes shared source. Which means that I'll open the source, you can add to it and send in the patches and whatnot, but it's not GPL or other crap. One big reason is that I don't want 843975984 forks of mIRGGI just because of "I want this dot to be there and not here" folks. And you're not allowed to use parts of mIRGGI in your own projects. Just because I'm evil.

So stay tuned. It'll happen soon. I just have a physics exam tomorrow, for which I haven't studied, and other stuff. But soon. You'll get to wonder the horrors of my coding and make mIRGGI even better.

Good? Bad? Don't care? At least the development shouldn't be just on my shoulders.

So, it seems that Nokia is dumping Avkon in favor of Qt. The timeline seems to be around Symbian^4 (who was the idiot that figured out that notation?). So, currently application developers are at a strange situation: Qt is not working at the moment (although Nokia has constantly stated that it would be available right now) and Avkon is going to be dumped. Nice.

So, what should we do if we want to create applications for S60? Create the applications with Avkon and rewrite them for Qt next year? Try to use Qt as it is and force users to install it separately and suffer the bugs? Wait a couple of years (decades?) to see when Nokia will get their act straight? That's for each to decide for themselves.

Me? I've gotten fed up with Nokia's stuff a long time ago. I would like to create some business applications for S60, but currently it's still too difficult. XML parsing takes huge amounts of memory, which is not available so I'd have to use some SAX+own code stuff, which is not nice. User interface controls have lots of annoying panics if you don't make sure everything is exactly as they want it (and this changes intermittently - older versions allow you to call method1 before method2, newer crashes if it's not method2 and then method1 etc).

What would it take to get me interested in developing for S60? Qt would probably be a good start. I haven't had much experience with it, but it can't be worse than Avkon and other Symbian APIs. And then I'd like to have a real IDE for S60 development. Carbide is still slow, bloated and buggy. Hell, Carbide.c++ has been available for 3.5 years soon and STILL it's nowhere near commercial grade environment. No wonder Nokia had to put it up for free.

Also one of the most horrible things in S60 development is the "emulator." I say "emulator" because it's just a crappy compilation of S60 on x86 architecture which allows you to code stuff that won't work on actual devices and also make code that works on devices but not on the "emulator." And the startup time... I have fast machines and still just to get the application to start in debug mode takes 1-2 minutes. Each time. Tak about efficiency. How about taking note about Microsoft's actual emulator for WinCE? It actually runs the same binary as the devices and you don't need to boot it every time you want to run an application. That's how it should be done.

What I'd like to see is a working emulator, working SDK (the current has lots of warnings and errors in their headers, for one and it can't even be compiled with current ARM compilers!) and preferrably a plugin for Visual Studio 2010 (and why not 2008, since it looks like the same plugins work in both). Then you could really do some development.

And a hint to Nokia: if you can't be bothered to update Carbide.vs to Visual Studio 2008+, just give me access to the source code and I'll work on it for almost nothing, maybe even for free. I know there are lots of people that would like to use Visual Studio for development since it's a lot better than Eclipse+CDT. CDT's code indexing is slow and many times doesn't even work. Intellisense works every time.

So it's very simple: provide me with the source for the previous release (under NDA) and you'll get a newer version. It doesn't take anything away from you and it only gives the developers the possibility to use the IDE they want to. Deal?

Those of you that get crashes with CTCP Pings, please send a comment with the device you're using, the version of mIRGGI, name and version of the client you use to ping and if it always crashes.

I haven't gotten the crash to happen so this would help me find the exact cause.

Ok, it's out. Sorry it took so long, but now the settings work again.

BTW, you can always get the previous version of mirggi using one of these URLs (just change the version number to what you want):

• http://mirggi.net/mIRGGI_060.sisx
• http://mirggi.net/mIRGGI_5th_060.sisx
• http://mirggi.net/mIRGGI_2nd_060.sis
• http://mirggi.net/mIRGGI_2nd2_060.sis

I finally have time to address the problem with 0.62 not working if it is installed on a clean phone without settings. Hopefully I'll have a working version out within the hour at the latest.

Update: Problem found, compiling new version and uploading...

Version 0.62 should now fix the problems with 5th edition. I had to change the volume keys to function as channel changing buttons since 5800 XpressMusic has no other usable buttons. Settings for servers work (they worked before if you changed them, clicked left and then back) and I changed the default colors to white background and black text.

Otherwise it's the same as 0.61 and 0.60, so only 5th edition users have to update.

To type in, you have to click the input line (I know it's a bit small, I'll make it larger), write with the virtual keyboard and press enter on the virtual kb to send it.

Apple has messed up their developer certificate stuff. The actual certificates work ok, but the provisioning profiles (which are used when testing applications on devices and when sending the application to the AppStore) won't work. Seems that Apple has forgotten to put the certificate information into the provisioning files. And many people are pissed. Fortunately I didn't need my provisioning profiles right now even though I ran into this problem.

Nice work, Apple. Keep it up. It's not ok to mess up stuff for everyone just because you're releasing iPhone OS 3.0 today...

More info about the identity matching provisioning profile mess.

Ok, I finally got my head messed up enough to figure out why the settings weren't working on the 5th edition devices. It's now fixed in 0.61. You can get the versions from the normal locations, 5th edition is at http://5th.mirggi.net/ from now on.

There are no major changes in this version, mainly the 5th edition compatibility and update to the Estonian translation (thanks Henrik!)

Oh, and naturally the certificate thingy is fixed. No need to change dates on your phones to install. Sorry for the delay :(

Text input on 5th edition seems "a bit" shaky, I'll try to fix it now!

I got the Nokia 5800 XpressMusic a while back. I used it for 5 minutes and was horrified. I expected Nokia's first mass marketed touch screen phone to be not that good but I didn't expect this.

The user interface has not been changed in any way to really support the touch screen. There are also lots of nuisances and inconsistencies all around. I can't understand why they let the device go to market like this.

Oh, and the problems are still in the current version on my phone (21.0.026.C02.01)

1. In some places (like the application grid) you can use single click to start an application. But when using settings screens etc you have to click twice. The first click only selects the item, the second activates it.
2. You have to use lots of clicks to change text settings. For example, change your password on the MfE client. Click on Password to select it. Click again to activate. You'll get an empty text box on the screen. Click it to open the keyboard. Click Ok to accept the text. Click Ok again to accept the text. This is how it should be?
3. Many binary (yes/no) settings need lots of clicks. First to select, second to activate, third to select the other option, fourth to activate it. In iPhone, WMobile etc you only need to click the check box/slider. That's it!
4. On-screen keyboard is horrible. The small is too small to use without the stylus. The large one always rotates the screen, so it's quite impossible to use one-handed. Also all accented letters need four clicks to get (first open the accent menu, then select the accent section, then the character and then change back to normal letters). Horrible.

And that's just some of the most irritating ones. I would tell Nokia to do as Microsoft and Apple did, but it won't help since they already did that. They just thought it wrong. Apple and Microsoft took an existing mouse-operated UI, tweaked it and put it into a touch screen device. Touch is like a mouse, so it works. Nokia took an existing D-pad-operated UI and used it as such without thinking. Way to go!

And yes, I do know that Symbian itself has supported touch screen/mouse for a looong time, so actually, Nokia did nothing. They just added the touch screen.

But no worries, I'm sure Qt4 will fix this. Too bad we'll have to wait for it for some time still...

Nokia opened Ovi Store, finally. And I was not disappointed at all. It was as bad a mess as I thought it would be. And I'm not talking about the capacity problems and stuff.

The logical comparison is between Apple's AppStore and Nokia's Ovi Store. Both sell applications for the users of their devices. So let's do some basic comparisons:

So, I want to make a freeware application (actually I've already done one for the iPhone). With Apple I'll pay $99 for the first year. That's it. With Nokia I'll pay at least $220 for getting the application in. More than double. So, it's not a reasonable route to get freeware applications to users. Oh, and when I need to update the application, add features etc, I'll have to pay at least $20 every time. With Apple, it's free.

Ok, forget the freeware. I'd like to get some revenue from the application. Let's say I'll charge $1 for it since it's a small application and people are willing to pay that amount for it. With Apple I'll have to get 142 new purchases per year to break even. With Nokia I need 314 purchases for the first year if I don't do any updates and I only use credit card billing. If the customers are via operator billing, then I'll need at least 550 purchases to break even.

But since all applications will be updated, this is not the case. With Nokia, every time you update the application you need to sell 29 more applications. So you really have to think if the update will get you more customers or not. With Apple it's free.

Also, if you're not part of the Launchpad program, you'll have to pay $50/application to get them into the store (is this still valid?). So the purchases needed goes higher and higher.

Someone tell me why I should use Ovi Store? To get the application into millions of devices? Oh wait, the actual store application isn't available in more than a couple of countries. And only for two devices. So that's not going to be a reason for me until it's available everywhere and on every S60 3rd edition+ device.

So in my book, Nokia messed things once again. Even though they did ask a couple of Finnish companies how things should be done and the main answer was "like Apple's store." But no such luck.

Finally, my application Telkussa (iTunes needed to open the link) got into Apple's iTunes AppStore. It only waited for four months for all the legal crap and Apple's slowness. But there it is!

And more: it's the Top 2 free application now. And it's only been out for a couple of days. Woohoo! :)

So, I'm an accredited Symbian developer. Pheer my Symbian skilzzors!