On 07/23/2012 12:25 PM, Knoll Lars (Nokia-MP/Oslo) wrote:
> On 7/23/12 10:55 AM, "ext Samuel Rødal" wrote:
>
>> On 07/16/2012 10:59 PM, ext Fredrik Höglund wrote:
>>> On Monday 16 July 2012, Thiago Macieira wrote:
On segunda-feira, 16 de julho de 2012 07.47.10,
gunnar.sle...@nokia.com w
On 7/23/12 10:55 AM, "ext Samuel Rødal" wrote:
>On 07/16/2012 10:59 PM, ext Fredrik Höglund wrote:
>> On Monday 16 July 2012, Thiago Macieira wrote:
>>> On segunda-feira, 16 de julho de 2012 07.47.10,
>>>gunnar.sle...@nokia.com wrote:
I both like and dislike the idea. Like because it resolve
On 07/16/2012 10:59 PM, ext Fredrik Höglund wrote:
> On Monday 16 July 2012, Thiago Macieira wrote:
>> On segunda-feira, 16 de julho de 2012 07.47.10, gunnar.sle...@nokia.com
>> wrote:
>>> I both like and dislike the idea. Like because it resolves all the functions
>>> and that way save a lot of p
On Saturday 21 July 2012 09:50:25 Sean Harmer wrote:
> On Monday 16 July 2012 20:22:24 Sean Harmer wrote:
> > On 16/07/2012 19:54, gunnar.sle...@nokia.com wrote:
> > > On Jul 16, 2012, at 4:54 PM, ext Sean Harmer wrote:
> > >> On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
> > >>> On segund
On Monday 16 July 2012 20:22:24 Sean Harmer wrote:
> On 16/07/2012 19:54, gunnar.sle...@nokia.com wrote:
> > On Jul 16, 2012, at 4:54 PM, ext Sean Harmer wrote:
> >> On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
> >>> On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
> >>>
On Monday 16 July 2012, Thiago Macieira wrote:
> On segunda-feira, 16 de julho de 2012 07.47.10, gunnar.sle...@nokia.com wrote:
> > I both like and dislike the idea. Like because it resolves all the functions
> > and that way save a lot of pain and dislike because it adds a lot of
> > symbols, and
On segunda-feira, 16 de julho de 2012 18.54.17, gunnar.sle...@nokia.com wrote:
> The reason we didn't go for this in the past is that end-user applications
> always link directly against the OpenGL library, so it doesn't matter what
> libraries Qt resolves at runtime. The app will resolve a differe
On 16/07/2012 19:54, gunnar.sle...@nokia.com wrote:
> On Jul 16, 2012, at 4:54 PM, ext Sean Harmer wrote:
>
>> On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
>>> On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
>>
On Jul 16, 2012, at 4:54 PM, ext Sean Harmer wrote:
> On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
>> On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
>>> On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
I'm asking for Qt 5.0: what should we tell Linux distr
On Monday 16 July 2012 08:09:29 BRM wrote:
> > From: Sean Harmer
> > I don't like how even building the wayland QPA plugin means that we limit
> > Qt
> >
> > and the apps built with it to OpenGL ES. I really don't want to get into a
> > situation where we can build modern OpenGL apps for the desk
On Monday, July 16, 2012 07:21:23 Thiago Macieira wrote:
> On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
> > On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
> > > I'm asking for Qt 5.0: what should we tell Linux distributors to
> > > configure qtbase with? Considering wh
> From: Sean Harmer
> On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
>> On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
>> > On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
>> > > I'm asking for Qt 5.0: what should we tell Linux distributors
> to
>> > > conf
On Monday 16 July 2012 07:21:23 Thiago Macieira wrote:
> On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
> > On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
> > > I'm asking for Qt 5.0: what should we tell Linux distributors to
> > > configure
> > > qtbase with? Considerin
It gets worse :)
For the Linux Desktop we also want Qt to not only work with Mesa (which
provides us with a GLES 2 api), we also want it to function with say the
proprietary nvidia drivers, which do not provide GLES (on ia32/x64) or the
wayland egl extensions.
Simon
--
Sendt fra min Nokia N91
On segunda-feira, 16 de julho de 2012 15.12.15, Sean Harmer wrote:
> On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
> > I'm asking for Qt 5.0: what should we tell Linux distributors to configure
> > qtbase with? Considering what requirements qtwayland has, I think it needs
> > to be -opengl
On Monday 16 July 2012 07:08:38 Thiago Macieira wrote:
> On segunda-feira, 16 de julho de 2012 13.30.31, Sean Harmer wrote:
> > IMHO, no. If Desktop GL capabilities are present on the system then Qt
> > should enable their use. In time Wayland maybe adopted by Desktop OpenGL
> > vendors without the
On segunda-feira, 16 de julho de 2012 13.30.31, Sean Harmer wrote:
> IMHO, no. If Desktop GL capabilities are present on the system then Qt
> should enable their use. In time Wayland maybe adopted by Desktop OpenGL
> vendors without the need of pulling in X and GLX but for now it is ES2
> only.
"I
On Monday 16 July 2012 05:10:25 Thiago Macieira wrote:
> On segunda-feira, 16 de julho de 2012 07.47.10, gunnar.sle...@nokia.com
wrote:
> > I both like and dislike the idea. Like because it resolves all the
> > functions and that way save a lot of pain and dislike because it adds a
> > lot of symb
On Monday wk29 2012 July 16 05:10:25 AM ext Thiago Macieira wrote:
> On segunda-feira, 16 de julho de 2012 07.47.10, gunnar.sle...@nokia.com
wrote:
> > I both like and dislike the idea. Like because it resolves all the
> > functions and that way save a lot of pain and dislike because it adds a
> >
On segunda-feira, 16 de julho de 2012 07.47.10, gunnar.sle...@nokia.com wrote:
> I both like and dislike the idea. Like because it resolves all the functions
> and that way save a lot of pain and dislike because it adds a lot of
> symbols, and I'm a little bit uncertain on the usecase.
>
> Because
Hi Gunnar,
On Monday 16 July 2012 10:00:03 gunnar.sle...@nokia.com wrote:
> Compatibility between ES and desktop needs to be handled for these classes
> to be used in Qt. For the core set that Qt/QML currently uses, this is
> already handled by QOpenGLFunctions.
ES does not support geometry shade
On Jul 16, 2012, at 10:46 AM, ext Sean Harmer wrote:
> Hi,
>
> On Monday 16 July 2012 07:47:10 gunnar.sle...@nokia.com wrote:
>> I both like and dislike the idea. Like because it resolves all the functions
>> and that way save a lot of pain and dislike because it adds a lot of
>> symbols, and I'
Hi,
On Monday 16 July 2012 07:47:10 gunnar.sle...@nokia.com wrote:
> I both like and dislike the idea. Like because it resolves all the functions
> and that way save a lot of pain and dislike because it adds a lot of
> symbols, and I'm a little bit uncertain on the usecase.
The use case is for an
I both like and dislike the idea. Like because it resolves all the functions
and that way save a lot of pain and dislike because it adds a lot of symbols,
and I'm a little bit uncertain on the usecase.
Because the functions are not a well defined subclass hierarchy (and nor can
they be), the u
Hi,
I have pushed the following WIP patch for review:
https://codereview.qt-project.org/#change,30554
The idea of this is to provide a set of classes that expose the OpenGL
functions specific to the version and profile of the corresponding
QOpenGLContext.
This means that it is no longer neces
25 matches
Mail list logo
