Create and implement a standard for visual installers for all deep-packages

[Konard]

The ideal solution would be:

1. Create link type for example:

   (VisualInstaller: Any Type ClientHandler)
   

   or

   (VisualInstaller: Any Type TSX)
   

   or

   (VisualInstaller: Any Type Selector)
   

   Using selector may allow selecting any ClientHandler like link.

   Also, it would be great to use VisualInstaller link as an outgoing link from package itself, issues required to be closed before completion:

   • Possibility for links to point to package #95
   • Put Package link inside deep.json as link with reserved name: this deeplinks#256
   • Add PackageDepends and package link inside package #36

2. Add handler that opens client handler on creation of Installed link connected with installed package. This handler should create Opened link with ClientHandler selected by VisualInstaller link.

[FreePhoenix888]

Why is this handler called VisualInstaller? Why should it be open on package installation? What this handler should do?

[Konard]

Why is this handler called VisualInstaller?

Do you have better ideas?

Why should it be open on package installation?

Because in Windows and Linux it works like this, you think it is not necessary?

What this handler should do?

Make all preparations/initial settings that are required for any package to work. If there is no visual installer, the user will not see it.