What is the status of EGL_MESA_screen_surface?

[Adam Jackson]

On Thursday 23 February 2006 20:57, Paul Ramsey wrote:
> > The idea is to provide a complete interface so the developer doesn't
> > have to be concerned with any other lower-level native environment.
> > The implementation of EGL_MESA_screen_surface (and EGL itself) might
> > of course tie into a lower-level interface such as fbdev, or it might
> > program the hardware directly.  In any case, the EGL application
> > developer doesn't have to care.
>
> Having all of the functions have "egl" at the first three letters of the
> name doesn't make it more complete. It just puts Khronos into the business
> of designing minimalist window systems.

Designing the API for, but sure.

EGL is already being implemented as an opaque interface to the window system.  
All this does (or rather, is intended to do) is extend EGL just enough to be 
the window system on its own.

> > I guess one could do that, but I think it's simpler to just have a new
> > sub-type of drawing surface.  Also, we don't have to worry if all the
> > EGL window surface properties/semantics apply to screen surfaces, and
> > vice versa.
>
> As far as EGL is concerned a ScreenSurface as described in this spec
> already has all of the semantics of a window. The window just happens to be
> full screen.

No, eglWindows have to be created relative to a "native" window.  Platform 
#ifdefs in every application.  Whereas a screen surface is created by the 
implementation from whole cloth.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dri-egl/attachments/20060224/36eccf69/attachment.pgp