[MonoDevelop] Version Control UI

Michael Hutchinson m.j.hutchinson at gmail.com
Tue Aug 17 16:40:49 EDT 2010

On Tue, Aug 17, 2010 at 2:01 PM, Mike Krüger <mkrueger at novell.com> wrote:
> Your grouping is the right grouping. All other files than the
> MainWindow.cs are only there for one reason:
> Make the life of the forms designer easier.
> - The forms designers started out parsing the InitializeComponents ()
> method from the forms class. I don't think that it's good to confront
> the user with this technical complexity (and you got the point - aspx
> etc. is for direct editing where gtkx files are only helpers for the
> forms designer no user should ever touch directly).
> IMHO you did the right thing - gtkx files are monodevelop only - it
> doesn't make a reason to build the project this way (try to think what
> happens when the project is opened in vs.net or #develop).
> I think the designer/source view is good for the gtk# designer. All IDEs
> (expect VS.NET - maybe a technical limitation in their IDE?) do a split
> system for forms.

VS does a split view for Winforms but not for anything else, so I very
much doubt it's a technical limitation. Winforms is essentially a
legacy designer - it used to store the GUI definition in a folded
method *in* the code file, so the combined view actually made sense
for that.

The more modern GUI editors in VS -- XAML, ASP.NET etc -- all have a
concept of "codebehind" being distinct from the GUI definition, even
though they also generate designer code. IMO the grouping works very
well for these, and I don't see why it wouldn't work just as well for
stetic, since it's much more akin to what we do. See also Xcode and
xib files.

Michael Hutchinson

More information about the Monodevelop-list mailing list