What is Webview Button in Design toolbar(in Qlikview) used for?

[Anonymous]

What is Webview Button in Design toolbar(in Qlikview) used for?

[Chanty4u]

hi

AJAX/WebView Help

This help is used for the AJAX client as well as the WebView mode in the QlikView Desktop. Some features might differ slightly in the different clients.

WebView Mode in QlikView Desktop

Via a single click on a toolbar button it is now possible to switch between traditional rendering and AJAX rendering when running QlikView Desktop. This feature provides a convenient way for the developer to see exactly how the layout will look when used from an AJAX client. Naturally the AJAX property dialogs are available when running in WebView, providing some nice functionality that is not available to the developer in standard view. However, it should be noted that some functionality are not available in WebView, for example:

• report editing.
• menu commands cut, copy, and paste (shortcuts Ctrl+X, Ctrl+C, and Ctrl+V).
• Animation of charts

[Peter_Cammaert]

Where do I start?

1. For testing/checking the layout of applications that will be visited using the AJAX client. For instance, there are subtle differences between object sizes, object positions, fonts and the likes between QV Desktop/IE Plugin mode and AJAX/WebView mode. Better check them before you publish. WebView allows you to do that.
2. For dobulechecking disabled/enabled features before you publish your document. WebView replaces the normal rightmouseclick menus with those from the AccessPoint. To check what options and menu entries an AccessPojnt visitor will have at his/her disposal, use WebView.
3. To simulate navigation and document usage as-if-you-were using the AJAX client on an AccessPoint document. In WebView, everything that isn't available in the AJAX client (built on HTML+Javascript) will be disabled. Does your document still work?
4. Made a macro that cunningly manipulates UI and object layout properties? Switch to WebView. Does it still work?
5. Etc.

Nice devleoper feature, this WebView. Only one disadvantage. You cannot decouple WebView from the Internet Explorer DLLs so there is no way to use Google Chrome as WebView engine.

Peter

[stabben23]

Hi, this should be used before you move the developed application to production if you gona use AccessPoint.

You will be suprised that object can change so much in layout in webView and in desktop mode.

[oscar_ortiz]

In addition to what everyone else said above.

If you are using extensions you must use webview.