Earlier quoted context omitted.
Probably a copy/paste bug that the author overlooked.
Which is precisely my point.
[deleted]
Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
111–120 of 187 posts
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#112This is an amazing design exercise, but the thing about Win10 that really pushes my buttons is the Control Panel/Settings conundrum. Each version it seems another feature gets added into the real settings app but still needing to open an old-themed dialog to change mouse settings of all things seems odd. It's not like mouse settings are an obscure feature. I'm not sure why a higher emphasis on cohesiveness isn't note…
In the touch-enabled world of devices Metro was envisioned for, yes, mouse settings should no longer be relevant. Meanwhile, in the real world, Windows phone died, just one colleague I know uses Windows on a tablet, yet Microsoft is still attempting to replace the control panel with an optimized-for-touch-only app. This is Apple- or Gnome-level pretentiousness: "that use case doesn't fit our brand, let's act like it'…
What about notebooks with touch screens?
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#113Earlier quoted context omitted.
As awesome as the Win2k source leak probably is from an educational standpoint, I don’t want to taint myself with illegal source code. I hope they eventually decide to open source more things, even if it was just older things.
Taint yourself with illegal source code? What does that even mean?
Look at the Google/Oracle case about their replicating of the Java API. There was significant debate over whether they made a clean room implementation or whether they just copied Oracle's code.
If you could stand up in a court room and truthfully say "I've never seen the source code I am accused of copying" it would be to your benefit.
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#114Earlier quoted context omitted.
Your standards are unfortunately warped by modern trends. Almost all popular apps are hugely bloated because the developers just don't care, the focus is on UI re-design and feature churn and the illusion of ease of development. Some counter examples (compressed installer size for convenience): 7-zip for 64-bit windows: 1.4 MiB Winamp 5.8: 7.8 MiB mpc-hc: 13.5 MiB (open source media player with many built-in codecs)…
So it’s 4x the size of mpc-hc, did the sky really fall here? I’m not on a computer but quickly scanning the repo there’s a fair number of image assets, so I don’t really know that that’s a good proxy for “bloat”
why image assets are necessary with modern application? We should be using vector images by now. And vector images are tiny.
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#115It's funny to see the gradient in the title bar, contrasting with the bland borderless-sea-of-whiteness of the rest of the UI. > FilesUwp.Package_0.5.0.0_x64.zip 54.4 MB Nearly 55MB, compressed , for something that attempts to mimic some of the functionality of the regular explorer.exe, is quite frankly ridiculous. I don't have a system to check right now, but I believe even latest Windows 10 has an explorer.exe http…
Why so harsh?
This isn't production code published by Microsoft, it's an "enthusiast's take" written by a student learning to code. Most of my college colleagues couldn't make it through FizzBuzz.
Hopefully a bright new programmer doesn't get discouraged by getting smacked down in the top comment on hacker news.
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#116Earlier quoted context omitted.
Your standards are unfortunately warped by modern trends. Almost all popular apps are hugely bloated because the developers just don't care, the focus is on UI re-design and feature churn and the illusion of ease of development. Some counter examples (compressed installer size for convenience): 7-zip for 64-bit windows: 1.4 MiB Winamp 5.8: 7.8 MiB mpc-hc: 13.5 MiB (open source media player with many built-in codecs)…
It's probably not OP's code itself but usage of UWP. The apps you mentioned here are all written in pure Win32 API. HWND, HANDLE, HPEN, HDC, anyone? Just pure C (or pure C++) and some functions... Those were the days!
Unfortunately those APIs seems to be kind of obsolete nowadays. All the nice things are with UWP. I think that WinAPI is not even hardware accelerated. That's a pity, but what can we expect, when Microsoft themselves botched WinAPI in their own products long ago.
Windows could be so better with their old Windows 2000 style, without all those design jumps around.
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#117Earlier quoted context omitted.
What you might be missing is some complex technical reason why the mouse control panel cannot be easily migrated. For example, a lot of drivers integrate their own tabs into the mouse control panel for features. The slow migration from control panel to settings is actually, in my opinion, one of the better ways Microsoft has done software development. We aren't waiting 5 years for them to migrate 20 years of settings…
I don't get people's enthusiasm for the settings app, I find control panel the faster way of achieving almost everything. Settings is slow and sometimes you circuitously end up where control panel world have sent you directly, e.g. when you want to change network adapter settings.
The lack of keyboard shortcuts and tabbing means any setting I have to change repeatedly is a bunch of hard-to-automate clicks. (Namely, plugging into a new monitor and rotating it, since the Ctrl+Alt+UpArrow doesn't work any more.)
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#118Earlier quoted context omitted.
Wine doesn't allow contributions from people that have seen the Windows source code[0]. I'm not sure of other projects with similar restrictions though. [0]: https://wiki.winehq.org/Developer_FAQ#Who_can.27t_contribute...
Yes that seems very easy to enforce. I bet 99% of Wine core developers have at least skimmed through the Windows 2000 leak at some point.
99%? Do you actually believe that?
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#119Earlier quoted context omitted.
Taint yourself with illegal source code? What does that even mean?
It means that if you read the Win2k source code, any code you write could well be challenged as a copyright infringement.
This seems like a really silly point of view: it would be similar to saying that anyone ever reading a novel would not be able to write their own.
Re: Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be
#120Earlier quoted context omitted.
In the touch-enabled world of devices Metro was envisioned for, yes, mouse settings should no longer be relevant. Meanwhile, in the real world, Windows phone died, just one colleague I know uses Windows on a tablet, yet Microsoft is still attempting to replace the control panel with an optimized-for-touch-only app. This is Apple- or Gnome-level pretentiousness: "that use case doesn't fit our brand, let's act like it'…
What about notebooks with touch screens?
They are rare compared to every other desktop/laptop computer, they still have touchpads and really why would you smear your screen with your sweaty fingers when you can avoid that?