Re: RFC: Removal of Gorm's outline view class editor

[Quentin Mathé]

Le 7 déc. 04, à 15:54, Gregory John Casamento a écrit :

> --- Quentin Mathé <gnustep-quentin@club-internet.fr> wrote:
>
> > For me it is ok, I never handle the outlet and actions directly with
> > the outline view. What I would like to see is the possibility to do a
> > search in the outline view content in the same way it is possible to 
> > do
> > within the class inspector.
>
> How do you add them?  Via the class inspector?

Yes, via the class inspector.

> > > Disadvantages:
> > >
> > > 1) People who've gotten used to the convenience of using the classes
> > > view
> > > editor will have to switch to the outline view (this is the other
> > > major reason
> > > why I haven't done this).
> >
> > Here I don't understand what you mean because it seems to be the exact
> > opposite of what you have just explained above.
>
> No, it's not.  Basically, the NeXTSTEP and older OPENSTEP versions of 
> IB
> allowed the user to edit the class in the outline view in the main 
> window of
> IB.  Gorm's main window was modeled after this.

ok. First Mac OS X versions of Interface Builder were similar, the 
class inspector was a feature added in 10.1 iirc.

> > Well in fact, I think
> > you want to remove the parent class choice in the class inspector (aka
> > class view editor, right ?), hmm I think it is not really good idea
> > because it would remove the feature we have currently which permits to
> > reset the parent class of our custom class directly in Gorm unlike
> > InterfaceBuilder.
>
> I don't agree at all with the reasoning of "it's not in IB so it 
> shouldn't be
> in Gorm."

hm, I have probably been not very clear : what I mean here is in IB we 
cannot change the parent class of our custom classes once they have 
been created, but we can do it with Gorm then I would like to have this 
feature kept in Gorm.
Moreover, you should know :-) I have never stated opinions like : "it's 
not in IB so it shouldn't be
in Gorm." , "it's not in Cocoa so it shouldn't be in GNUstep."… I can 
even say I would be perfectly happy with a Gorm version which is vastly 
different from IB , if it works well…

>  There are some other features in Gorm which IB currently doesn't
> have.   My purpose with Gorm is to give the users more features than 
> in IB
> wherever possible.   In the case of the parent class in the class 
> inspector, a
> lot of people were asking for this since it was impossible to change 
> the class
> heirarchy in Gorm once the classes were added without deleting all of 
> the
> classes and starting over.

Well, it is exactly this I want to be kept in Gorm and which I miss a 
lot in Mac OS X IB.

> Also, what some people would do instead is edit the data.classes file 
> which is
> a really really big NO NO and is one of the best ways to cause issues, 
> if it's
> not done right.

Sure.

> > Moreover what would be great is to have Gorm synchronizing not only 
> > the
> > outlets and the actions with the related class files (header and
> > implementation) but also the parent class we set (in the inspector).
>
> Synchronizing?

From the verb to synchronize or to synchronise. I hope it exists ;-).
What means in my sentence : keep in sync (keep updated) the class' 
parent class (specified in the Gorm class inspector) with the code 
written in the class files, only the class' outlets and actions are 
kept in sync currently I think; I'm talking about the outlets, the 
actions and the parent class of the custom classes we create or use in 
Gorm…

Quentin.

--
Quentin Mathé
qmathe@club-internet.fr