[GEM Development] Today I Learned

Thomas Clayton topcatdrc at yahoo.com
Tue Feb 28 09:45:07 PST 2012


John,

> What it involves is rewriting all the video drivers,
> so that they store the palette values ... .

Wouldn't THAT be MORE far-reaching? !:-|

Also, I'm amazed at your knowledge of _just_where_ GEM places _what_ within its 'guts'! 

Besides someone RE-reading the source code (from scratch, as it were);
is there any place these things _are_ documented?
In other words, IF we were to "loose" John Elliot, where could the "rest of us" (<-- to steal a phrase!) find out about these things that YOU know?

Sincerely,

Thomas Clayton




--- On Mon, 2/27/12, John Elliott <jce at seasip.demon.co.uk> wrote:

From: John Elliott <jce at seasip.demon.co.uk>
Subject: Re: [GEM Development] Today I Learned
To: gem-dev at simpits.org
Date: Monday, February 27, 2012, 1:48 PM

> I'm thinking that the function-call will (would) have to be made "lower" in=
>  the system, so ALL windows would see the same palette. This implies some  =
> fundamental programming changes with-in GEM.=20
> 
> (Now, let me show my ignorance: this would be changing the call from the AE=
> S to the VDI ??
 )

  It's not quite as far-reaching as that. What it involves is rewriting all 
the video drivers, so that they store the palette values in their code segment
(which is common to all programs) rather than their data segment (which gets
duplicated every time a program opens a new graphics workstation).

-- 
John Elliott
_______________________________________________
gem-dev mailing list
gem-dev at simpits.org
http://www.simpits.org/mailman/listinfo/gem-dev



More information about the gem-dev mailing list