[comp.graphics] OO Graphics

pcb@cacs.usl.edu (Peter C. Bahrs) (11/18/90)

What exists for OO graphics besides HOOPS, Smalltalk and Actor?

I heard that some work was done at Brown University..."Bags" ???
Has anyone heard of this work?


/*----------- Thanks in advance... --------------------------------------+
| Peter C. Bahrs                                                         |
| The USL-NASA Project                                                   |
| Center For Advanced Computer Studies      INET: pcb@swamp.cacs.usl.edu |
| 2 Rex Street                                                           |
| University of Southwestern Louisiana      ...!uunet!dalsqnt!gator!pcb  | 
| Lafayette, LA 70504                                                    |
+-----------------------------------------------------------------------*/

i1neal@exnet.iastate.edu (Neal Rauhauser -- ELT Computer Applications Group) (11/18/90)

In article <18871@rouge.usl.edu> pcb@cacs.usl.edu (Peter C. Bahrs) writes:
>What exists for OO graphics besides HOOPS, Smalltalk and Actor?

   If by 'Actor' you mean Actor3.0 from the WhiteWater Group, I have used
it quite a bit and would recommend that you take a look at Asymetrix's
ToolBook. ToolBook is slow, hogs memory and disk space, and OpenScript
(its language) is definitely Cobol for the nineties, but it has some
pretty good graphics features.

        i1neal@exnet.iastate.edu

garry@ithaca.uucp (Garry Wiegand) (01/26/91)

Cazier@mbunix.mitre.org (Cazier) writes:
>As a researcher involved with the management and integration of computer
>standards, what does the object-oriented world bring to the graphics
>standards and interoperability table?
>
>Will OO approaches to graphics somehow "solve" the interoperability issue
>between software packages re: sharing graphics files such as CGM or some
>other type of standard? If so, how?

I have not heard of anything along these lines yet - extending OO
concepts from memory data out into exchanged data. I can see how it
would make the metafiles more readily extensible, but everyone would
still have to agree on the basic structure and method before they
could start extending.

But besides the extensible datatypes, 3/4's of the point of OO
programming is the ability to modify/override instance methods.
There's no good way yet to exchange procedures between programs, so
it's hard to export methods.

(I've added comp.object to the newsgroups: line.)

Garry Wiegand    ---    Ithaca Software, Alameda, California
...!uunet!ithaca!garry, garry%ithaca.uucp@uunet.uu.net