<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 3/20/2012 16:45, Jerome Leclanche wrote:
<blockquote
cite="mid:CAFd36Bh0s1EkLps02ZSyRPzYVkJz1bq_oE9q7r44gju0KkW1=w@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Tue, Mar 20, 2012 at 11:02 AM, Nikolay
Sivov <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:bunglehead@gmail.com">bunglehead@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div class="h5"> On 3/20/2012 12:48, Jerome Leclanche
wrote:
<blockquote type="cite">
<div>
<div>
<div>On Tue, Mar 20, 2012 at 9:43 AM, Jacek Caban
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jacek@codeweavers.com"
target="_blank">jacek@codeweavers.com</a>></span>
wrote:</div>
</div>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
GSoC is starting this year and, if we want to have
good applications, we<br>
need to update our proposals. Usually the most
attention is directed<br>
into adding new ones, while we keep obviously bad
(or just bad IMO)<br>
proposals on the page. I'm planning to remove
following project proposals:<br>
<br>
Security - implement sandboxing<br>
Theming - Implement Wine theming support<br>
NTDLL - support performance registry keys<br>
Winelib Aware Scons (or cmake)<br>
Cleanup Winemenubuilder to support generating
Application Bundles on Mac<br>
OS X<br>
Wine-based application virtualization<br>
<br>
If someone knows a reason to not remove them,
please reply.<br>
<br>
<br>
Cheers,<br>
Jacek<br>
</blockquote>
<div> </div>
</div>
<div>Why remove theming support? It would go a long
way towards excellent desktop integration.</div>
</blockquote>
</div>
</div>
I'm not sure how it helps with desktop integration actually,
you're probably referring to using host system looking alike<br>
control theme to be used by win32 application?<br>
<br>
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.<br>
<br>
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. <br>
<div class="im"><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Yes, something like that. Googling for it brought this
topic up: <a moz-do-not-send="true"
href="http://www.pclinuxos.com/forum/index.php?topic=91452.0">http://www.pclinuxos.com/forum/index.php?topic=91452.0</a></div>
<div>It's how GTK apps are themed under Qt environments; with
GTK themes cloning Qt themes. Oxygen does it really well, I'm
sure it would be possible to create an oxygen-for-windows
theme. Of course this is quite far. I think the whole thing
should be split into smaller projects involving better desktop
integration to be honest.</div>
</div>
</blockquote>
<br>
<blockquote
cite="mid:CAFd36Bh0s1EkLps02ZSyRPzYVkJz1bq_oE9q7r44gju0KkW1=w@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><br>
</div>
<div>Adding to that list: The ability to use native file pickers
over Wine's win32 ones; at least the GTK one (Qt would be in
C++ so I don't know if AJ would even consider it). With, of
course, a configure option such as
--with-file-picker=native|gtk (native by default).</div>
<div>I don't know how much work this would involve, at least
converting the data back and forth between win32 and gtk; but
I'm not even sure if it's possible to use the file pickers
without a GtkApplication. Just throwing it out there...</div>
</div>
</blockquote>
I don't think it's really possible to replace common dialogues with
something completely different, just few problems:<br>
<br>
- application expects not only particular API for that dialogues but
also certain control layout, to add its own controls for example.
It's not possible to guarantee that when you don't fully control a
dialogue;<br>
- if you want a file picker it should be based on some shell folder
internally, so you can explore you virtual c: drive and everything
else you added on top of default wine config, I'm not sure how
deeply you can interact with native file pickers to do that;<br>
- why GTK ones? or Qt ones? every toolkit will need its own
implementation to work with, and no way to guess which toolkit user
wants exactly. So it's not really an integration. <br>
<br>
<blockquote
cite="mid:CAFd36Bh0s1EkLps02ZSyRPzYVkJz1bq_oE9q7r44gju0KkW1=w@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<br clear="all">
J. Leclanche</div>
</blockquote>
<br>
</body>
</html>