On 7/1/19 11:47 AM, Richard Gaskin via use-livecode wrote:
Curious: how long does it take to load the document in Chrome on the
same device?
Didn't get a moment to check until now. I had to count in my head, but
it's about 4-5 seconds in Firefox. Maybe 8-10 seconds in Chrome.
13 minutes in C
Curious: how long does it take to load the document in Chrome on the
same device?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.com
I was wrong. I do get "browserFinishedLoading" in about 26 seconds, but
it's lying. When I start to scroll down, it acts just like the widget.
It isn't really all there.
I guess that makes sense, assuming the widget is just a wrapper around
the mobileControlCreate code.
On 6/30/19 4:37 PM, J
I did some timing tests comparing mobileControlCreate vs. a browser
widget. Both loaded a 10-meg file from the documents folder on an
Android Pixel running Android OS 9 (Pie.)
mobileControlCreate: 26352 ms, 26610 ms (2 tries)
browser widget: 785426 ms (13 minutes).
While 26+ seconds is too
I'll experiment with it. The browser is in a stack that loads dynamically
on demand so it isn't always visible (though it does stay in RAM) so I hope
that isn't a problem.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 29, 2019 6:
Placing the browser widget in a background group and display/hide as needed is
a possible solution to have it retain content.
Thanks,
Brian
On Jun 29, 2019, 6:40 PM -0400, J. Landman Gay via use-livecode
, wrote:
> I have a 10-meg file on disk that I display in a browser widget. It is
> heavily
