Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!apple!netcom!schang
From: schang@netcom.UUCP (Sehyo Chang)
Newsgroups: comp.lang.smalltalk
Subject: Re: Future evolution of Smalltalk-80
Message-ID: <7135@netcom.UUCP>
Date: 13 Feb 90 00:52:49 GMT
References: <6836@tekgvs.LABS.TEK.COM> <SDL.90Feb12104048@lyra.lyra.mitre.org>
Distribution: comp.lang.smalltalk
Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290 guest}
Lines: 40

In article <SDL.90Feb12104048@lyra.lyra.mitre.org> sdl@lyra.mitre.org (Steven D. Litvinchouk) writes:
>
>In article <6836@tekgvs.LABS.TEK.COM> jans@tekgvs.LABS.TEK.COM (Jan Steinman) writes:
>
>> <For example, does anyone know what the much-awaited color imaging model in 
>> Smalltalk will be like?  Also, are there any plans to provide some kind of 
>> "Interface Builder" to facilitate developing user interfaces without so much 
>> MVC hacking?>
>> 
>> What do you mean, "much awaited"?  A solid color model has been available in 
>> Tek Smalltalk since 1986!  Over two person-years went into Tek Color Smalltalk, 
>> with much of that spent on building a layered architecture.  Personally, I'd 
>> love to see the portable part become a standard, but there's NIH to deal with.  
>
>
>I'm aware of this too.  But when I asked Jim Alexander if the source
>code could be made available to those of us (like myself) who own
>ParcPlace's implementation rather than Tek's, I didn't get a positive
>response either.  Can someone at Tek upload Glazier to the ParcBench
>bulletin board?
>
>Please forgive me if this sounds like a flame.  It's just that it
>would be nice that future enhancements to Smalltalk would continue to
>be relatively standard across implementations.  It would be too bad if
>Tek, ParcPlace and Digitalk all adopted different color models, for
>example!  
>

You don't have to worry about it very much since Tek is out of smalltalk
business and Digitalk's Smalltalk is ParcPlace's smalltalk's image model
is different anyway(at least classes are different).  Maybe best way to
implement color is to give access to internal display object ( such as
display bitmap) such that you can hook up host imaging model. That way
you can uses X-window's color-map capability.
Anyway, I am getting tired of just seeing b/w image.  We have gone from
bad to worse in PP 2.5, at least in 2.3 you can do some color
-- 
Sehyo Chang						schang@netcom.uucp
Ascent Logic Corp.
(408)943-0630