crouton in a Chromium OS window (xiwi)

Basic concepts

xiwi (X11 in a Window) works by creating a window in Chrome and channeling a virtual X11 framebuffer over to it. While crouton transfers the framebuffer relatively efficiently, there's no GPU acceleration and a fair bit of overhead, so don't expect games or graphics-heavy desktop environments to perform well. For basic productivity use it works great, though.

Regardless of how you intend to use xiwi (full desktop environment vs. single-app), you need to add it to your chroot.

1. Install the xiwi target into your chroot, either via update (-u -t xiwi) or via initial install (-t xiwi,xfce). If you only intend to use the single-app mode, you can avoid installing a desktop environment entirely (-t xiwi).
2. Ensure you have the Chromium OS extension installed.

If you want to temporarily launch using native Xorg, add the -X parameter to your enter- or start* command (e.g.: sudo startxfce4 -X xorg).

You can set the default method back to xorg by updating with the xorg target explicitly, after which you can still use xiwi via -X (e.g.: sudo startxfce4 -X xiwi).

Hit the full screen (above the 5 key) or switch window (above the 6 key) to get out of full-screen crouton.

If you close the window, xiwi is still running. You can get back to your windows via the extension dropdown.

Ctrl+Alt+Shift+Back/Forward still works to cycle chroots, although it makes less sense here since Chromium OS's window management works fine too.

You can have xiwi chroots and xorg choots running simultaneously. Usually it's not a good idea to run two instances of a desktop environment in the same chroot at the same time, but in most cases it's fine to run multiple xiwi single-application instances even alongside a desktop environment inside the same chroot.

Running full desktops in a window

Once you have xiwi set up, launching your desktop is the same as if you were using xorg (i.e., sudo startxfce4). An ongoing discussion is here.

Running individual applications in windows

With xiwi installed, you do not need a desktop environment. You can launch apps on an individual basis in a Chromium OS window.

1. Enter your chroot to get a command line: sudo enter-chroot
2. Launch your app via the xiwi command: xiwi gimp
3. You can combine those into a single command sudo enter-chroot xiwi gimp.
4. You can silence output and run the command in the background via sudo enter-chroot -b xiwi gimp.

If your application forks and quits, xiwi may get confused and quit as well (you'll get an error/quit when the window launches). Search your application's documentation for a parameter that prevents forking (oftentimes it's -f). If you can't find one, you can pass -f to xiwi itself (e.g., xiwi -f gvim), and xiwi will not close unless there are no applications visible and you close the Chromium OS window. It's always better to use the appropriate options on the application's side of things if possible, though (xiwi gvim -f in this example).

You can pass parameters to your application like normal, but remember that if you use the combined form (e.g., sudo enter-chroot xiwi gimp), your current directory is ignored. So even if you're in your Downloads folder and want to edit img.jpg, sudo enter-chroot -b xiwi gimp ~/Downloads/img.jpg is necessary.

Single-window applications work better than multi-window applications, but if you end up with multiple windows, you can switch between them via either the tabs at the top, or via the Ctrl+Alt+Tab and Ctrl+Alt+Shift+Tab keyboard shortcuts. Ctrl+Alt+Shift+Escape acts the same as the close button on most windows. If a pop-up window appears in a weird place, you can either drag-move it, or Alt+drag to resize it.

If you launch applications via aliases, the xiwi command will not know about them. You can add the following snippet to your .bashrc/.zshrc to handle basic aliases:

# Wrap xiwi so that aliases work
xiwi() {
    local cmd="`alias "$1" 2>/dev/null`"
    if [ -z "$cmd" ]; then
        /usr/local/bin/xiwi "$@"
        return
    fi
    eval "cmd=${cmd#*=}"
    shift
    for param in "$@"; do
        cmd="$cmd '`echo -n "$param" | sed "s/'/'\\\\\\''/g"`'"
    done
    eval "/usr/local/bin/xiwi env $cmd"
}