launcher_with_automatic_client_updates [TAST DokuWiki ]

User Tools

Site Tools


Sidebar

First steps in TAST

What is UML

Computer setup for TAST use

FAQ

Recognized Issues

TAST tool Menu

TAST Adaptors

Adaptors examples

TAST Integrations

Interesting features

Documentation of technical administration

Modeling recommendations

Training in the TAST tool

launcher_with_automatic_client_updates

Launcher with automatic client updates

Introduction

A launcher has been included in TAST. This launcher is a comfortable way to deal with the TAST client updates. Here below an explanation of how this launcher works and some tips will be found.

Explanation

The launcher is an executable that search if the user has the latest version of the client in the folder where it is located.

  • Once the launcher does the comparison can happen two different things, the first one is that a new client version is downloaded and then executed,
  • and the second one is that it founds the latest version and this one is executed directly.

Also, the client has two new functionalities:

If someone don´t use the launcher to open the client, but instead uses the client itself, if the client is obsolete it will ask you if you want to upload it (only if is in the same folder as the launcher).

A visual guide of this is:

First, we open the version 1.60.10 for example, in this example the updated version is 1.60.11


When the client is open and the username and password settled, we click login and:


This warning will appear, if we choose “YES” it will download the new version of the client and it will open it (calling the new launcher functionality), otherwise if you press “NO”, it will open that outdated version client (just if the client is not in the same folder as the launcher, if it is, it will be updated within 60 seconds).

On the other hand, other new functionality of the client is if the client belongs to a connection pool (If the Lab Host belongs to a connection pool) that client is supposed to be open always, so the client will automatically update even if it is open doing nothing.

The meaning of that is: with the new launcher you have to click in the launcher to update it but in this case, with a client in a connection pool, there is no need to click in the launcher it will automatically download the new version and log in into the account only having the client open and logged. If the client is not in a connection pool it also will automatically update if its open, but this functionality was focused on the connection pool clients.

How to use the launcher step by step

To use this launcher, we are going to start from the basis. First of all, we have to download it. To do that, we have to go to TAST application and click in client, then click in exe version.

Now the download will be an executable named tast.exe, not like before that was a tast.zip.

Once we have downloaded the launcher, we have to execute it. A little window will appear, and the client update will start.

When the download is finished, the launcher will automatically unzip the new client and save it in the same folder where the launcher is located.

And to finish this process it will automatically open the launcher.

Those were the steps in the case that it’s the first time downloading the launcher.

If you already have the launcher in your computer (tast.exe), you should use it always from now on. That’s because the launcher will automatically download the new clients and you don’t need to download the clients manually as we are doing up until now.

Tips for using TAST Launcher

To use the TAST Launcher with some optimization we recommend to create a folder exclusively to keep the launcher there so in that folder all the clients will be stored and create a shortcut of the launcher to execute it.

The automatic downloads when the client remains open just happens if the client is in the exact same folder where the launcher is. That’s why we recommend the creation of a folder apart to keep the launcher with the clients.

launcher_with_automatic_client_updates.txt · Last modified: 2023/12/18 14:44 (external edit)