Hi Jakob,

I've pushed an updated version to

http://cgit.freedesktop.org/~olv/st_api/

If you think anything is not ready to go into st_api.h, just let me
know.  I will move them to DESIGN.  Or you can start a repo that I can
pull from.

I myself would like to see the st_visual and st_api->make_current issues
resolved (listed as issue 1 and 3 in DESIGN file).

I also want to use a consistent variable naming in st_api.h.  Here is my
preference

* use smapi for "struct st_manager_api"
* use stapi for "struct st_api"
* use stfb/stdraw/stread for "struct st_framebuffer"
* use stctx/stshare for "strcut st_context"
* use statt for "enum st_framebuffer_attachment"

In the state trackers or st managers, there might already be
structs/enums to represent things like api, fb, ctx, or att.  Prefixing
those in st_api.h help state trackers distinguish which of them they are
refering to.

I now also think "struct st_manager" might be a better name than
"struct st_manager_api".  How does it sound?

-- 
Regards,
olv

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to