[Ben] HTML5 preloading suggestion...
Peter TB Brett
peter.brett at livecode.com
Thu Jul 16 13:08:42 CEST 2015
On 2015-07-16 02:35, Monte Goulding wrote:
>> On 16 Jul 2015, at 4:06 am, Colin Holgate <colinholgate at gmail.com>
>> I looked at the HTML5 example pages, and they take a while to load.
>> I’ve seen that sort of slowness before, where it took a while to
>> download a lot of graphics. In that particular case each download was
>> completed before the next one starts. The problem was completely
>> solved by allowing more connections at the same time.
>> So, if the current version is also assuming one connection at a time,
>> change it to allow six at once.
> It looks like it’s just one file:
> I’m hoping that rather than deploy standalones we have the option to
> deploy stacks and an engine to run them with the engine pulled from a
> common CDN and cached.
At the moment -- and I'm working on changing that right now -- the demo
standalones consist of three files:
* standalone-community.js is the engine itself. It is the same for all
* standalone-community.html.mem is the initial memory image for the
engine. As above.
* standalone-community.data is a file system image that contains the
stack file(s) and other essential resources.
At the moment, we are expecting that people who deploy standalones will
configure their web servers to ask browsers to cache the engine and
initial memory image.
If I was designing a larger app using HTML5 support, I would probably
put a "splash screen" stack in the standalone, and then get the splash
screen to download additional stacks and resources using "get url",
while giving progress feedback.
Dr Peter Brett <peter.brett at livecode.com>
LiveCode Engine Development Team
More information about the use-livecode