tags:

views:

114

answers:

5

Suppose I wanted to create an open source Windows Forms project written in .NET. I am pretty well-established in my opinion that the System.Windows.Forms suck big time. I love Developer Express' controls, but they cost an arm and a leg and I don't see how their per-developer licensing would make it possible to use them on an open source project.

What options are there for third-party Windows Forms controls to be used in an open source project? I don't care whether the controls themselves are open source - just that they have good functionality and look good.

A: 

any 3rd party controls are for example GTK and QT. Don't know the legal aspect using it in open source software

PoweRoy
Neither of those tools work smoothly with .NET or at all with Visual Studio.
Josh Kodroff
GTK and QT have a different approach yes. Mostly designing the form outside the IDE. Both have .NET support, GTK# and QT# for C#. If you want smooth intergration then you should look at something else
PoweRoy
+2  A: 

I would recommend you to take a look at the following component vendors: devcomponents, krypton toolkit, purecomponents, viblend, divelement. All of these have a lot of built-in features and they are relatively cheap.

Jonas
Cheap's not going to work for an open source project. I want to have contributions from the general public who are likely not going to be apt to contribute if there's a dependency on a control they need to pay for.
Josh Kodroff
Krypton Toolkit is very good and looks very professional.
Laurent Etiemble
A: 

DockPanel Suite is pretty good for building nice dockable UI

Thomas Levesque
A: 

IMO the standard Winforms controls are good enough for creating standard-looking Windows applications. But, if that's not enough for you, have you considered switching to WPF?

Sorin Comanescu
A: 

If you want an open source project, you will need open source controls. You should also make certain your application builds under open source tools, such as SharpDevelop. Yes, you will give up some features (and depending on what it is, maybe a lot of features) but creating open source often means sacrificing convenience for openness.

Your options are, build your own controls that do what you want, use the standard controls, or use the rather slim set of open source controls already out there. There is really no way around that, because any open source project won't be open source if it requires proprietary controls.

Mystere Man