[jharker]

Originally Posted by Iñigo

I really like jharker's proposal.
Just a minor comment: imo fullscreen should go on "page" submenu, and should be activated by default when opening new docs.

Thanks! I actually prefer fullscreen by default, but I don't think we should implement that, because it would be a significant change for most users. Also, as the Mobipocket viewer doesn't do fullscreen by default, and we don't control the Mobipocket viewer, we wouldn't have a consistent UI.

Also, I can't get the desktops idea for the iLiad.
As most of our apps/docs should be opened maximized, which are the differences between changing desktop to show other contents and minimize current app and maximize next in the apps/docs ring? why to waste bottom buttons for a not-so-useful-feature-in-iliad?

You're right, there's really no difference to the user between "different desktops" and "switch applications". And in fact, in practice I think we'd probably implement it as "switch applications" in the software.

The basic idea here is that the iLiad should be able to open more than one document at a time, and switch between them. I was under the impression that most people thought this would be an extremely useful capability...? If people don't, I'd love to know, because this OS should be good for everyone.

The solution to a lot of the "how to please everyone" problems is to simply make everything configurable. Advanced users (like us) can customize to suit their own preference, but basic users want it to "just work" and not to be surprised.

So this discussion really has two components:

• What new features should the UI have?
• What should the default configuration be?

My thinking is that we'll eventually create a detailed configuration utility, with two shortcut buttons: iLiad Classic, and All Features. Users can select one to start with and then customize from there.

My hot dreams include a tiled wm like awesome [1]... don't know if it is posible or even interesting for people.

I think a tiled wm would be interesting, although I personally don't consider it useful. It might not be too hard to implement, though. You could try compiling Awesome for the iLiad using the SDK and see how it works...? The iLiad currently uses Matchbox as a window manager, I believe, so it might be as simple as killing Matchbox and running Awesome?

Matchbox runs the toolbar, but it's a very modular program, you might be able to leave the toolbar and kill the window manager.

The ContentLister is currently designed to only allow one open program at a time. When it's rewritten to allow multiple windows, Matchbox will just have them all fullscreen and show only the top one, while you could set Awesome to open them in tiles, each 1/4 of the screen...? That might be interesting, I'd love to see it!