On 3/20/2012 12:48, Jerome Leclanche wrote:

On Tue, Mar 20, 2012 at 9:43 AM, Jacek Caban <jacek@codeweavers.com> wrote:

Hi all,

GSoC is starting this year and, if we want to have good applications, we
need to update our proposals. Usually the most attention is directed
into adding new ones, while we keep obviously bad (or just bad IMO)
proposals on the page. I'm planning to remove following project proposals:

Security - implement sandboxing
Theming - Implement Wine theming support
NTDLL - support performance registry keys
Winelib Aware Scons (or cmake)
Cleanup Winemenubuilder to support generating Application Bundles on Mac
OS X
Wine-based application virtualization

If someone knows a reason to not remove them, please reply.

Cheers,
Jacek

Why remove theming support? It would go a long way towards excellent desktop integration.

I'm not sure how it helps with desktop integration actually, you're probably referring to using host system looking alike
control theme to be used by win32 application?

The problem with getting this work properly is that you need to touch loader most likely (so kernel32/ntdll), duplicate all user32 controls inside comctl32 including tests, make them register themselves when application really wants to. And of course fix uxtheme bugs. So it's quite a lot of work, and not really explored part actually.

And in my opinion this accomplishes nearly nothing, except one nice thing - some applications want new comct32 v6 controls that are formerly implemented in user32, and it's not right to fix that in user32 code now, cause native user32 doesn't provide new buttons styles for example. It's not really related to theming support, it's all about use32/comctl32v6 coexisting.

J. Leclanche

(Sorry for the double post, Jacek)