LiveCode Forums.

Hi there,

First attempt at HTML5 and despite the large loading time it works.
But the output is not sharp at all. It is blurry, nor retina(?) proof?
That is for images, text and even for simple 'oval' graphics.
Is there a way to get it better?

Greetings,

William (iMac retina 4K)

I wonder what format the HTML5 standalone builder exports LiveCode images to?

Just run off an image-intensive stack as an HTML stack and waiting 'forever' for the blasted thing to load.

The original stack (image at 30% of original) looks like this:
- -
OK, OK: I'll just pop off for my lunch while the thing tries to load . . .

So; after 60 minutes the thing has not loaded.

At this point I was going to say something unrepeatedly coarse and get on with something else, but foolishly, I decide to reduce
that stack to a single card; and as I was hiving off an HTML standalone the title picture went "all black"

(admittedly this may have something to do with macOS 11.1 playing 'silly buggers' with PNG images imported into Livecode):
- -
So, then tried to load that HTML5 'thang' . . .

Churning
- -
Cripes . . . NBG.

It didn't work for me locally but only when I put the files on my webserver.
Localhost takes forever to load with Safari or Chrome (from the Test button in the IDE).
On my webserver it takes about 20 sec. I think to load the file(s).

The odd thing is that somewhere inside the HTML5 standalone folder I would expect to find
versions of images from the original stack, and am unable to.

Presumably (?) images are encoded in either the

standalone-community-9.6.1.html.mem

or the

standalone-community-9.6.1.js

especially as the HTML5 standalone comes in with amazing bloat at 41.8 MB

(compared with 17.4 MB for a macOS build from the same stack).

2.5 times bigger than a macOS build.

Yes, no seperate images but somewhere within these files indeed.
And no question answered yet.

Why is everything so blurry?
Anyone?

Maybe you need to use images with higher resolution.

It is not just images.
It is also text, svg widgets and simple graphic ovals,

I don't know why everything is blurry, but if the images were imported as controls then they have become embedded in the stack file as binary code. They won't exist outside the app.

I'm just guessing, but load times might be faster if the images are referenced instead.