Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #144846 > unrolled thread

OT: libpng docs

Back to article view | Back to comp.lang.c

Contents

  OT: libpng docs nobody@example.org (Scott) - 2019-06-14 15:25 +0000
    Re: OT: libpng docs Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-06-14 20:46 +0000
      Re: OT: libpng docs nobody@example.org (Scott) - 2019-06-16 02:01 +0000
        Re: OT: libpng docs Eli the Bearded <*@eli.users.panix.com> - 2019-06-19 06:26 +0000
          Re: OT: libpng docs nobody@example.org (Scott) - 2019-06-19 16:04 +0000
            Re: OT: libpng docs Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-06-19 09:16 -0700
              Re: OT: libpng docs Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-06-19 20:42 +0000
                Re: OT: libpng docs My nuts hurt <cdalten@gmail.com> - 2019-06-20 06:55 -0700
                Re: OT: libpng docs Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2019-06-20 07:46 -0700

#144846 — OT: libpng docs

Any of you who have worked with libpng, were you able to find a better
source of documentation than the abstruse wall of text that is the
official manual?

[toc] | [next] | [standalone]

#144865

On Fri, 2019-06-14, Scott wrote:
> Any of you who have worked with libpng, were you able to find a better
> source of documentation than the abstruse wall of text that is the
> official manual?

No.  I think I used that, and the header file.  On the other hand, I
didn't look further.

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

[toc] | [prev] | [next] | [standalone]

#144908

On 14 Jun 2019 20:46:34 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se>
wrote:

>On Fri, 2019-06-14, Scott wrote:
>> Any of you who have worked with libpng, were you able to find a better
>> source of documentation than the abstruse wall of text that is the
>> official manual?
>
>No.  I think I used that, and the header file.  On the other hand, I
>didn't look further.

That's where I'm at as well. I'll likely end up rummaging around in
the sources to answer some questions too. Thanks for posting though,
if I do find something better I'll share it here.

[toc] | [prev] | [next] | [standalone]

#144979

In comp.lang.c, Scott <nobody@example.org> wrote:
> On 14 Jun 2019 20:46:34 GMT, Jorgen Grahn <grahn+nntp@snipabacken.se> wrote:
>> On Fri, 2019-06-14, Scott wrote:
>>> Any of you who have worked with libpng, were you able to find a better
>>> source of documentation than the abstruse wall of text that is the
>>> official manual?
>> No.  I think I used that, and the header file.  On the other hand, I
>> didn't look further.
> That's where I'm at as well. I'll likely end up rummaging around in
> the sources to answer some questions too. Thanks for posting though,
> if I do find something better I'll share it here.

When you posted that, last week, I hadn't done anything with libpng.
Since then I've implemented some code to generate png files. I found

http://zarb.org/~gc/html/libpng.html

which has a sample program that reads a (RGBA) png, modifies it on a
pixel by pixel basis, and then writes a new one out. It was very helpful
to see that and then be able to check against the wall-of-text manpage.

I'm not likely to be doing any reading of them, but I did want to write
more than just RGBA and now I can.

Elijah
------
RGBA, RGB, GA, G in multiple bit depths

[toc] | [prev] | [next] | [standalone]

#144985

On Wed, 19 Jun 2019 06:26:35 +0000 (UTC), Eli the Bearded
<*@eli.users.panix.com> wrote:

>When you posted that, last week, I hadn't done anything with libpng.
>Since then I've implemented some code to generate png files. I found
>
>http://zarb.org/~gc/html/libpng.html
>
>which has a sample program that reads a (RGBA) png, modifies it on a
>pixel by pixel basis, and then writes a new one out. It was very helpful
>to see that and then be able to check against the wall-of-text manpage.

Nice find, thanks. There is (seems to be) a lot more to libpng, but
that's not a bad starting point.

[toc] | [prev] | [next] | [standalone]

#144986

On Wednesday, 19 June 2019 17:02:41 UTC+1, Scott  wrote:
> On Wed, 19 Jun 2019 06:26:35 +0000 (UTC), Eli the Bearded
> <*@eli.users.panix.com> wrote:
> 
> >When you posted that, last week, I hadn't done anything with libpng.
> >Since then I've implemented some code to generate png files. I found
> >
> >http://zarb.org/~gc/html/libpng.html
> >
> >which has a sample program that reads a (RGBA) png, modifies it on a
> >pixel by pixel basis, and then writes a new one out. It was very helpful
> >to see that and then be able to check against the wall-of-text manpage.
> 
> Nice find, thanks. There is (seems to be) a lot more to libpng, but
> that's not a bad starting point.
>
You might prefer LodePNG, written by Vance Lode

https://lodev.org/lodepng/

You can also get my copy of it on GitHub, along with other image format
codecs.

https://github.com/MalcolmMcLean/babyxrc

[toc] | [prev] | [next] | [standalone]

#144987

On Wed, 2019-06-19, Malcolm McLean wrote:
> On Wednesday, 19 June 2019 17:02:41 UTC+1, Scott  wrote:
>> On Wed, 19 Jun 2019 06:26:35 +0000 (UTC), Eli the Bearded
>> <*@eli.users.panix.com> wrote:
>> 
>> >When you posted that, last week, I hadn't done anything with libpng.
>> >Since then I've implemented some code to generate png files. I found
...

>> Nice find, thanks. There is (seems to be) a lot more to libpng, but
>> that's not a bad starting point.
>>
> You might prefer LodePNG, written by Vance Lode
>
> https://lodev.org/lodepng/

libpng has one big advantage: it's widely available (installed on
almost all Unix machines already) and well tested (by normal usage,
and by attempts to exploit bugs in it).

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

[toc] | [prev] | [next] | [standalone]

#144990

On Wednesday, June 19, 2019 at 1:42:28 PM UTC-7, Jorgen Grahn wrote:
> On Wed, 2019-06-19, Malcolm McLean wrote:
> > On Wednesday, 19 June 2019 17:02:41 UTC+1, Scott  wrote:
> >> On Wed, 19 Jun 2019 06:26:35 +0000 (UTC), Eli the Bearded
> >> <*@eli.users.panix.com> wrote:
> >> 
> >> >When you posted that, last week, I hadn't done anything with libpng.
> >> >Since then I've implemented some code to generate png files. I found
> ...
> 
> >> Nice find, thanks. There is (seems to be) a lot more to libpng, but
> >> that's not a bad starting point.
> >>
> > You might prefer LodePNG, written by Vance Lode
> >
> > https://lodev.org/lodepng/
> 
> libpng has one big advantage: it's widely available (installed on
> almost all Unix machines already) and well tested (by normal usage,
> and by attempts to exploit bugs in it).
> 

I *think* one of the engineering groups at my job uses libpng. I *think*. I'm not that sure since we employ over 1000 engineers in our division alone.

[toc] | [prev] | [next] | [standalone]

#144992

On Wednesday, 19 June 2019 21:42:28 UTC+1, Jorgen Grahn  wrote:
> On Wed, 2019-06-19, Malcolm McLean wrote:
> > On Wednesday, 19 June 2019 17:02:41 UTC+1, Scott  wrote:
> >> On Wed, 19 Jun 2019 06:26:35 +0000 (UTC), Eli the Bearded
> >> <*@eli.users.panix.com> wrote:
> >> 
> >> >When you posted that, last week, I hadn't done anything with libpng.
> >> >Since then I've implemented some code to generate png files. I found
> ...
> 
> >> Nice find, thanks. There is (seems to be) a lot more to libpng, but
> >> that's not a bad starting point.
> >>
> > You might prefer LodePNG, written by Vance Lode
> >
> > https://lodev.org/lodepng/
> 
> libpng has one big advantage: it's widely available (installed on
> almost all Unix machines already) and well tested (by normal usage,
> and by attempts to exploit bugs in it).
> 
I make that two advantages.

LodePNG is a single file solution. You drop it into your codebase, and
then it has a simple interface to read and write a PNG. It's not the
industry standard, so not suitable for all applications. But often it's
a better option, particularly for small projects.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c

csiph-web