| Re: More OO jargon [message #49401] |
Mon, 24 July 2006 09:59  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Sat, 22 Jul 2006 16:48:48 -0700, Robbie wrote:
> I have recently published some of my frequently used base classes which
> are a part of my Nuclear Medicine software project (NMTK).
>
> NMTK Atom Tree:
> This is a factory class which manages a set of IDL graphics objects.
>
> NMTK Control:
> This is an alternative to using coventional OO event handlers.
> I consider this class to be more useful than xmanager because it has
> better support for multiple controls within the same UI. It's still
> incomplete because I'm hunting around to steal someones data model.
> Feel free to tack on your own data model.
Sounds like we're all reinventing the same wheel. David has his Catalyst
library, and I have my Object Messaging framework, both of which free you
from the constraining structure of "up the inheritance stack" message
passing, which is the default IDL event mode.
|
|
|
|
|
|
| Re: More OO jargon [message #49618 is a reply to message #49482] |
Sat, 05 August 2006 23:55  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Robbie writes:
> I think that there it is possible to find an ideal object design of
> event processing, widget managment, graphics management, data model,
> macros etc.. using IDL. I thought through a number of designs before
> choosing the one I liked. It's then a matter of collating those ideas
> together into a single package and developing a rich set of UI features
> to complement it.
Well, and then writing the book that describes it. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
