[Mono-winforms-list] Dialog implementation and look and feel

Aleksandar Dezelin dezelin32@fastmail.fm
Tue, 21 Dec 2004 09:46:07 +0100

Peter Dennis Bartok wrote:

> 2) The look and feel is determined by two things:
>     First, the control provides certain properties, the look and feel must 
> allow for all properties to be usable by the code.
>     Second, MWF uses a themeing concept. This means that the design of the 
> dialog must allow for the actual layout code to be in the theme driver. All 
> implementations must implement the .Net look by default (goes into 
> ThemeWin32Classic). Other theme modules may be added in the future, maybe 
> the Gtk one will call down and invoke the actual Gtk dialogs. However, for 
> the default implementation, this is not acceptable.

Could we just expose underlaying dialog MWF controls as internal and use 
  , for example, 'void LayoutFontDialog(FontDialog fontDialog)' method 
in the themeing classes? Or there is a better approach?

> 3) The dialogs (obviously) must use the existing controls to implement their 
> functionality, unless no control exists that provides the required 
> functionality. This means that if there's a button on the dialog, use a 
> button control and do not write your own button code into the dialog.
> Hope this helps a bit.
> Cheers,
>   Peter

What to do with 'My Network' button? I think that ignoring it and 
waiting for something like Mono.Net.Samba is best for now.


Aleksandar Dezelin

Linux is like wigwham - no windows, no gates, and apache inside...