[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Object Widgets
- Subject: Re: Object Widgets
- From: "J.D. Smith" <jdsmith(at)astro.cornell.edu>
- Date: Tue, 16 Nov 1999 16:45:45 -0500
- Newsgroups: comp.lang.idl-pvwave
- Organization: Cornell University
- References: <3823382B.E454DF02@va.aetc.com> <firstname.lastname@example.org> <38306F7E.F5371DDE@astro.cornell.edu> <email@example.com> <firstname.lastname@example.org>
- Sender: verified_for_usenet(at)cornell.edu (jts11 on vodka.tn.cornell.edu)
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:17315
Struan Gray wrote:
> J.D. Smith, email@example.com writes:
> > I often do all sorts of things in the Start method.
> Having thought about it a bit I can see several advantages to this
> idea. Part of me still likes the idea of invoking a working widget
> with a single call, but I expect I'll get over it. Incidentally, if
> you feel like showing the public your generalised messaging class I
> for one would be very interested.
Do to demand I have put a tiny ObjMsg page up at:
It's just a skeleton of a page, and, as it mentions, without examples and
details, ObjMsg doesn't seem to have much utility. Basically, ObjMsg is just a
set of conventions for method extensions and some convenient housekeeping. The
real meat of this paradigm exists in inheriting classes, some of which I hope to
clean up and post at some point. For instance, the "Start" method convention
doesn't even exist at this high level, but originates one level down in a
so-called broker class. It's not really as complicated as it sounds.
Anyway, comments are welcome.
J.D. Smith |*| WORK: (607) 255-5842
Cornell University Dept. of Astronomy |*| (607) 255-6263
304 Space Sciences Bldg. |*| FAX: (607) 255-5875
Ithaca, NY 14853 |*|