@Mark
*** Thanks for your expertise. I couldn't do that this perfectly. ***
One of the reasons for posting this JPNG stack is to show the power of LC:
The essential code of compressing PNG -> JPNG and decompresing PNG -> JPNG
is both less than 10 *essential* lines of code, using com
On 2017-08-11 10:41, Richmond Mathewson via use-livecode wrote:
It may not, but the stack does export images with a .lcjpng suffix . .
. and the question is what for?
Perhaps so it can be loaded again by code which knows how to decompress
them as images in LiveCode? After all you have to *stor
stion is a bespoke way of reducing resource
size for built apps and their content - as there isn't a 'standard'
for JPNG (yet) it isn't really useful for interchange between apps,
but it might be that a standard does appear at some point.
Can your stack export a JPNG image
s and their content - as there isn't a 'standard' for JPNG
(yet) it isn't really useful for interchange between apps, but it might
be that a standard does appear at some point.
Can your stack export a JPNG image?
It doesn't need to in order to be useful. This is som
JPNG image?
And, if, so; what will read it?
AND this:
"This may even result in a larger data size than the original when
decompressing."
doesn't bode well.
Richmond.
On 8/11/17 2:56 am, hh via use-livecode wrote:
JPNG (named using JPEG and PNG) is not an image format but a com
JPNG (named using JPEG and PNG) is not an image format but a compression method.
We use the file ending ".lcjpng" for that.
It takes features from both JPEG (setting JPEGquality to compress the imageData
and from the PNG compression the alphaData/transparency). It saves the
alphaData,
