[MonoDevelop] Larger set of stetic patches

[Lluis Sanchez]

El dv 30 de 06 del 2006 a les 15:02 +0100, en/na Michael Hutchinson va
escriure:
> On 6/30/06, Rafael Teixeira <monoman at gmail.com> wrote:
> > On 6/29/06, Lluis Sanchez <lluis at ximian.com> wrote:
> > >       * When building a dll which implements both widgets and windows
> > >         that contain instances of those widgets. The problem in this
> > >         case is that we need to have the widget description before
> > >         compiling, but we don't have a dll to reflect.
> >
> > Yes, that is why in VS.NET normally you separate components into
> > topologically-lower libraries and the windows/forms that use them in
> > other libraries or the main exe. After design is finished, some
> > reusable windows may be rafactored (moved) to the lower libraries, as
> > it is just a design-time issue. Not the cleanest thing but
> > nevertheless usable.
> 
> Surely the code parsing services in MD could be used?

We can't, because a project may need to be built in a system where MD
ins not installed. Stetic would still be needed, but it is a much
smaller dependency.

> 
> Also, you can compile the widgets into tempory assemblies and use
> those for the design surface. Or even just use the most recent build.
> I think that's what VS.NET must do for WinForms controls.
> 
> > Yes, we shouldn't mix things. I vote for reflection all the way but I
> > will defer it to the time I have some working code to show...
> 
> I vote for reflection too; it's much cleaner. Also, I have written
> ToolboxItem-consuming code for AspNetEdit, because that's the standard
> .NET toolbox way.
>