topic Re: When should a developer make a new tab in edit script in QlikView

When should a developer make a new tab in edit script

Mon, 04 Nov 2013 10:33:06 GMT

When should a developer make a new tab in edit script

1: when code exceeds 255 lines

2: When he first time access edit script

3: when the script is no more logically related

Re: When should a developer make a new tab in edit script

Jason_Michaelides — Mon, 04 Nov 2013 10:35:53 GMT

Number 3. The best use of tabs in the edit script is to logically divide the sections of the script. Then you can put a nice big header of comments explaining what this section of script will do (plus of course more commenting on lines that need it, which will be many of them).

Jason

Re: When should a developer make a new tab in edit script

Mon, 04 Nov 2013 10:39:41 GMT

This is really help full,

what if entire script is related with only one section?

Re: When should a developer make a new tab in edit script

Gysbert_Wassenaar — Mon, 04 Nov 2013 10:40:24 GMT

Whenever it improves maintainability of the application.

Re: When should a developer make a new tab in edit script

ngulliver — Mon, 04 Nov 2013 10:40:28 GMT

Hi, Sreeharsha.

Jason is absolutely correct.

Remember, the person coding the edit script may not be the same person who has to amend or maintain it.

So it is important to break it down into logical sections so that the code can be easily followed. By having clearly named tabs you can resolve issues much quicker.

Regards,

Neil

Re: When should a developer make a new tab in edit script

Jason_Michaelides — Mon, 04 Nov 2013 10:46:35 GMT

"what if entire script is related with only one section?"

Then try to break it down further. But if it is a small script only performing one logical function that one tab is fine (although the settings is usually best in a tab of its own for tidiness)

Re: When should a developer make a new tab in edit script

Gysbert_Wassenaar — Mon, 04 Nov 2013 10:51:48 GMT

Some developers put every load in a sub routine and put groups of related sub routines on their own tab. On a 'main' tab all those subs are called in the order they should be executed. This makes it easy to follow the flow of the script at a high level and dive into details in the subs.