Native Development

[bdaemon]

[BGmot]

What's possible? -)

[taylortbb]

I think the question is, could they offer Momentics in App World?

Momentics does run on QNX so it seems theoretically possible. It depends on libraries like GTK that aren't available on the PlayBook yet though.

[BGmot]

Momentics in AppWorld?
***Bgmot shakes his head***
Anyway if you want to buy I can sell ;-)

*Edited*

I do apologize and take my words back. Just did not think that widely - developing on Playbook itself...

[fernando_simoes]

Yes, the hardware setup is not only possible, but a quite interesting idea.

Maybe it's about time to have someone porting EMACS to PlayBook!

[BGmot]

RIM owns Momentics IDE, how would you see the process of making it possible if someone outside RIM decided to port needed components?

Thanks.

[elena_laskavaia]

Not it is not possible, it is written on java (J2SE) and java is not available on playbook.

So far starters:

a) port J2SE

b) port SWT and other native runtime eclipse components

Then we can talk

[cycletronic]

Changing the original question a little bit, is it possible to compile and run code all on the device?  In other words, can I instead port emacs or vim and a shell like xterm, write some code on the PlayBook, then compile and run it from the terminal, all without connecting to a PC?  

I don't currently have resources enough to do this, but it would be interesting to know if it is possible.

[elena_laskavaia]

You need gcc compiler compiled for arm, we don't ship that, but if you find it you can try. There is I think terminal app for playbook. What is wrong with desktop development?

[BGmot]

There are obvious benefits like:

- you do not care about simulator (whatever we say there are/might be) differences in app's behaviour on SImulator and on real device).

- you do not need different third-party libraries compiled for Simulator and Device

- you save tons of time on pushing the app to Playbook in case you work on large project. Transferring .bar to the device *is* slow.

- it is just natural - to develop an app on the OS/architecture where it is supposed to work.

Though I am not sure these benefits are worth effort of bringing NDK to Playbook.