Re: Portrait mode use cases
 

cool 2 new vids:
http://www.youtube.com/watch?v=zBKSBAaJpc8
http://www.youtube.com/watch?v=R6OnWuZ9mYs

the 1st being more important... he clearly says...that it's not that it couldn't be done (portrait), nor that they wouldn't do it...it's just they thought the features would be better to use on landscape...and if enough people want for eg. the browser in portrait, it could be done...

so, we might get what we want in firmware updates :D

Re: Portrait mode use cases
 

so... the first video show that we can use the picture gallery in portrait mode right?

Re: Portrait mode use cases
 

Oops :) Houston we have been uncovered :) Yes, but the video is really about: The EXACTLY same code running on Maemo and Symbian :)

*ps it's Not nokia 2.0. It's a QT experiment to really try to prove (no IFDEFS) that you can indeed have the same same code on 2 platforms. So in the end.. doesn't matter if it's Maemo or Symbian :) good for developers!


:)

Re: Portrait mode use cases
 

What does 'exact same code running on maemo and symbian' means?
Simply that it doesn't need manual porting work during the build phase, or that they're somehow binary compatible (like OSX with dual intel+ppc binary bundles)??

Re: Portrait mode use cases
 

For a portrait text input method, could the dialer keypad not be modified to allow for alpha-numeric text entry ala your bog standard mobile phone? That seems to be the main requirement here.

Re: Portrait mode use cases
 

So no manual intervention (or if def to allow platform specific stuff to be loaded) when compiling.

After that, we will have PySide (QT bindings) working, then we will have exactly the same "binary" running in both platforms.

:)

Re: Portrait mode use cases
 

They could be using that web framework they were going on about some time back.

In a speculative case, the container for running the javascript/html/whatever could be some natively compiled qt client with an exposed API to system resources (files/sound/accelerometer/etc). If you mirror the client on many machines (regardless of the OS), then the same javascript code will run -- exactly how web browsers work today. The benefit is run-anywhere, easy to develop and test code. The cost is app performance (you won't likely see an PSX emu developed this way).

This is WILD speculation (none of it is real information), but it's a reasonable solution with some very large benefits.

}:^/~

Re: Portrait mode use cases
 

Yes this was wild speculation :)

We are not using any web based stuff. But you pointed out exactly the point : If we go Javascript, python or any other dynamic language you pay the price for performance.

That's why the code is PURE QT, and thus runs on the N97, and the N900 without any modification to the source and no ifdefs.

It would be too simple to use JS on top of QTwebkit :)

The demo is to demonstrate that Nokia is getting there :) real cross platform development :)

BR

Marcelo

Re: Portrait mode use cases
 

This must be what Eldar found exciting and what he hinted to be announced at the event on the 2nd\3rd Sept. Why didn't Nokia simplify the message of 'cross platform apps\developments' that could really rock the news?

I'm not talking about making baseless hype, but a little factual excitement can't be that bad.

Re: Portrait mode use cases
 

This is very interesting indeed. Is there a wine type layer in between on at least one of the platforms? What is the Symbian executable file format like? Is it somehow compatible with elf (assuming maemo apps are compiled to ELF)?

I'm very curious about this (links would be lovely). From what I understand, unless the apps are being compiled to processor-and-os-independant byte-code (which should be entirely possible), this is a hack at best. If for example the processing architecture changes with natively compiled apps, then you'll have to emulate to run apps which can bear a heavy processing/development cost. I think this is why Google went with java as the platform for android apps (uh, I think). Perhaps there's something I'm missing?

\:^!~