3 ms·
But they can't be used on both sides - you port your ruby program to windows and then you start using .NET libraries (and there are a ton of them, many of which
by tomjen3 16y ago
But they can't be used on both sides - you port your ruby program to windows and then you start using .NET libraries (and there are a ton of them, many of which are good). Initially it might just be a couple to make a simple GUI, then you add more and more and in the end you have to rewrite the program if you want to get away from Microsoft.
So I don't get their problem.
- rbanffy 16y agoTheir reasoning must be either that they find the native and cross-platform Ruby libraries to bee "good enough" or that rubyists that port their work to Windows do it in a way they keep the core cross-platform and the GUI thin and easily portable. It would be interesting to have a WinGlade/WPFGlade GUI library that used the GUI descriptors Glade generates to build native Windows interfaces on-the-fly. That would make life very easy for porters. It's so interesting I find it unlikely I am the first to have this idea. Got to google it. Would be even funnier to have a plugin for Visual Studio to "Save As Glade"...