Commit graph

7 commits

Author SHA1 Message Date
jperkin
a887acb737 graphene: SunOS needs -D__EXTENSIONS__ 2022-05-14 15:31:50 +00:00
adam
b6d9bd86bc revbump for icu and libffi 2021-12-08 16:01:42 +00:00
nia
f8331b5844 graphics: Replace RMD160 checksums with BLAKE2s checksums
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
2021-10-26 10:45:53 +00:00
nia
84d3786e88 graphics: Remove SHA1 hashes for distfiles 2021-10-07 14:11:55 +00:00
nia
7c9ac0c4d4 graphene: set PYTHON_FOR_BUILD_ONLY 2021-04-12 13:23:36 +00:00
wiz
808d527cff graphene: simplify download URL 2020-09-06 13:24:40 +00:00
prlw1
191488c53d Add graphene 1.10.2
Needed for GTK4.

Description:
When creating graphic libraries you most likely end up dealing with
points and rectangles. If you're particularly unlucky, you may end
up dealing with affine matrices and 2D transformations. If you're
writing a graphic library with 3D transformations, though, you are
going to hit the jackpot:  4x4 matrices, projections, transformations,
vectors, and quaternions.

Most of this stuff exists, in various forms, in other libraries,
but it has the major drawback of coming along with the rest of
those libraries, which may or may not be what you want. Those
libraries are also available in various languages, as long as those
languages are C++; again, it may or may not be something you want.

For this reason, I decided to write the thinnest, smallest possible
layer needed to write a canvas library; given its relative size,
and the propensity for graphics libraries to have a pun in their
name, I decided to call it Graphene.

This library provides types and their relative API; it does not
deal with windowing system surfaces, drawing, scene graphs, or
input. You're supposed to do that yourself, in your own canvas
implementation, which is the whole point of writing the library in
the first place.
2020-09-04 11:21:41 +00:00