[MonoDevelop] RE:Windows Forms Designer in MonoDevelop

Lluis Sanchez lluis at ximian.com
Fri Jun 2 05:03:35 EDT 2006


El dv 02 de 06 del 2006 a les 08:49 +0100, en/na Tom Potts va escriure:
> I haven't checked out stetic properly but as I understand it this is how 
> it should work:
> All 'graphical' objects should expose certain properties and methods so 
> that the designer merely has to ask the object how to display it 
> ,maximum /minimum size, C# code prototypes etc so that it can be used in 
> the designer. As far as I can tell this is how VStudio works - this 
> means you can use more or less the same designer for Windows or Web 
> forms - *if its not then theres a huge duplication of effort!*

VStudio don't use the same designer for Win forms and Web forms.
However, they share some common infrastructure. This is possible because
they are based on the same component model (System.ComponentModel.*).
Stetic is implemented in GTK#, which has its own component model, so we
can't even share that infrastructure. Why doesn't GTK# use the same
component model? that's out of the scope of this mailing list, but
summarizing: Win/Web forms were built from scratch over System.Component
model, while GTK was created even before .NET existed. 

> If stetic has used the same methods/properties as used by the 
> Windows.Forms objects then it should be possible to 'point' stetic at 
> the appropriate (Managed.Forms) library and it should be able to work 
> out how to display/edit and code for them - *if its not then theres a 
> huge duplication of effort!

The world is full of *huge duplication efforts*
(Linux/Windows, .NET/Java, GNOME/KDE, ...), and believe me, most of them
have a good reason to exist.

Lluis.




More information about the Monodevelop-list mailing list