Can I offer a link to a Toolbox in the Add-On Explorer?

I am a steward of Matlab Community Toolboxes. I often edit example Live Scripts for toolboxes.

If a Live Script requires an additional toolbox, I'd like to be able to give the user the option to click on a link to the toolbox in the Add-On Explorer. For example, one example script requires the System Identification Toolbox. Is there a link I can offer the user to go right to the Add-On Explorer entry?

Thanks

Steve

[Dyuman Joshi]

LiveScript provides that option by itself.

See the attached image - I wrote a code using the gscatter function, which requires the Stats and ML toolbox, and I do not have that installed.

When I run the code in the livescript, it mentions the toolbox needed and provides a link. When you click on the link, it opens the corresponding Add-On Explorer entry directly.

[Steve Van Hooser]

Thanks Dyuman. I appreciate the note.

This isn't quite the behavior I want for my user. I want to allow the user to add all the toolboxes needed in the beginning of the tutorial, so they don't get interupted in the middle.

I suppose a workaround would be to call some function in a helper function that activates each toolbox. But then I'd need to identify a light function (that returns quickly) for each required toolbox, or test for the existence of the toolbox before running it.

So I'd prefer the ability to just assert that the toolbox is there and ask the user to add it if it is not there.

Thanks

Steve

[Walter Roberson]

This is a feature I have requested in the past

I know that it must be internally possible as I have encountered links that say roughly to click on a link to install a package (for example Image Acquisition Explorer offers links to install support packages). I did not, however, investigate to find the mechanism.

In the past I found something but it needed an abstract url not deduceable from the package name

[Steven Lord]

Am I correct in assuming it's not the case the whole community toolbox that requires the additional toolbox, but just some of the examples and/or functions? So it would not be completely accurate to list the additional toolbox as a requirement of the community toolbox? It's more the additional toolbox enables certain functionality, or the example shows how the community toolbox interacts with functionality in the additional toolbox?

[Steve Van Hooser]

That's right, it is a particular LiveScript demo that requires a toolbox. I'd like to run the test at the beginning of the LiveScript.

Thanks

Steve