[Mono-winforms-list] Theming in MWF
Pedro Martínez Juliá
pedromj at gmail.com
Fri Jul 29 08:20:05 EDT 2005
But we have a theming implementation in MWF. If we want to be 100%
compatible with MS.NET, we need to get out that theming implementation
and put it as an optional patch...
I think that the best solution to have themes is to provide a high level
definition for controls and then provide few implementations (gtk#,
wx.net, system.windows.forms, and maybe system.web). Like glade/xaml/xul
are doing but with more than one target toolkit.
El vie, 29-07-2005 a las 12:44 +0200, Kornél Pál escribió:
> MS.NET has no theming support. Theming means that it would be able to draw
> contorls and/or windows using custom functions. There is no such support in
> It has an Application.EnableVisualStyles method that enables using Visual
> Styles. Visual Styles are provided by Windows not by MS.NET.
> All that Application.EnableVisualStyles does is that it loads comctl32.dll
> version 188.8.131.52 using a manifest file through Windows side-by-side assembly
> support and the initializes comctl32.dll.
> By default controls are drawn by MS.NET so you have to use FlatStyle.System
> to let Windows draw the controls using visual styles.
> For more information see:
> Visual Styles:
> Side-by-side Assemblies:
> Mono draws contorls itself (just like MS.NET) that provides identical
> appearance across all platforms.
> Enabling custom themes is a good idea but it cannot be done in MWF because
> it has to be compatible with MS.NET implementations.
> ----- Original Message -----
> From: "Pedro Martínez Juliá" <pedromj at gmail.com>
> To: "Mono Winforms" <mono-winforms-list at ximian.com>
> Sent: Friday, July 29, 2005 12:31 PM
> Subject: [Mono-winforms-list] Theming in MWF
> > Hi,
> > I've seen the implementation of themes in MWF and I'm not agree at all
> > of having theming in this stage of the development. I know that MS.NET
> > has themes but I think that themes are implemented in Windows because I
> > didn't see anything related in MSDN documentation.
> > I saw that Theme.cs has a lot of painting logic and I think it shouldn't
> > be there. For example, DataGridPaintRows iterates the rows of a datagrid
> > to paint each one. I think that it should be in DataGrid and not in the
> > theme class.
> > The problems I see in this issue is that I can implement a Theme that
> > changes the view of any control and in the other hand, this theming
> > engine doesn't allow a user to easily download and install a theme.
> > At the end, we have only Win32Classic theme maintained and it adds one
> > level to the indirection at the time to paint any control.
> > For all of this I think we can redesign now the theming. It's only an
> > idea.
> > Regards,
> > Pedro
> > --
> > Pedro Martínez Juliá
> > \ pedromj at gmail.com
> > )| Jabber: petrux at jabber.org
> > / MSN Messenger: yoros at wanadoo.es
> > Socio HispaLinux #311
> > Página web: http://pedromj.dyndns.org
> > Usuario Linux #275438 - http://counter.li.org
> > _______________________________________________
> > Mono-winforms-list maillist - Mono-winforms-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-winforms-list
Pedro Martínez Juliá
\ pedromj at gmail.com
)| Jabber: petrux at jabber.org
/ MSN Messenger: yoros at wanadoo.es
Socio HispaLinux #311
Página web: http://pedromj.dyndns.org
Usuario Linux #275438 - http://counter.li.org
More information about the Mono-winforms-list