Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

shree909
Valued Contributor II

Why extesnions work in AJAX/Webview

Hi,

can someone give an reason why extenions Only works in Webview/AJAX client.

1 Solution

Accepted Solutions
Employee
Employee

Re: Why extesnions work in AJAX/Webview

Extensions are objects created with web technology, e.g. html, java script or flash player. The WebView client is a web browser running inside QlikView, and - hence the extensions work.

The older QlikView C-client, written in C++ as a windows program, is not browser based and has really very little with the web to do. So, extensions do not work.

HIC

5 Replies
Employee
Employee

Re: Why extesnions work in AJAX/Webview

Extensions are objects created with web technology, e.g. html, java script or flash player. The WebView client is a web browser running inside QlikView, and - hence the extensions work.

The older QlikView C-client, written in C++ as a windows program, is not browser based and has really very little with the web to do. So, extensions do not work.

HIC

shree909
Valued Contributor II

Re: Why extesnions work in AJAX/Webview

Thanks for the response,

if i use the extenions in access point through  Internet explorer will this work.

Employee
Employee

Re: Why extesnions work in AJAX/Webview

If you use the Ajax client, yes.

But not if you use the Internet Explorer Plug-in. Both clients can be invoked from the Access point, and both can run in IE

HIC

shree909
Valued Contributor II

Re: Why extesnions work in AJAX/Webview

Thanks a lot for clarifying the issue.

could u please give an explanation why macros  only  work in IE but not AJAX.

i know that macros wont support  safari browser?

becoz macros are made up of VB script  which can be used in IE and safari  dont support Macros(vb script)

Is there any other reason??

could u elaborate on this

Thanks

Employee
Employee

Re: Why extesnions work in AJAX/Webview

Same reason. The macros are code that access the COM/Automation interface of Windows, mostly running client-side. So they work fine in the C-client,

But in a web environment there is no way to access the COM/Automation interface - the client isn't perhaps even Windows.

HIC