Can I run Anjuta from my desktop and use it on my N900? is it usable?

YES! I can and YES! it is :)

I know because I tried it :)

The goal of eBrainPool is to be able to use software from any device around you. This could be a Desktop,Laptop, Mobile phone or tablet or any other device with a computer in it. This could be running any Operating System on any Architecture and you should still be able to USE it on your device. Software hosted on any device, Run from any device but Used on the one you have in front of you at that time :)

This weekend, while taking a break from writing the libssh based ssh server for eBrainPool, I decide to see how the premise of eBrainPool would actually look and feel. We've tied up software from our debian laptops,netbooks and other desktops into one big software pool and used software off each other. We've also got bits and pieces of the code working on the N900 as the Moving towards the N900 post shows. What we've not yet done is actually run software from a our debian based desktop/laptops across form factors onto a small screen device like the N900 or Android - and I was very curious :)

While our current code is not yet ready for the N900, I didn't really need the mesh network or any of the other fringe features we plan. For now all I wanted to do was "SEE IT WORK" :)

A simple ad-hoc network between my debian system and the N900, the SSH tunnel setup and X forwarding had Xeyes running from my deb system on the N900. I slide my hands over the touch screen and the eyes follow me around and it feels awesome :)

Next I try gedit...and yes it works...and yes it was fairly usable :)...I type a note to myself and save it.

Next Anjuta :)....and yes it works...and while it is more congested because the user interface is definitely designed for a larger screen size....I could definitely go through the eBrainPool code in Anjuta and compile it no problems whatsoever :)

Then I got cocky and decided to try an OpenGL game....and this of course bombed...the N900 may not have the GLX extensions and probably a hardware that supports it. This was expected since the way X works is that it uses the graphics hardware on the device to which the display is actually connected to render unlike screen sharing software (as demonstrated in the post X rendering, measured using gtkperf ....but we shall see what we can do about this too sometime in the future ;)

Now back to some code... :)

Additional note: I want to clarify that what this also demonstrated was code compiled and built for the amd64 architecture being used on an A8-cortex RISC based processor in the N900.

Previous Post Next Post