On Fri, Feb 5, 2010 at 7:40 PM, José Fonseca wrote:
> On Thu, 2010-02-04 at 21:23 -0800, Chia-I Wu wrote:
>> On Thu, Feb 4, 2010 at 9:31 PM, Keith Whitwell
>> wrote:
>> >> As st_api.h can be implemented parallelly with st_public.h, a possible
>> >> route I
>> >> would like to take is to (in this
On Thu, 2010-02-04 at 21:23 -0800, Chia-I Wu wrote:
> Hi Keith,
>
> Thanks for having a closer look.
>
> On Thu, Feb 4, 2010 at 9:31 PM, Keith Whitwell
> wrote:
> >> As st_api.h can be implemented parallelly with st_public.h, a possible
> >> route I
> >> would like to take is to (in this order)
On Fri, Feb 5, 2010 at 1:23 PM, Chia-I Wu wrote:
>> I had some other questions. It took a little while to understand the
>> scope of this work, but I think I'm there now. This is basically a
>> unifying interface for managing state-trackers of khronos style APIs.
>> Specifically, it is useful fo
Hi Keith,
Thanks for having a closer look.
On Thu, Feb 4, 2010 at 9:31 PM, Keith Whitwell
wrote:
>> As st_api.h can be implemented parallelly with st_public.h, a possible route
>> I
>> would like to take is to (in this order)
>> 1. implement st_api.h in OpenVG and OpenGL state trackers
>> 2. co
On Thu, Feb 4, 2010 at 3:39 AM, Chia-I Wu wrote:
> There was a discussion about a new interface, st_api.h, that will replace
> st_public.h last month. Comparing to st_public.h, st_api.h allows multiple
> current contexts for each rendering API supported. It removes the need for
> pipe_screen->fl
