few questions about new class & convert to sibling

Hi,
and forgive me for asking probably obvious:

-what is the motivation for extra dialog when creating a new class (choose
subclass)?
-what is refactorings-convert to sibling supposed to do? I whatever existing
class name I enter in dialog I get error?

rush

Davorin

You wrote in message news:[hidden email]...
> Hi,
> and forgive me for asking probably obvious:
>
> -what is the motivation for extra dialog when creating a new class (choose
> subclass)?

It allows you to insert a new class in the middle of the hierarchy in one
operation. For example you have a hierarchy with superclass A and subclasses
B, C and D. You realise that B, and C have much in common, and so you decide
to insert an abstract parent for them both, E. Using the choose subclass
dialog one can insert E between A and its existing subclasses B and C.

Ideally there should be a custom dialog for the 'Create Subclass' command
that allows one to specify all of this without multiple dialogs, but we have
not had time so far.

> -what is refactorings-convert to sibling supposed to do? I whatever
existing
> class name I enter in dialog I get error?

http://wiki.cs.uiuc.edu/RefactoringBrowser/Children+to+Sibling

Regards

Blair

"Blair McGlashan" <[hidden email]> wrote in message
news:[hidden email]...
> > -what is refactorings-convert to sibling supposed to do? I whatever
> existing
> > class name I enter in dialog I get error?
>
> http://wiki.cs.uiuc.edu/RefactoringBrowser/Children+to+Sibling

thanks!

rush

Hi Blair,

> > -what is the motivation for extra dialog when creating a new class
(choose
> > subclass)?
>
> It allows you to insert a new class in the middle of the hierarchy in one
> operation. For example you have a hierarchy with superclass A and
subclasses
> B, C and D. You realise that B, and C have much in common, and so you
decide
> to insert an abstract parent for them both, E. Using the choose subclass
> dialog one can insert E between A and its existing subclasses B and C.
>
> Ideally there should be a custom dialog for the 'Create Subclass' command
> that allows one to specify all of this without multiple dialogs, but we
have
> not had time so far.

I'd like to second your custom dialog idea.  My concern is that the required
prompters will be distracting during refactoring sessions.  It's great to
have the new capabilities, but, one should be able to pass on them too.

Have a good one,

Bill


--
Wilhelm K. Schwab, Ph.D.
[hidden email]