Hi,
RhoElements 4.0.0 on MC3190 Windows 6.5
javascript only
Navigate too slowly (about 5 sec) between action and real start navigate.
I tried:
Rho.WebView.navigate(path);
Rho.WebView.refresh();
document.location.href = path;
rholog.txt:
I 02/18/2014 10:59:31:000 0edd60f2 WKEngine| Navigate :file://\Program Files\RhoElements\HTML\index.html
I 02/18/2014 10:59:34:000 ed756e7e Eng.cpp: 207| Message from Engine:CWkInterface::InitEngine - Engine Version: 2.2.6.2 (Release 11504)Line: 190
I 02/18/2014 10:59:34:000 ed756e7e RhoWKBrowserEngine.cpp: 47| onTopmostWnd
I 02/18/2014 10:59:34:000 ed756e7e Eng.cpp: 207| Message from Engine:WinMain - The engine has startedLine: 121
I 02/18/2014 10:59:34:000 0edd60f2 WKEngine| START PB_ONTOPMOSTWINDOW
I 02/18/2014 10:59:34:000 0edd60f2 WKEngine| ProcessOnTopMostWnd
I 02/18/2014 10:59:34:000 2d6d2fbe Sync| Starting main routine...
I 02/18/2014 10:59:34:000 2d6d2fbe Sync| ThreadQueue blocked for 60 seconds...
I 02/18/2014 10:59:35:000 0edd60f2 Core::LoadPlugin| Scanner
5 Replies
I found that not delay if I'm not including rhoapi-modules.js
Maybe Sync? Can I disable it?
Found this in the documentation under Rho.WebView.navigate("http://www.example.com");
Considerations
Each NativeTabbar creates its own WebView, which consumes a fair amount of resources. On older devices, mainly on Windows Mobile, this can make the whole application run more slowly, especially if your views are complex. Be sure to test on a physical device to get a feel for the responsiveness of your application.
Also its highly recommended to not use jQM or any other styling libraries on WinMo or WEHH based devices.
thank you.
Im not using NativeTabbar and jQM
what about document.location.href = path; ? its working slowly too...
The window.open works well for me.
window.open("http://www.w3schools.com");
Could you attach the page you are trying to display or site you are trying to navigate to?