Newsgroups: comp.soft-sys.powerbuilder,comp.object,comp.lang.c++,comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!hookup!news.Direct.CA!sunserver.insinc.net!cuugnet!wagnerc
From: wagnerc@cuug.ab.ca (Craig Wagner)
Subject: Re: what is an object?
Message-ID: <D7GMDz.5Gx@cuug.ab.ca>
Followup-To: comp.soft-sys.powerbuilder,comp.object,comp.lang.c++,comp.lang.smalltalk
Organization: Calgary UNIX User's Group
X-Newsreader: TIN [version 1.2 PL2]
References: <3mu025$e5o@tst.hk.super.net> <3mudap$o0h@wendy.ibmpcug.co.uk> <D79A9u.2H2@cuug.ab.ca> <3n6sip$6cs@wendy.ibmpcug.co.uk>
Date: Sat, 22 Apr 1995 23:17:13 GMT
Lines: 23
Xref: glinda.oz.cs.cmu.edu comp.soft-sys.powerbuilder:13885 comp.object:29881 comp.lang.c++:124508 comp.lang.smalltalk:22946

John Tyndale (irish@nicotine.win-uk.net) wrote:

: One question.  Are you suggesting that functionality should be
: spread across the window and the menu?

I'm unsure what you mean exactly by the question, but typically my menus 
have very short scripts that, in most cases, consist of simply triggering 
an event on parentWindow.

I've thought about this topic a little since writing the original 
message, and I suppose one could create a generic enough menu attached to 
a window and then inherit both as a single entity. In the descendant 
object the developer could then hide/show menu items as appropriate.

The other option is to take the route of Delphi and insert/overlay menu 
items based on some type of identifier. I've only looked at Delphi for a 
grand total of about ten minutes, but what I saw of their menu handling 
looked interesting.
-- 
Craig Wagner		| Internet:	wagnerc@cuug.ab.ca
CPD Professional	| Fidonet:	1:134/238
Visual Systems		| Home: (403) 271-7387
Calgary, AB		| Work: (403) 262-9970
