Scripting Index and online Help: "see also"

[hogi]

☐ cool new feature
☑ could help many users!

☑ removes a „bug“

☐ nice to have

☐ nobody needs it

The scripting index is a great source of knowledge and the examples are very useful to understand what the functions do and how they can be used (with some code context around the actual function).

On the other hand, for a user who wants to find a function for a specific application, the functionality of Scripting Index feels a bit like:
If you don't know the correct function name, I cannot give you the correct info.
https://community.jmp.com/t5/Discussions/Collection-of-quot-funny-quot-JSL-newbie-questions/m-p/5593... 

With some "links" between the entries, a user can be guided through the Scripting Index and finally get to the function that he wants.

-> Please add "see also" to the online help and fill "see also" of the scripting index" with more alternatives along the idea:
What possible confusions could have led users to search this function?

e.g. there should be a link between Length/NItems  and  NRow/Dim

examples:

https://www.mathworks.com/help/matlab/ref/length.html

https://reference.wolfram.com/language/ref/Length.html

compare:
https://www.jmp.com/support/help/en/16.2/index.shtml#search/length 

more wishes submitted by  

[hogi]

Visibility / Get visibility:

see also: Set Property

to set the visibility

[hogi]

close data grid and close summary panels

wrong desriptions in the scripting index (see screenshots)
(description is the same as for close side panels)

[hogi]

column<< set selected

add a link to 

dt << Clear Column Selection();

[hogi]

Lineup Box:
The "example" is definitely a nice application case for lineup boxes.

But: Is N=1 really the best possible example for N Cols Lineup Box?

Does it make sense to add a second (slightly more general) example?

[jthi]

N Col(1) is a good example, because it will make all displays have similar width BUT there should be first example with larger N Col and this N Col(1) is more like a special case (even though it is very common and usable case).

Also noticed that we have Line Up Box in Scripting Index which uses N Col(2) and then Lineup Box which uses N Col(1).

[hogi]

the delight of synchronous wonder:
https://community.jmp.com/t5/Discussions/JMP-Scripting-Index-feedback-and-discussion/m-p/590951/high... 

[hogi]

good examples:
For some commands, there are plenty of example codes listed, all the possible options are listed as comments in the examples and there are even some explanatory comments
-> very helpful 

[hogi]

for normal variables, there is no difference between creating the variable or changing the value of a variable:

x=1;

for table variables, there is:

new table variable ("x",1);

and

set table variable ("x",1);

Unfortunately, in the see also, nothing is listed.

Ah, x=1 works as well
any difference to set table variable?

[Craige_Hales]

https://community.jmp.com/t5/Discussions/difference-between-set-and-new-table-variable-strange-resul...

(difference between set and new table variable - strange results in writing string?  )

describes how strings and numbers are handled by the functions and variables. It would be great if the doc(s) were updated with the info.

[hogi]

How good for Jmp that some wise guy set up the community