EMIWG/QuickInstallBetaRequirements

Introduction

This document describes the main requirements of Eclipse Pulsar. The QuickInstall feature will not have all requirements implemented and it will provide only some basic features.

Below image presents the initial view of the QuickInstall feature and the information that will be available there. It is important to highlight that when the "Install" action is executed, a usual update process will be started based on P2 UI flow.

It is important to highlight that part of the information presented on QuickInstall view is local (internal of pulsar) and another part is online (that depends on SDK Providers sites). The offline information [REQ1] is related to SDK Providers (the root node of Mobile SDK Tree) and the online information [REQ2] is related to the SDKs categories and installable units (the children of Mobile SDK Tree).

If some of the concepts described here are not clear, please refer to the definition session at the Use Case document.

Needs

QuickInstall feature aims at solving some specific problems. Those problems are listed below and the feature requirements and design need to answer each of them.

- Improved User Experience: QuickInstall needs to provide a better user experience on the process of identifying new Mobile SDKs and downloading them;

- Reuse current P2 Provisioning Mechanism: QuickInstall must not provide a new provisioning protocol. It must reuse P2 as it is and focus only on improving the user experience;

- Reuse current P2 UI Flow: QuickInstall must focus only on Mobile SDK discovery. The other execution flows must reuse as much as possible the current P2 UI flow (that minimizes the effort to implement the solution as a whole).

Requirements

- [REQ1]: List Repositories The quick install UI shall ask the quickinstall services for the list of metadata repositories that are registered. For each repository it shall query its content to identify the SDKs that are available. ([gep]: how the SDK providers URLs will be hardcoded? should we just have all of them is the usual eclipse settings as any other repository?) ([gep]: if the repository is not HTTPS or if there is some error to access i, should we just ignore it or present some error message to teh user?)

- [REQ2]: Query SDK Provider Repository The quick install UI shall ask the quickinstall services for the detailed information of this repository. This request must return informatio such as:

 - Repository name
 - SDK imagem (if available)
 - Categories
 - Instalable units of each category

This information is presented on the UI to the user. The user is then able to select as many SDKs as he wants to be intalled and then press "Install" to start the download / install process.

([gep]: if the SDK image is not available, should we present some default image?)

- [REQ3]: Start Download Process When the user presses "Install", the quick install view will send a request to P2 to start the process. The usual P2 UI flow must be followed ([gep]: how to start this process? it is still necessary to understand how to do that on P2)

Missin Features

- Only new content is shown. Dialog doesn't show what is already installed

- Only newest version of each IU is shown

- IU version is not shown

- Doesn't filter by repository