View Single Post
Old 10-16-2018, 09:52 AM   #87
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
The raw image API is probably going to be limited to the actual C API, because that'd be rather messy and hard to use via a CLI shim, but the plan is basically to accept G8/G8A8/R8G8B8/R8G8B8A8 raw scanlines, passing that data, the x res, the y res (i.e., number of scanlines/rows), the exact size of the buffer, and then everything gets processed through the existing image rendering code .

@sherman also floated the idea of implementing FT support directly, but that's probably on the back burner for now .

Last edited by NiLuJe; 10-16-2018 at 10:02 AM.
NiLuJe is offline   Reply With Quote