Martin Fuchs wrote:
What is currently exactly missing from explorer-new?
As far as I see, only the main taskbar and desktop stuff is implemented.
The full file management and many additional dialogs are still missing.
For example, some time ago the VC project files have
been deleted from the
Wine
directory. So it's no more compilable as a single
subproject - only as
part of the big build system.
You can still do "make msvc?" (where ? is the version number of your MSVC
version) and rbuild will create Visual C++ Project files for all modules.
Unfortunately, they rarely work without modifications, usually you have to
switch to the configuration with MS PSDK headers and add some additional
libraries or defines.
This was also the reason why most VC project files were deleted from the
tree.
You know I would still prefer an explorer written in
C++, but it
seems most of you don't think this is the way to go.
The real problem is not the language, but the way the current Explorer is
implemented.
If we want to be compatible to Windows, we have to do things the same way
Windows does them: Windows' explorer.exe is just a simple binary, which does
most stuff through other DLL's like browseui.dll, shell32.dll, etc.
Our current Explorer implements most stuff on its own in one single EXE
file.
It became quite difficult to find and fix all those
little bugs after the
base got stable - in conjunction with the GCC/MinGW restrictions.
GCC/MinGW restrictions?
The only restriction I can think of in this way is that all code must be
compatible with our main GCC/MinGW build system, but we highly appreciate
code, which is also compatible with MSVC (and in fact this is one of the
ultimate goals).
The main problem with MSVC compatibility currently is our rbuild build
system. In its current state, its very tightened to GCC/MinGW and quite
messed up even in conjunction with these compilers.
KJK started an attempt to work against all this mess, see
http://www.reactos.org/wiki/index.php/Rbuild_sucks for more information.
Best regards,
Colin