On Mon, 24 Oct 2005 23:53:38 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote:
> On Mon, 24 Oct 2005 06:19:37 +0000 Felix Breuer <[EMAIL PROTECTED]> babbled: > > So, why are modules part of the desktop? > > Why was this design choice made? > > > > One alternative I could think of is to make modules part of a special > > module layer that hovers _above_ all windows and which can be toggled > > on mouse click or which is faded in when the mouse approaches the > > screen border. > > > > I am aware that this would be a problem transparency-wise, but I, > > personally, could live with shaped modules until X's damage and > > composite extensions are ready for practical use. > > the reason being that in time x will allow us to have the alpha we want AND > modules ANd not change design majorly. this is a limitation of x - we give up > one thing to get another. I am not sure I understand you correctly. Do you mean that, once X provides the required functionality, you are planning to implement something like a "modules in surface layer" feature? If yes, what limitations of X need to be removed for that to happen? Thanks, Felix ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
