Slashdot Mirror
MS Vista Look and Feel To Go Cross-Platform
Robert writes "As part of the announcement of the next generation look and feel for Windows Vista,
Microsoft said that it will make a subset of the new presentation layer available for
other platforms. 'Windows Presentation Foundation', the look and feel which provides the rich front end for
Vista, will also eventually be available in compact form for other platforms such as the
Apple Macintosh, older
versions of Windows, and smart devices such as phones or PDAs."
I saw the announcement and a demo on the PDC (well, live through the internet that is). Anyway, the idea of WPF/E (Windows Presentation Foundation/Everywhere) is to be able to deliver apps using the WPF (codenamed "Avalon") API using JavaScript. So any OS capable running JS will be able to run those apps... whether it's a smartphone, MAC OS X or Linux...
The article makes clear that this is vaporware. Microsoft haven't got further than "scoping this out" and in any case it won't be part of the first Vista release. Besides, it could be a few years before someone works out how to stuff a 6800GT into a Nokia cellphone.
... the borg is stirring ... the mere threat of Vistarizing your watch, phone, toaster, camera, alarm clock, yay, the great globe itself, with dinky beeping sounds, natty symbols and rich interactive content from doubleclick.net ... I surrender, master.
Unless
Las qué passoun
tournoun pas maï
MS tried this before on the mac.
It was a dismal failure
MS Word 6.x on the Macintosh worked, but was heavily bloated, slow, and did not at all fit in with the way the mac worked.
Why? It used a subset of the Windows GUI. It didn't use Macintosh gui calls and was not only weighed down by using an untested (compared to windows gui elements on windows, which has the benefit of being used by hundreds of apps and debugged over time) gui, but worked opposite to how good macintosh apps should work.
It was regarded as a failure even at the time and many people stuck with Word 5.1
Yes, I'm talking about the interface stuff from Mozilla. XUL.
If you want to write an application that runs on Windows, Linux, *BSD and Mac OS X, that utilises a common interface across all these platforms, and if you want to write it today, then use XUL.
We should all bow down to Microsoft's reinvention of the wheel.
Why can't I add anotherpanel, along the left side of my screen. With the number of quicklaunch and tray Icon's it would be nice to have those easily accesible, without being crowded and small at the bottom, half of them hidden becuase they don't have the room.
1) Load up your quick launch toolbar with shortcuts
2) Right click on the taskbar and make sure "Lock the Taskbar" is turned off
3) Click on the quick launch toolbar's handle, drag it to the side of the screen you prefer, and release.
4) Stare in amazement at a feature you didn't know about but has been present since Windows 98
Also, once it's docked, you can also set it to autohide on the right click menu
Microsoft "targeted" Mac OS before. Sometime in the mid-90's you could use Microsoft's development tools to build cross-platform (Win/MacOS) applications. In theory.
The reality was that the barrier to entry was very high (IIRC, you needed a specially-configured version of NT to host the tools), and you could use only a subset of the Windows APIs (sound familiar?). AFAIK, Microsoft didn't even use them to build anything significant; my recollection is that the then-current version of Office was not built with them.
So what was the point? To the extent that anybody thought about doing cross-platform development, they could be answered with the line that "if we use Microsoft's tools, we'll be able to cross-develop if and when we want to." One more reason to consider using not getting locked into Microsoft's tooling was apparently answered.
Also, the "subset" qualification meant that you could make a choice: be cross-platform, or exploit every platform feature to build the best possible application. As soon as you were sucked into the latter alternative, you were locked out of the other platform(s). (This is the approach Microsoft took with their flavor of Java.)
Finally, the non-Windows implementations of these cross-platform application were marginal at best in terms of platform guidelines on the Mac. So, if you were to go ahead and deliver on the cross-platform tools, you were guaranteed a luke-warm reception at best from the Mac community, which in turn would probably make you think twice about developing for the platform again.
That attempt to go "cross-platform" by Microsoft was so choked with booby traps that it never got off the ground. I expect the same result here, even allowing for adaptations to lessons learned.
1. Create folder
2. Stuff links into folder
3. Right click start bar, left click "Tool bars", "New tool bar"
4. Right click start bar and make sure "Lock tool bar" is not checked
5. Left click and drag new toolbar from Start menu to the left hand side of the screen. You could even float it if you like.
HTH.
your present monitor will NOT work with Vista.
I haven't been following Vista too closely, but I don't recall anything about monitors not working with Vista. Are you referring to the same thing that this ars technica article (new window) is discussing? In that case it's not that the monitors won't work with Vista at all, it's that they can't display legally obtained HD content in full HD on present displays. However, if I'm understanding this right, it looks like it will only to be crippled over a digital pipeline like DVI. But that's beside the point.
Unless I'm mistaken (and feel free to show me evidence that I am) your present display will work with Vista... but just might not show HD content in full HD.
Slashdot: where repeating an article in a post is "+5 Insightful"