Post a Comment
It's not very often I have something good to say about the zillion Linux distros out there which all do the same but don't share name...
This is actually the first time in a long time a distro brings some real diversity to the field of distros.
Good for the Linux crowd I guess...
I've been using Ubuntu/Kubuntu for about 6 months, so I'm still a realtive Linux newb. I tried the live CD version of Alpha 3, and like it very much. Only beef was it didn't receognize my ethernet port. Other than it looks very promising. Hopefully they'll get a final version out soon.
I'm not sure they're following their own laws of design very strictly. If the whole point of the desktop setup is that menus are bad, and the corners of the screen are the easiest to hit, why are there still close buttons on individual application windows?
Why not have the window manager stick those at the top of the screen where they can be easier targets? (and I guess, hold the right button to hide open applications so you can get to the desktop targets?) I know there are problems with this too, but it's just an idea...
Really, I don't see how can this be a good idea: to apply a concept that works on tiny LCD's to huge desktop screens. I don't want to move all that distance untill the screen corner. I think Enlightenment approach is the best: middle click to shade app and get a glimpse of the desktop, left click on the desktop to open menu. I'm replacing movement with clicks, which is easier since my fingers are already resting near the buttons.
We do in fact maintain compatibility with the Debian repositories and our future releases will be based on the DCC Alliance's DCCRI core. In fact we have debian packages available for the mezzo desktop environment via our apt repository.
add
deb http://archive.progeny.com/symphonyos/apt/ ./
to your sources.list and install mezzo and orchestra then copy over the contents of /etc/skel to your home directory.
It is still rough at this point. One item that has been brought up on the forums is having a right click pie menu on the desktop offering the four corner menus whereever your mouse happens to be.
When I first read about SymphonyOS, I though that the design is as follows: When you click a corner menu, all open windows iconify. When you click it again or hit the close panel button, the windows restore.
But now it seems like activating a desktop panel doesn't hide the open windows. This is not the best design, given the popularity of maximized windows.
As I mentioned in a previous SymphonyOS thread here, I think that this design needs to be approached as panel viewports surrounding a central workspace viewport:
D
S W A
T
where D=documents, S=system, W=workspace, A=applications, and T=trash. Any number of mouse and keyboard navigation profiles can be selected to suit the users taste. For example, a simple edge resistance mouse-over can switch viewports, or ctrl-alt-arrows, and maybe double-clicking on a panel viewport automatically returns focus to the workspace. Since SymphonyOS is based on FVWM, this should all be extremely simple to implement.
The bottom line is that there needs to be some separation between the desktop panels and the windowing workspace. When the panels are activated, the windows should not be on top of them, and it should be really easy to activate and dismiss the panels.
However, I don't think that the UI design of this particular project (Mezzo) is very important in the scheme of things. What SymphonyOS brings to the table is Orchestra, the concept and implementation of a desktop (root window) rendered from (more or less) W3C standard web markup. This is an incredibly promising approach that I believe will be better implemented in a future desktop environment.
We hope to have keyboard shortcuts (at least for the 4 corner targets) implemented in the next release. We are also going to be working a lot on the "feel" of the interface. Things still feel a bit clunky compared to OS X, Gnome, or KDE and most of that can be solved by continuing to refine the wm configuration and changing the way it interacts with mezzo.
One change will be rather than minimizing all the windows when a target is clicked we will simply bring the mezzo window to the front, then when the menu is left we will take it back to the back. This should work a lot nicer than the current model.
"One change will be rather than minimizing all the windows when a target is clicked we will simply bring the mezzo window to the front, then when the menu is left we will take it back to the back. This should work a lot nicer than the current model."
That will certainly be a step in the right direction.
It also seems that these panels are a solution in search of a problem. The current screenshots don't really justify why anyone would need all that real estate for such a limited set of tasks and other listings. An autohiding menubar might suffice.
Mezzo is basically a proof-of-concept desktop based on Orchestra. If anything, its clunkiness should attract developers to work on a more useful interface.
"This is one of those things that looks good on paper, but pretty much just sucks out loud."
Yeah, the UI design seems to have gone off in the wrong direction. This will not be a successful offering, at least in its initial release series. I think this project is in need of a good ole fork.
I don't even know about that. I honestly don't see anything feature-wise that actually advances the desktop interface in any way. The 4-corners thing was a nice try, but it's too rigid to be practical, or like butters said, a solution searching for a problem.
The desktop menu things basically just reduplicate (poorly) directories. To demonstrate this, let's consider what a folder is: a list of items. What is an application in its most abstract form? an item. Gee, I think we have a match.
-bytecoder







