Thanks for your blazingly fast responses, guys!

<at> Dave: Sounds great! Limiting such functionality to developers only sounds like a fair deal.

<at> Micah: Thanks for the tip, I might give this a try. However, I once started Unity on Chrome OS (just for fun) and it ended up in a mess... Unity didn't manage the windows spawned by Chrome OS and disappeared whenever you clicked something. I think I've played around with VT2 before, but I can't remember what I ended up with. I might give this a try!

...more information here.

On Tue, May 8, 2012 at 6:30 PM, David Reveman <reveman-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> wrote:

Hi Tom,

we've been experimenting with some limited support for handling X
windows in Aura and it's possible that this will be available in some
form in the future. This would only work on Chrome OS machines in
developer mode though.

David

On May 8, 10:52 am, TomTasche <tomtasche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello,
>
> I'm currently trying to figure out a way to do the few things I still
> have to do locally (most importantly, Eclipse) on Chrome OS. One
> approach was X-Forwarding, followed by installing the applications
> natively (or in an Ubuntu chroot). Unfortunately, none of these
> approaches helped me achieve a usable solution. The problem I'm facing
> is that those "foreign" windows (so, windows spawned by applications
> other than Chrome) aren't being handled by the window manager Aura
> Shell and therefore are hardly to impossible to use.
>
> I've taken a look at the Aura design documents and completely
> understand that it's purpose is to *get rid of* dependencies like Gtk,
> but I don't understand why this means the window manager kind of
> "ignores" other windows.
>
> Would anyone be so kind and shed some light on this for me?
>
> Have a great day
> Tom