Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Or just some best practices to follow when creating your own ones?
Currently I'm doing the following:
...and now I'm ready to start working on my Document Extension, make changes to the files, refresh, debug and inspect in my browser.
Is there an easier way of doing this?
I would check out Stephen Redmond's blog www.QlikTips.com or check out the direct link to his beginners guide: http://www.qliktips.com/2011/01/beginners-guide-to-qlikview-extension.html
Thanks Oscar, but that blog only covers Extension Objects, not Document Extensions
Hi
I guess that this is the way (neatly described).
If you just want to inspect what you are doing, you could add a
Qva.LoadScript('https://getfirebug.com/firebug-lite.js#startOpened', function() {
...
});
in your script and then look at HTML/CSS/Script directly in QlikView Desktop (skipping the Server steps). No support for breakpoints though...
But due to lack of breakpoints and stepping, I also run all my development from a server.
Br Patrik
PS!
To automate the process, I use grunt.js (http://gruntjs.com/) to simplify development of extensions. Change the code, run grunt and then test. Some work to set up the environment though but if you are into heavy extension development then its well invested time.
DS!