New post
AllAccepted answers
Stefan Wittmann · Jan 29, 2016

What this means is that you have to create a new CSP application in the System Management Portal here:

 System > Security Management > Web Applications

 Create a new web application and provide "/" as the name. Select "csp/sys" in the copy from dropbox and save the web application.

This allows you to access

http://localhost/csp/sys/UtilHome.csp

as

http://localhost/UtilHome.csp

Stefan Wittmann · Jan 15, 2016

Sure. The best way to achieve this is to build your own custom theme using the jQM ThemeRoller application:

https://themeroller.jquerymobile.com

Add a swatch with a custom letter (e.g. "f") and define your theme by setting colors, fonts and so on for all elements. When you are done you can download the theme zip file and extract it in the directory where you serve your static files from.

Include your CSS file, instead of the default jQM CSS file and finally just set the defaultTheme of your jQMPageManager to the swatch you designed (e.g. "f") and you are done.

Stefan Wittmann · Dec 16, 2015

Steve,

here is a link to the related documentation from 2015.2:

http://docs.intersystems.com/ens20152/csp/docbook/DocBook.UI.Page.cls?KEY=ESOAP_web_service#ESOAP_ws_soap_sessions

If I read this correctly, then different SOAP calls do not share the same CSP license slot by default. If you set the parameter SOAPSESSION=1, then a SOAP header will be added to the response that allows the client to maintain the session for subsequent calls.

HTH,

Stefan

Stefan Wittmann · Dec 15, 2015

Hi Fabio and Bernd,

<documentView>.disableItem(id,newState);

is really just a shortcut for 

<layoutItem>.$disable(newState);

Both only work on standard control elements, and only *if* the library rendering the widget in question don't add special logic. jQueryMobile implements their own styles and behavior for disabling and enabling elements, therefore, it is the most stable approach to leverage the jQM logic.

A long discussion regarding this topic can be found here: http://stackoverflow.com/questions/5875025/disable-buttons-in-jquery-mobile

Let's walk through this in the ZM.jQM145.HomePage.cls demo and disable/enable the main button with the caption "Start demo".

var view = zen('mainView');

var button = view.getItemByKey('start-show');

var id = button.$findElement().id;

$('#'+id).button('disable');

$('#'+id).button('enable');

Line 1 retrieves the documentView component while line 2 retrieves the button layout object. This is pretty basic. 

In order to run jQM logic we have to find the HTML DOM element we want to disable/enable with the $() method from jQuery. As it requires the physical id that Zen Mojo generated for us we store that in a local variable id in line 3.

Line 4 now looks up the jQM widget and disables it with the supported jQM library call. Line 5 enables the button again.

In the future, we may add support for $disable and these special library calls as we have done for $show and $hide. $show and $hide work on any widget from any supported plugin.

HTH,

Stefan