unity-design team mailing list archive

["S. Christian Collins" <s_chriscollins@xxxxxxxxxxx>]

On 06/09/2010 08:52 AM, Ted Gould wrote:
> It seems like you'd still need two deeply integrated theme engines
> though.  And, in the case of multiple toolkits, deeply integrated
> between them as well if this was ever going to look in anyway
> reasonable.
>
> I just don't understand why having two theme engines is better than one.
>
> 		--Ted
>    
Because it is the lesser of two evils, as made very clear IMO by Martin 
and others on this list.  Also, if done properly, it's not really a big 
deal.  A theme engine can be designed that has both a app theme 
component and a window manager component and they can talk to each 
other.  Both QtCurve and Oxygen do this quite nicely.  Notice how 
Oxygen's decoration and window contents both share the same gradient, 
shading and color.

If an app designer really wants to do their own thing with the 
decoration, etc. then they always have the option of doing what Chrome 
does and dismissing the window manager's window decoration.

The big problem is that if window management is left up to the 
applications themselves, that opens a whole pandora's box of other 
problems, which have already been expertly laid out in Martin's letter.  
Your ideas seem more idealistic than realistic IMO, and a blind eye has 
to be turned to some rather damning facts if everyone is to go ahead 
with the plan to implement CSD.

-~Chris

 		 	   		  
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3