You might have a stab at the VSCL ... its possible

As far as I could make out (esp looking at the ext api) they've got a halfway house to MIDP2.0 there

To be fair on O2 its not then keeping the SDK secret - they didn't even know there was an SDK. Even worse Benq didn't know one existed - or if they did they deliberately hid it. We pestered their guys in Holland for ages and they came up with nothing).

I'm not sure where you got yours (not a Macrospace guy are you ?) but we obtained ours through some Chinese guys who know the people at Benq very well.

We have given O2 the SDK - but only on the understanding that they get permission from Benq to redistro - as the license afaics doesn't permit that.

I'll second that.

"Roughly" K700 speed - I would say not quite as fast - but definitely respectable.

Worst thing I've found so far - it has a dedicated Image heap area which unlike  the S/E doesn't gracefully swap between user heap and Image heap. So if you blow the image heap (did I really want to load that 160KB image)  it just dies on you. It also seems to have some problems when the heap is quite full and it can't fit another image in.

In classic Samsung style the keypad isn't mapped properly with getGameCode() - only "5" appears to work.

If you're very nice I can provide you with some api details. (We originated the SDK for O2).

I can't distro the SDK I'm afraid but can give some hints ;-)

Not possible I'm afraid

I trawled the SDK (I couldn't possibly say I decompiled it) - and there's actually a naughty little call "suppressSoftKeys(boolean)" or similar that's activated when in fullscreen mode.

I fiddled around with various dummy menu options but came to the conclusion that the only safe thing to do is abuse the "*" and "#" keys as the softkeys.

This probably doesn't help you much but we developed our own emulator - still some way to go to cover all apis.

However, for "logical" debugging it rocks. You can run your midlet in process from within Eclipse and its FAST. You know how all those emulators from Sony/Samsung/Sun - even the S60 ones - drag their feet ... this blows them away. It makes the s40 emulator look sluggish.

The emphasis here tho is on logical debugging.

So :
1. You can make sure game logic/collisions etc work
2. You can verify that the application complies with device behaviour (key codes etc).

but

1. Heap profiling is out - well tbh even with the Nokia emulators this is touch and go.
2. Speed testing is unrepresentative.
3. We haven't sorted all the font issues yet ... so font behaviour is off (but then I haven't found an emulator that does this properly yet anyway).


It makes a huge difference tho for  getting the application to a state where you're confident wierd behaviour on the device - is the device's fault.