Run Gnome -- On Windows
Charles Northrup (followed by many others) writes: "After a long battle with the POSIX.DLL from AT&T's U/WIN, we finally have recompiled over 4 million lines of code for the Gnome Desktop running on Windows. We had to change just under 100 lines to do this. Amazingly, the recompilation of Gnome only took 1.5 weeks. Then we had to spend the next 3 months working on the 47,000 line POSIX.DLL to get Gnome working." Here are some screenshots of this odd hybrid, pointed to by reader dimator. (Northrup invites e-mailed comments and questions, too.) And jumbolo points out the discussion about this at The GNOME Project's Gnotices site.
Look, as soon as the CYGWIN folks release XFree 4.0 for Windows (which they're about to do), Windows folks will have a high quality free X server available. From there it's a simple jump to Gnome and KDE applications on Windows. That's the migration path.
A large IT shop can't afford to simply dump Windows and move their entire userbase to Linux in one fell swoop. There's training costs to consider, application testing for internal conformity within the organization, plus security and productivity issues. If you're managing several hundred to a thousand desktops you can't afford to segment off a department just to try out a new OS, nor can you afford to just move everyone in enmasse given the potential risks involved; what if it doesn't work? You need a migration path whereby both systems can be tested and either junked in case of failure. Successful IT shops plan for failure otherwise they experience failure.
Microsoft has done a good job at killing off potential migration paths away from Windows by either buying up competitors or squashing them with anti-competitive means. See: Netscape. This is a major threat to Windows because within a year or two it will allow an IT manager the possibility to deploy GNOME and its applications on the desktop and test them without being dependent on their success. Combine this with OpenOffice and Gnome-1.4/2.0 and the Free Software community will have provided a safe migration path off of Windows. Most IT organizations are risk averse, but they're not stupid about unnecessary expense. If they can get away from the Windows tax without affecting productivity, watch the world dump Windows.
Cheers,
J. Maynard Gelinas
If you teach people Gnome applications on Windows, you can then slip the OS out from under them without complaint.
Personally, I think the requirement to have an X server is terribly flawed... but then I hate this "desktop war" too. I bet they'll eventually be able to do it without relying on Exceed. Ethereal is a Gnome app and it works o.k. on Win32 without one. (http://www.ethereal.com/)
If you're using an X server why not just run X over the network?
This may be successful with people who are interested in WMs like Litestep, Darkstep and other less known ones.
Having tried most of them, I'd say that they're usually buggy and quite beta. Usability is limited, mostly because you lose most of Windows' native functions (which are dependent on explorer.exe, the WM) and only implement a limited number of new ones.
This feature implementation is usually done by using plugins and modules, which are in theory a good thing. In practice it means that you usually get a slow manager that can crash or behave badly just because of one buggy plugin.
I've managed to use Litestep for a few days, but eventually went back to explorer.exe because features like file managing and printing were still tied to the latter, making the whole idea somewhat flawed.
I hope Gnome works as one would expect. If it does, I'll probably change for good.
Flavio
--
--
Mod up a post Rob doesn't like and you'll never mod again
I thought that their claim of how easy it was to change the gnome source to get it to work was a sure sign of a hoax until I saw the list of requirements...
An X server...
:)
- Muggins the Mad
"It is a greater offense to steal men's labor, than their clothes"
er..no.