Here's what I have so far: http://www.mediafire.com/download/p28al ... r_WIP1.zipwindows.nt.win32 wrote:Well if you've actually made some progress porting the Longhorn explorer, I would be interested in seeing that. It does sound interesting, and hey, maybe we will go somewhere with that. Who knows. That does sound interesting at the very least. If you feel like you're getting somewhere with that, then by all means continue doing it. I'd love to see it, even if we don't end up using it in the long run.
It still doesn't actually work per se, but I've managed to get it to read copies of the original Longhorn DLLs in its own folder, rather than the non-4074 ones in most computers' system32 folders, and cut down all the errors relating to it not finding stuff in those 4074 DLLs for some reason...though I fear the error it now produces may be a result of how I got around the other errors D:
I'm officially at a loss as to how to progress with this. If you have any ideas, give me a shout, or try them yourself.
I'm not sure exactly how much, but I know that just about everything on 4074's Explorer Window title bars (nav buttons, breadcrumbs bar, favorites and search buttons, etc.) is added via toolbars, which can be disabled via the right-click context menu on the title bar .-.windows.nt.win32 wrote:If most of Longhorn's shell was developed through shell extensions, it could me interesting to look into porting them (or at the very least recreating them). Like I've said before, I'm all for giving everyone plenty of options, even if I won't use all of them personally.
(A toolbar is a type of shell extension, correct? .-.-. )
And I agree, drowning users in settings, options, and other ways to customize stuff is the best approach. There is no justification for removing an option unless it was only used for a now-removed feature!!