FIRST OPENMOKO IN THE WILD!

[Rodolphe Ortalo]

Le jeudi 08 mars 2007 à 10:16 -0800, michael at michaelshiloh.com a écrit :
> 
> 
> On Thu, 8 Mar 2007, Harald Welte wrote:
> 
> > On Wed, Mar 07, 2007 at 09:51:18PM +0100, Rodolphe Ortalo wrote:
> >> Le mercredi 07 mars 2007  12:26 +0100, Harald Welte a crit :
> >> [...]
> >>> We neither have a working dialer application nor GPRS implementation at
> >>> this point of time.
> >>
> >> Btw, would it be possible to know which applications are supposed to be
> >> somehow running today (as opposed to simply core-dumping or really at
> >> initial first stage)?
> >
> > As of now, I would not assume anything above the
> > bootloader/kernel/driver/userspace/glibc/libx11/xserver level to work
> > reliably.
> 
> I can add that xterm works very well. I think the touch keyboard may have some
> key bounce issues, but it could very easily be my old eyes and poor touching.
> If it improves in the next few days we'll know it's me and not the
> application.
> 
> All of the command line utilities that I've used so far work fine.

My question was mostly targeted at a demonstrator or local test build
only.

>From what I see in another window currently (built and running on an x86
host in xoo with my top auto-thing), I'd say that contacts,
openmoko-messages, today or even the openmoko-dialer are not in such a
bad state. (I still have to understand the intended operation of the
openmoko-taskmanager too but it show the wheel and the other apps at
least.)
I can switch between the apps, show the dialer (starting the app twice),
the phone book which amusingly reuses my local evolution data, the
"today" static demo screen, etc. Even if they do not seem truly usable,
on a demonstator it is not so bad. Some panel plugins are runable too
(but they seem to be pretty similar to matchbox-panel default ones).
I have not really understood however how we are supposed to start apps
from the moko UI itself (I still have to start them in a separate
xterm): is there an app for that?
That's not so easy to build them all and run them however (at least for
a newbie to embedded devices like me). Well, of course, _you_ do that
for the real hardware so...

Anyway, building the apps is just an (hopefully useful) exercise before
asking where help is needed (and possible for an outside
contributor). ;-)

Rodolphe