Just interested if anyone puts all there loadscripts split into include files ?
I can see the advantages of doing this for easier version control and reuse.
I have seen some applications that have more tabs than I would like to say and would like to avoid this situation.
I also like the idea of using Visual Studio or Notepad++ and the qlikview plugin from MatthewFryer for editing.
Let me know what you think.
Hi Mark -
I have only used include script for Section Access, although I have thought about using them on other occasions. The only reason I haven't took the initiative is because I feel during the development stage, I have to make changes to the script several times and it seems that it would be easier to do it in the application itself.
The other issue is related to what parts of the script should I move to text files so that I can benefit from reuse? Master Calendar, Currency Conversion, some other standard widgets? The issue is that every other application I need to work on require a slight modification to these standard widgets which would again require to have another text file. I guess this end up pushing me away from maintaining text files for script. But if someday I can truly standardize a part of the script (just like the Section Access) I would love to move to text files.
Thanks for the reply Sunny,
You make some good points.
My main feeling is that I would like to gain more control over what already exists in the loadscripts.
I am also trying out Xmind (hopefully Visio in the future) to have a visual view of my loadscripts, the idea being that I can then link the external text files to the mind map.
Have a great weekend.
I use include-files for many things (paths, file-formats, variables, section access, various load- and subroutines) and think that I have further potential to include some more and optimize them but to make respectively keep all scripting outside from qlikview (even with the Notepad++ extension which is great) is a very radical and rather unpractically approach.
I'm still thinking about the pros and cons at the moment.
One of the cons would be when it comes to moving code between different development environments would be a little more effort.
As most of my other developments are done within text files I didn't think this approach was that radical.
to keep everything what is redundant in include-files is very useful but each application has it own reason and therefore script-parts. I would need a lot more working-steps in switching between the external editor and qlikview to write and check my script and change it again and would also need to open the qv script-editor to put the include-files there (unless you would prefer to nest all the include-files - I use also nested included-files, but couldn't say that I'm very happy about it).
Further if you have very long respectively many often in tab splitted scripts it would be not easier to handle it externally, for example if I have 30 tabs in Notepad++ open. For me are possible advantages in versions control not so relevant - it's very simple and old-school to create a backup before I do bigger changes, slight changes are most not controlled or even documented which might be insufficient in larger environments where several/many people are involved (but for me it's ok.).