Metro should have been made from the start to inter-operate fully (with some caveats, like clipboard behavior) with the regular desktop UI and "legacy" programs, by way of user-adjustable window size (which are only just getting added--nice divisible screen-size chunks would be fine),
But only in half from what has been revealed. I would like a division like a real window, in fours that can be adjusted.
separating the visible monitor space(s) into Metro (tiling) and desktop (overlapping WIMP)
At first I thought you meant overlapping traditional windows OVER Modern ones and have Modern ones act more like small windows. Or it is that idea and not my other interpretation of a separate display pane of overlapping traditional windows.
Because I feel overlapping (much like my real desk and workbench) hides things, feels more cluttered, and it is a mess to deal with in shuffling used and unused elements. And forcing traditionally windowed items to now take up possibly more space than they were initially designed would be awkward.
Traditional windowed programs that were larger than the intended pane won't fit, resulting in my solution of having that monitor section pane to be able to act like Magnifier to view and pan, with touch. Which I hope gets put in to compensate, allowing for an infinite desktop potentially filled with all the buffet of overlapping windows one ever needs.
slices (dynamically, by resizing the Metro apps, with memory in between uses), and having a distinct compatibility layer (no incestuous code, and WinRT wouldn't get it).
I thought Modern applications already have a inactive mode to reduce memory use when not active and being on display, and also still allow the quick recovery once put active by switching to them from the Modern taskbar.
The arbitrary resizing from the start would have also made responsive UI design mandatory to get and keep users, too, for any and all metro app devs :twisted:.
On a desktop, it is easier to precisely move and manage small and overlapping windows because their titlebar size isn't finicky for a mouse/trackball/pen. But since Windows 8 was designed for touch as well, having to deal with managing windows gets harder.
Sure it will allow for adoption of Modern applications on the desktop alto better, and bringing back the whole Charms feel of Vista and 7. But having used Windows 8 as intended (on a touchscreen) the desktop is more awkward. But I am still happy that there are these options side by side, both Modern and desktop traditional, I can still have options to plug in my trackball (I stopped using desktop Opera in favor for touch Modern IE - miss that Opera link ability). It is a compromise that I feel was implemented to quickly get into an already established market so Microsoft wouldn't be more far behind.
While it was being developed, the above would not have been hard to do, but if the APIs don't cooperate, it may be difficult or impossible after-the-fact. Something like the above would have made the new UI, and programs associated with it, pure added value:
As in from what I am possibly understanding, Modern applications, as the one that is the pure added value? I feel that Windows 8 draws traditional and Modern as both as effective to an acceptable degree (can be better) but to say Modern applications are the tail end? There is a reason I brought up my Opera example.
if you could make use of them as touch/remote apps, great; if not, you still wouldn't have to worry about trying to get them out of your way, as the only difference would be getting used to tiling windows (easy enough, especially with the applications being made for it).
Give the option for 'touch pointer' for the native desktop environment (and the pane it occupies) and this brings me to accept any desktop improvements to the precision pointing input.
Given the importance of compatibility to MS' user base, especially their business customers, it's mind-boggling to me that they implemented it the way that they did.
It did felt a bit off by a tiny margin on the purely traditional desktop hardware. (I got in on the $15 deal with a machine I built right at the near beginning date of acceptance of machines that 'can' upgrade.) I can see all the start screen complaints - and as I iterated, didn't faze me much due to using a trackball.
But what else could they done to now satisfy a now 80% happy (and in the past - prospective tablet PC) user? The pen was the biggest draw initially, but everything else I used, was clear. However, do note some suggestions I posted earlier in the thread as the reasons why I am not completely satisfied.
Add to that removing subpixel rendering, instead of making it better, and not allowing WinRT on domains ("What would be a good way to get back some phone or tablet marketshare?"/"How about integrate with AD, like real Windows, for our corporate and government customers?"/"You know, I'd rather they just use iPads, instead, and get used to horizontal integration.").
I vouch for the Pro in work environments. You get what you pay for. Cheap clients that have a separate support and an additional attack vector in terms of security or an initial cost of clients upfront to a support cost that won't be additional.