[MonoDevelop] class wizard

[olivier dufour]

Ok, I do not think to CodeDOM, I think we will use binding and put in
interface of binding the function we need.
CodeDOM is more elegant. fine for me ;)

For multi-page, I am ok. I have test and there are too much features to make
a readable form. So best is cut in more than one forms.

2008/2/4, Michael Hutchinson <m.j.hutchinson at gmail.com>:
>
> On Feb 4, 2008 2:46 AM, olivier dufour <olivier.duff at gmail.com> wrote:
> > Wow,
> >
> >  thanks for all these feedback ;)
> >
> >  So, first issue will be modifiers each language have his own keywords
> and I
> > do not know if all language support all modifiers of csharp (I do not
> think
> > so). So, I will have to do a function in each language binding to get
> the
> > list of grouped modifier for radio button (public,private,protected,
> > internal) and single modifier for checkbox ( static,sealed, partial,
> > abstract, unsafe).
> >  But we have some rules here between single modifiers.(abstract and
> sealed
> > for example)
> > And maybe some language have more than one group of modifier.
>
> Well, a lot of these things are fundamental to .NET. if you generate
> the class using CodeDOM, the language's code generator should sort
> things out.
>
> >  And if we do what is my next question, we will have issue because some
> > modifier is not allowed with structure or interface (static for
> example). I
> > do not think it is a good idea... because will add a lot of issue and if
> we
> > add too much thing it will become too complexe.
> >
> >  Do we need something to say class, structure or interface or we only
> > provide something for class?
>
> Is this a struct and interface designer too? I guess there's no reason
> why it couldn't be a struct designer, but I think that there is little
> overlap with interfaces.
>
> >  So language binding class willl have GetModifiers and CheckModifier
> which
> > will avoid to break modifier linked rules.
>
> I'm pretty sure CodeDOM allows you to query for supported features.
>
> >
> >  Else I can limit the list of modifier to the more common but it lead to
> > another question which one?....
> >
> >  For auto-complete box great idea.
> >
> >  A treeview seems to be more adapted to what we need for member to be
> > overriden.
> >
> >  For the multi page, I am not sure... I am OK that this can be usefull
> > outside but not sure because I really prefer to have all screen. Anyway,
> I
> > will see if all can be in the form else I will see if we do 4 windows
> with a
> > button next/previous or if I do tabs (what do you prefer).
>
>
> Well, my main point with the multi-page is that many of the steps can
> be re-used independently of the class wizard.
>
>
> --
> Michael Hutchinson
> http://mjhutchinson.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20080205/9d687606/attachment.html