suggestion: moving wine dlls

[Timo Kreuzer]

I have a suggestion:
Move all wine shared dlls to dll/wine or dll/3rdparty/wine, only kepping
our own dlls (gdi32, user32, kernel32, syssetup, newdev, console, hid,
mmdrv, ...) in dll/win32.
Reason is, we just lost a few earlier commited translation of wine dlls
with the latest winesyncs.
With this we would make sure everone would directly see that the
component is synched with wine and should not be touched. Another point
is that it's quite annoying to have >100 folders under the win32 folder
that expand in the file browser, when you browse to one of our dlls.

Greetings,
Timo

[James Tabor]

Timo Kreuzer wrote:
>   I have a suggestion:
>  Move all wine shared dlls to dll/wine or dll/3rdparty/wine, only kepping
>  our own dlls (gdi32, user32, kernel32, syssetup, newdev, console, hid,
>  mmdrv, ...) in dll/win32.
>  Reason is, we just lost a few earlier commited translation of wine dlls
>  with the latest winesyncs.
>  With this we would make sure everone would directly see that the
>  component is synched with wine and should not be touched. Another point
>  is that it's quite annoying to have >100 folders under the win32 folder
>  that expand in the file browser, when you browse to one of our dlls.
>  
>  Greetings,
>  Timo
>   
Yes,, that could work.

Once in a long time ago,,,, we had a wine tree and ReactOS tree. The wine
tree had all the wine imports and the ReactOS tree had the Ros diff and
extras. The best thing Casper ever did for ReactOS!

It's a good idea,
James