[Antartica]

Originally Posted by scotty1024

Antartica, I know you think embedding the erdm in the X11 lib means the end of porting to the iLiad but ...

The Matchbox window manager needs special care in the code.
The popup keyboard needs to be enabled or auto popped up as needed.
The frenetic busy LED needs to be turned off if launched via [SHELL] hack.

As I see it:
- For "full screen apps", there is no need to make the main window a popup. I want them to be as big as they can (hey, at home I'm using ratpoison window manager in the htpc because it does exactly that; it's nice for low resolution displays -- the TV definitely is a low resolution display, the iliad also qualifies not because the resolution but because the size...)

- The popup keyboard and the busy LED only need to be enabled once, at application startup, so this is done one at libX11 startup :-).

Originally Posted by scotty1024

The buttons need special handling in order to operate with them (pagebar, up button etc...)

- I agree that this is a problem. I would like a more general aproach, so as to map them to sane keys (I've not resolved the problem of how -- yet; perhaps with a helper application...):

up-button: keypad-up
down-button: keypad-down
select-button: enter
flipbar-advance: space
flipbar-backwards: backspace
return-to-previous-menu: escape
main-menu: (I don't know-- I would like this key to open the contents in books, and to open the menus in applications, but I think that there isn't a standard binding for that)

Originally Posted by scotty1024

And many of the apps I've worked with need a fair amount of rework to make them into unzip-n-go applications that don't need things installed to the root filesystem.

sed is your friend here :-) (after compiling the app, you can change strings of paths to another strings, if you don't change the length of said strings -- coupled with the unix permissivity of double-slashes for directories, you can use shorter path strings, too).

Originally Posted by scotty1024

Plus if there is anything you can update on the iLiad with a higher brick factor than the X11 library... I don't want to meet it.

I agree, but only if it's installed in root.

But I don't want to install the patched libX11 in the root filesystem, but in the local libs directory of each app (so the brick factor is null).

Originally Posted by scotty1024

I'm testing your abiword.

Thanks :-)

Originally Posted by scotty1024

By the way, you realize only you and I likely have ldd on our iLiad's
right?

Ups! I forgot that...

In reality ldd for elf executables is just a helper script, that calls the binary with a special environment variable set (LD_TRACE_LOADED_OBJECTS=1).

So, if you can post the output of

# LD_TRACE_LOADED_OBJECTS=1 ./AbiWord-2.4

I would very grateful.

P.S.: I attach the ldd script. It's part of the generated tools when you build the crosscompiler using crosstool (search for ldd in the build directory). I hope that it works with the shell of the iliad, but I didn't tested it...