Il 21/01/2017 15:02, Иван Комиссаров ha scritto:
> Do I understand correctly that all is needed is to scan header of the
> texture, get some info from it and than load whole texture to the byte
> array?
Yes, get some metadata from the file, and no, not necessarily extract
the images as byte arrays
> 21 янв. 2017 г., в 16:25, Sean Harmer написал(а):
>
> It's
> about being able to parse texture files into CPU addressable memory. From
> there
> it can be used by OpenGL, Direct3D, Vulkan, Metal, $OTHER_API.
>
Do I understand correctly that all is needed is to scan header of the texture,
On Saturday 21 January 2017 13:51:15 André Pönitz wrote:
> On Sat, Jan 21, 2017 at 10:51:11AM +, Sean Harmer wrote:
> > On Friday 20 January 2017 20:35:49 Konstantin Tokarev wrote:
> > > 20.01.2017, 00:22, "Oswald Buddenhagen" :
> > > > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angel
On Sat, Jan 21, 2017 at 10:51:11AM +, Sean Harmer wrote:
> On Friday 20 January 2017 20:35:49 Konstantin Tokarev wrote:
> > 20.01.2017, 00:22, "Oswald Buddenhagen" :
> > > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
> > >> Nonetheless, since such loaders would be useful
On Friday 20 January 2017 20:35:49 Konstantin Tokarev wrote:
> 20.01.2017, 00:22, "Oswald Buddenhagen" :
> > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
> >> Nonetheless, since such loaders would be useful in more than one place
> >> (qtbase, qtdeclarative, qt3d) I think th
perhaps that is not so interesting anymore with the advent of
>> ETC2.
>>
>>
>> Cheers,
>> Laszlo
>>
>>
>> From: Giuseppe D'Angelo
>> Sent: Friday, January 20, 2017 11:11:09 AM
>> To: Laszlo Agocs; development@qt-project.org
>> S
20.01.2017, 00:22, "Oswald Buddenhagen" :
> On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
>> Nonetheless, since such loaders would be useful in more than one place
>> (qtbase, qtdeclarative, qt3d) I think that the best place for them would
>> be a new private library in qt
09 AM
> To: Laszlo Agocs; development@qt-project.org
> Subject: Re: [Development] Texture image loading library
>
> Il 20/01/2017 11:05, Laszlo Agocs ha scritto:
> > Ok. Adding support for ETC1/2 in PKM containers may be useful too (Qt 3D
> > should have some code for
szlo Agocs; development@qt-project.org
Subject: Re: [Development] Texture image loading library
Il 20/01/2017 11:05, Laszlo Agocs ha scritto:
> Ok. Adding support for ETC1/2 in PKM containers may be useful too (Qt 3D
> should have some code for it IIRC), but that can be added later.
>
Is
Il 20/01/2017 11:05, Laszlo Agocs ha scritto:
> Ok. Adding support for ETC1/2 in PKM containers may be useful too (Qt 3D
> should have some code for it IIRC), but that can be added later.
>
Is there anyone using those containers? Last time I checked I had a very
hard time finding specifications f
10:45 AM
To: Laszlo Agocs; development@qt-project.org
Subject: Re: [Development] Texture image loading library
Il 20/01/2017 09:25, Laszlo Agocs ha scritto:
> This would bring the benefit of potential reuse in the Quick (Image
> element) compressed texture support, once that materializes at s
Il 20/01/2017 09:25, Laszlo Agocs ha scritto:
> This would bring the benefit of potential reuse in the Quick (Image
> element) compressed texture support, once that materializes at some
> point in the future.
>
>
> Are ETC1 and ETC2 included? They would be fairly important as well.
Yes, but only
Il 19/01/2017 22:22, Oswald Buddenhagen ha scritto:
> you can't put it there if qtbase is to use it.
*Shees* Sorry, I planned to write that Qtbase is unlikely to use it
directly, except for providing enablers to other modules. But ok, let's
put this stuff in there.
Thanks,
--
Giuseppe D'Angelo |
t] Texture image loading library
On quinta-feira, 19 de janeiro de 2017 22:22:17 PST Oswald Buddenhagen wrote:
> the central "regular" image loaders are in qtgui, and the "elementary"
> (6MeB of sources ...) opengl support is nowadays also in qtgui, so it
> seems quite pla
On quinta-feira, 19 de janeiro de 2017 22:22:17 PST Oswald Buddenhagen wrote:
> the central "regular" image loaders are in qtgui, and the "elementary"
> (6MeB of sources ...) opengl support is nowadays also in qtgui, so it
> seems quite plausible to put the texture loaders there as well.
And event
On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
> Nonetheless, since such loaders would be useful in more than one place
> (qtbase, qtdeclarative, qt3d) I think that the best place for them would
> be a new private library in qtimageformats.
>
you can't put it there if qtbase is
Hi,
As part of some ongoing work I'd like to add some private classes in Qt
to deal with loading of texture files.
Texture files (.dds, .ktx, etc.) are somehow different from ordinary
image files. Not only they store image data in GPU-oriented formats
(that don't require any decoding on the CPU),
17 matches
Mail list logo
