> Anyone interested in the topic of image optimization
> could learn a lot from this webpage too:
>
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/image-optimization
Check this useful information about two new image compression
file formats: BPG and FLIF
> Al wrote:
> Yes, LiveCode shell control is a real godsend for
> working with command line programs, but we could
> not use webP compressed images within our stacks
> unless LC engine could decode them back to RGBA
> images within LiveCode.
So what's the problem?
Decode them with shell to a (tem
Richard Gaskin wrote:
> This sounds like a good opportunity
> for using FFI in a Widget.
Looks like every computer language
now uses FFI. I think that we need
a Cookbook to learn this new feature
or adapt tutorials from other platforms.
Who volunteers to add LiveCode to this
Wikipedia article:
ht
Alejandro Tejada wrote:
> Hermann Hoch wrote:
>> For webP you could use (from LC via shell) these
>> free WebP utilities for Mac/Win/linux
>
> Yes, LiveCode shell control is a real godsend for
> working with command line programs, but we could
> not use webP compressed images within our stacks
>
On Sat, 26 Aug 2017, Monte Goulding wrote:
> I don?t think anyone is ruling anything out.
This is good news! :D
Hermann Hoch wrote:
> For webP you could use (from LC via shell) these
> free WebP utilities for Mac/Win/linux
Yes, LiveCode shell control is a real godsend for
working with command li
For webP you could use (from LC via shell) these free WebP
utilities for Mac/Win/linux:
cwebp -- WebP encoder tool
dwebp -- WebP decoder tool
vwebp -- WebP file viewer
webpmux -- WebP muxing tool
gif2webp -- Tool for converting GIF images to WebP
See https://developers.google.com/speed/webp/downl
> On 26 Aug 2017, at 5:12 am, Alejandro Tejada via use-livecode
> wrote:
>
> Please, before ruling out completely the opportunity
> to include a modern compressed image format
> like webP,
I don’t think anyone is ruling anything out.
Cheers
Monte
_
I forgot a very important aspect of implementing webP in LiveCode engine.
For a first implementation, LiveCode could import (decode) only static -not
animated- webP images and exclude the option of exporting images as webP
(excluding the encoder from the engine). This would reduce the complexity
o
NVM you are talking about the compression ratio.
Bob S
> On Aug 25, 2017, at 12:12 , Alejandro Tejada via use-livecode
> wrote:
>
> WebP compress flat color graphics (with transparency)
> much better than PNG or GIF.
>
> This is not a guess based on visual comparisons.
___
I thought PNG is lossless. How can the image be better than the original??
Bob S
> On Aug 25, 2017, at 12:12 , Alejandro Tejada via use-livecode
> wrote:
>
> WebP compress flat color graphics (with transparency)
> much better than PNG or GIF.
>
> This is not a guess based on visual compariso
Hi Monte,
on Thu Aug 24 2017, Monte Goulding wrote:
> webM would require a reasonable size refactor to players because
> we would need to wrap a custom player around the library and then
> decide which player to use depending on the movie file.
> webP on the other hand looks like it could be added
Hi Alejandro
webM would require a reasonable size refactor to players because we would need
to wrap a custom player around the library and then decide which player to use
depending on the movie file.
webP on the other hand looks like it could be added without any refactoring,
however, as you c
Hi All,
Now that there is an ongoing thread about storing
bitmap images inside a SQLite BLOB, I just want to
remember that there is an enhancement request
in LiveCode Quality Center for supporting
webP and webM in LiveCode engine.
If webP and webM support in Livecode Engine
could help in your
13 matches
Mail list logo
