QlikView Web Syntax Highlighter v1.0

Hot on the heals of last week's release of QlikView for WordPress, I'm pleased to announce the first full release of QlikView Web Syntax Highlighter v1.0 which the WordPress plugin is based on.

QlikView Web Syntax Highlighter provides basic syntax highlighting of QlikView script and expressions within web pages. It utilises a custom build of Highlight.js to apply the highlighting dynamically when the web page is viewed.

This version includes the following functionality:

• Highlighting of all current (v11.20) functions
• Highlighting of all current (v11.20) keywords and statements
• Highlighting of line comments (//) and block comments (/* */ and REM ; )
• Highlighting of variable definitions (SET and LET)
• Highlighting the usage of variable within dollar-sign expansion $( )
• Highlighting of field names in most situations 

As always, grab the download link and full instructions from the QlikView Web Syntax Highlighter page. If you find any issues or have any suggestions, please leave me a comment below.

QlikView for WordPress Plugin v0.2

As you may well have seen already, yesterday I released the first official pre-release of QlikView for WordPress plugin. This plugin brings syntax highlighting of QlikView script and expressions within posts and pages to WordPress blogs and websites.

The syntax highlighting is currently an approximation of that within the QlikView script and expression editors. It is however expected that the highlighting will be improved in later versions. The next version will include significant improvements to highlighting of expressions as well as some minor bug fixes.

Downloads and full instructions for installation and use can be found on the QlikView for WordPress page, or alternatively on the WordPress.org website.

Coming soon - QlikView Syntax Highlighting for the Web

I thought I'd let you all in on another little project I've been tinkering with on the side. I have had a long standing problem when blogging about QlikView. Most of my posts contain snippets of QlikView script or expression code which can be very hard to read if it is not syntax highlighted in at least an approximation of how it is highlighted within QlikView. I considered using images taken from screen grabs of the code in QlikView, but this means readers can't copy and paste the code into their QlikView projects making it less than ideal. And so I am left with the time consuming task of having to manually highlight code snippets in my posts, and this means less time for new posts.

//Define the table name
SET vMyTable = 'MyTable1';

//Load in the table of data
$(vMyTable)_Temp:
LOAD
    A,
    B,
    text(C) & ' a string' AS C
RESIDENT $(vMyTable);

QlikView UltraEdit Wordfile v2.0

QlikView language definition for UltaEdit v2.0 has been release.

This version is a huge leap from the first release and so has been labelled as a new major release. Some of the new features include:

• Missing keywords added including TABLES, FIELDS and UNTIL
• Store statements, Qualify and Unqualify statements, info loads, mapping loads, join and keep statements are all now identified in the UltraEdit Function List
• REM has been added as a block comment. Note, unlike QlikView, UltraEdit can't apply a REM comment only if it appears at the start of a line and thus REM comments will be highlighted wherever they appear.
• Added UltraEdit templates for commonly used statements and code snippets including:
  •   Binary load
  •   Include statement
  •   Test script
  •   Environment variables
  •   Calendar script - Basic
  •   Calendar script - Basic - From Field
  •   Set statement
  •   Let Statement
  •   Script Header Comment
  •   Script Section Comment

As always, full instructions and download links can be found on the QlikView for UltraEdit page. Alternatively you can find them on branch.qlik.com or on GitHub.
 
If you have any ideas for other code templates or find any problems, let me know by leaving a comment or raising an issue on GitHub.

QlikView for UltraEdit now on Branch and GitHub

I have now moved the QlikView language definition for UltraEdit to GitHub and have added a project for it on branch.qlik.com also. Unlike the language definition for Notepad++, I haven't made any changes to the UltraEdit version but am working on a couple of minor bugs so a new version should be available soon.

If anyone is a regular user of the UltraEdit version and would like to help test future versions then please get in touch using the Contact Me link at the top of the page.

Before the move I totted up the number of times both versions have been downloaded and am amazed at the result. A wopping 5,423 times! I'm glad there are lots of "Qlikers" out there making good use of it.

QlikView Notepad++ Language Definition v2.3

I've just released a new version of the QlikView Notepad++ Language Definition. Version 2.3 contains the following minor fixes/functionality:

• Solved an issue with correct highlighting of nested function calls. Added comma "," as an operator to correct issue with function names not being highlighted correctly when it immediately follows a comma inside another function call. 
• Added missing function tool tips. All functions should now provide both auto completion and tool tips.
• Removed the ability to fold IF statements because of an issue where Notepad++ tries to collapse if() functions which causes the collapsing to fail.  

Additionally, I have moved the project to GitHub and have added it to http://branch.qlik.com/ too. As always, head over to the Notepad++ Language Definition page (or Branch) for the download link and instructions.

Getting Started with Qlik Sense

Yer yer I know, its about time I put together my first post about Qlik Sense. Better late than never hey. As a starting point, I thought I'd post the below video "Qlik Sense Desktop - quick build tutorial" from Qlik. It is the best "get started guide" I've found so far. It walks you step-by-step through getting Qlik Sense installed to creating your first visualisations and answering business questions. And you don't need to be a coding whiz either, not a single line of script was hurt during the making of this video.