Miroirs/slackbuilds_ponce
1
0
Fork 0
mirror of https://github.com/Ponce/slackbuilds synced 2024-11-06 08:26:50 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

graphics/graphene: Fix README.

Browse source 
Signed-off-by: orbea <orbea@riseup.net>

Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
This commit is contained in:
orbea 2020-10-17 11:56:56 -07:00 committed by Willy Sudiarto Raharjo
parent aaab9e2d3a
commit 50804e4673
No known key found for this signature in database
GPG key ID: 3F617144D7238786
1 changed files with 16 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
graphics/graphene/README
View file

@ -1,20 +1,22 @@
ling 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.
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.
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.
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.
supposed to do that yourself, in your own canvas implementation,
which is the whole point of writing the library in the first place.