First off: why would we want to use JQuery? A very readable article arguing about it can be found here – also read the comments there. Since Cognos 11 is forcing its users to use modern web browsers a few advantages are gone, but I still like to work with JQuery anyways.
At first – if you watched the introduction video for R4 – it sounded like the HTML-item just got replaced with the new custom control. So, what’s the fuzz about?
Basically it’s not that simple. There are actually 3 types now:
- HTML- item: for your basic HTML and CSS needs
- Custom control object (new): Provide your own user interface
Rick Blackwell has given some information regardings the RAVE situation. As it turns out, it is not integrated in the last release but will probably be in the R5 due at the end of the year (fingers crossed).
Rick gave a few statements on the IBM Visualization board:
So, as we looked at RAVE 2 we chose a new set of goals:
1. In the box visualizations
2. More properties to allow more flexibility from a single visualization thereby minimizing the times a custom visualization is required
3. Well known technology base allowing customers to find developers with skills more easily
RAVE 2 has been is use by Watson Analytics since 2015; RAVE 1 will be eliminated from Watson Analytics very soon.
We are bringing RAVE 2 into the Cognos Analytics now. I expect to see it first in Dashboards in combinations with RAVE 1 and then in reports by the end of the year. Unlike RAVE 1, RAVE 2 visualizations will ship with the product and have many properties such that one does not need to create a new bundle for each minor variation. The exact set of RAVE 2 visualizations and properties is not yet fixed; I expect we will have a somewhat basic set of properties this year and add more over time.
We will leave RAVE 1 in Cognos Analytics to ensure that existing reports still operate. Of course, Cognos Analytics already supports RAVE 1 so there are no issues moving from Cognos BI 10.x.
Next year, we will look at providing an SDK to allow customers to integrate D3 content into Cognos Analytics. Details are yet to be worked out but the basic idea would be to keep the D3 code the same but add new code for the data and interactivity APIs and so on.