Yes and no. The framework is in place, but the tools are somewhat lacking. Some people would argue that building Gtk# applications in Glade is just as easy as the Visual Studio Forms Designer.
Personally, I disagree. Visual Studio is still a phenomenal IDE, and its GUI tools are some of the best on the market. But I think as we see Mono stabilize and mature past 1.0, the GUI tools for Gtk#, ASP.net, and the new Managed.Windows.Forms implemenation will be quite impressive.
(Disclaimer: This isn't a knock at Glade. Glade is good at what it does, but with the advent of Mono it's time for a replacement.)
Our intention with UserLinux is to work closely with the Debian team and improve on the current release cycle. Hopefully the Debian stable release cycle can be shortened (so users aren't left with 2.5 year old packages) without sacrificing the unmatched quality debian-stable has always had.
Bruce has mentioned on the list that we'll cook our own packages and tweak Debian where the need presents itself. However, we'll be following debian-stable as closely as possible (Sarge).
With regard to people recommending you use debian-testing: `testing' is currently preparing to become `stable' on Sept. 15th. Thus, this recommendation is less "use testing" than it is "use the up-and-coming stable.":)
Bruce has already answered this many times here, but I'll reiterate: UserLinux is Debian.
The differences between UserLinux and Debian are slight: branding, configuration tweaking, and temporary fixes where necessary.
The value of UserLinux does not come from technical achievements - everything we have, Debian has (and vice-versa). UserLinux selects a supportable subset of Debian and provides it to the customer in a neat package which any number of ISVs around the world can support.
Maybe if everyone decided to work together, rather than all start their own distros, the Linux platform would be in better shape than it is on the desktop.
So, why will UserLinux not be just another one of the pack?
You just answered your own question. UserLinux is already in the "pack." Debian has been around for 10 years - working together is what we're trying to do.
There are a number of reasons why System.Windows.Forms (SWF) isn't fully-implemented yet: First, he mono SWF implementation is based off of Wine, and wine is a bit of a moving target. Second, you will hear any number of mono developers -miguel included- declare SWF as a "terrible API", which it is.
Just recently I switched to using GTK# for all my.NET applications at work. It's perfectly cross-platform, and building Glade's XML files (in Linux or Windows) is a joy compared to building SWF interfaces. GTK# rendered SWF totally unnecessary in a couple days of use.
But, like serialization, SWF is on its way. However, if you're moving from.NET to mono, you'll probably prefer the SWF->GTK bindings which are being developed by the community.
Slashdot Mirror
Cobol and .NET, together at last. - Your prayers have been answered! ;)
Yes and no. The framework is in place, but the tools are somewhat lacking. Some people would argue that building Gtk# applications in Glade is just as easy as the Visual Studio Forms Designer.
Personally, I disagree. Visual Studio is still a phenomenal IDE, and its GUI tools are some of the best on the market. But I think as we see Mono stabilize and mature past 1.0, the GUI tools for Gtk#, ASP.net, and the new Managed.Windows.Forms implemenation will be quite impressive.
(Disclaimer: This isn't a knock at Glade. Glade is good at what it does, but with the advent of Mono it's time for a replacement.)
Our intention with UserLinux is to work closely with the Debian team and improve on the current release cycle. Hopefully the Debian stable release cycle can be shortened (so users aren't left with 2.5 year old packages) without sacrificing the unmatched quality debian-stable has always had.
:)
Bruce has mentioned on the list that we'll cook our own packages and tweak Debian where the need presents itself. However, we'll be following debian-stable as closely as possible (Sarge).
With regard to people recommending you use debian-testing: `testing' is currently preparing to become `stable' on Sept. 15th. Thus, this recommendation is less "use testing" than it is "use the up-and-coming stable."
Bruce has already answered this many times here, but I'll reiterate: UserLinux is Debian.
The differences between UserLinux and Debian are slight: branding, configuration tweaking, and temporary fixes where necessary.
The value of UserLinux does not come from technical achievements - everything we have, Debian has (and vice-versa). UserLinux selects a supportable subset of Debian and provides it to the customer in a neat package which any number of ISVs around the world can support.
Maybe if everyone decided to work together, rather than all start their own distros, the Linux platform would be in better shape than it is on the desktop.
So, why will UserLinux not be just another one of the pack?
You just answered your own question. UserLinux is already in the "pack." Debian has been around for 10 years - working together is what we're trying to do.
There are a number of reasons why System.Windows.Forms (SWF) isn't fully-implemented yet: First, he mono SWF implementation is based off of Wine, and wine is a bit of a moving target. Second, you will hear any number of mono developers -miguel included- declare SWF as a "terrible API", which it is.
.NET applications at work. It's perfectly cross-platform, and building Glade's XML files (in Linux or Windows) is a joy compared to building SWF interfaces. GTK# rendered SWF totally unnecessary in a couple days of use.
.NET to mono, you'll probably prefer the SWF->GTK bindings which are being developed by the community.
Just recently I switched to using GTK# for all my
But, like serialization, SWF is on its way. However, if you're moving from