Application talk:X

Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly? ~zonyl

Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb. More integration with webOS (see below), integration into Preware (not reliant on apt-get in the chroot), native apps (potentially faster), and perhaps a more accelerated server (lots of opportunities to make this better, including potentially glx but we'll see :D). Thanks for offering to write it up though, that is useful and should probably go up somewhere.

Packaging Proposal

I don't know the best place to put this, but I want this to be publicish so throwing it here.

xlib

Contains all the X libraries that are used. Iff the library is listed http://www.x.org/releases/X11R7.5/src/lib/ it's included.

Core

xorg-server

Contains the X server, no front-end. Depends on xlib

x11

Just a launcher script for xorg-server. Depends on xorg-server

Applications

Each application could be separated into two packages. This allows the user to have the icons they want in the launcher, but also allows them to install many applications without cluttering the pre's launcher. A good example here is 'xterm'.

app-bin

Contains the binary for the application "app", and app-specific libraries, resources, etc. No icon/front-end. Depends on xlib

app-launcher

Launcher script for the app "app". Spawns additional X server for each application. Depends on xorg-server, and app-bin.

Window Managers

Each window manager would be an application. One thought is it might not make sense to have a wm-bin package--does that really make sense? But maybe it should for consistency's sake.

Meta packages

We could introduce meta-packages for commonly installed applications/etc to save people from having to install a large number of applications manually, and just say "give me a good experience and a button to launch it!".