Re: [Chromium-dev] New Darwin Patch

[Christopher W. <cr...@ms...>]

On Jul 15, 2004, at 11:58 AM, Jorge Luis Williams wrote:
> I was running some experiments and I noticed that some AGL and GLX 
> programs generate CGL calls which are not documented.  Have you run 
> into these problems?  I always assumed one of the undocumented calls 
> linked the window with the context..is this what you're doing in the 
> render spu??

Actually, I have, and all I've done with them is forward them to their 
respective native CGL functions.  I'm not sure what the non-context 
parameters are yet, but I've been working to figure/find that out =)
These functions include:
	CGLSetSurface (4 parameters with the first being CGLContextObj)
	CGLGetSurface (4 parameters with the first being CGLContextObj)
	CGLUpdateContext (1 paramter, which is a CGLContextObj)

> How functional is your patch have you tested with AGL, GLX and Cocoa 
> apps?  If your patch isn't fully functional yet maybe we should merge 
> both of our patches since mine appears to be fully functional for GLX 
> apps.  Take a look at what I've done and let's see if we can add a 
> compilation option where we can compile with only GLX support and this 
> is fully functional for now or we can compile CGL which will be 
> experimental till you get your stuff up and running. This will get 
> people up and running on Darwin fast.
>
> On the other hand if you feel CGL is complete enough to support CGL, 
> AGL, and GLX apps - then maybe we should ignore my patch completely 
> :-)

I have only been able to test it with the chromium demo programs, and 
some of the samples that Apple provides.  While trying to test a Cocoa 
ogl app, I noticed that chromium (starting mothership) doesn't handle 
pathnames with spaces in them very well, even the "\ " spaces =(

At this time, I would assume that it works with everything except AGL 
... that is, -if- NSOpenGL doesnt do anything with contexts =\

  -Chris