[UX] Update toolchain view

[jyoungyun]

Let's try to finish the following within May. 😨 😅 🥵 🍺

• Enhanced "show installable toolchains"
  • Revise previous toolchains() to be friendlier to UI #573
    • toolchainTypes()
      • returns, e.g., ['official', 'nightly']
    • toolchains() -> toolchains(toolchainType: string, from: number, count: number)
      • why? there could be, e.g., tons of versions in some toolchain type, e.g., nightly.
      • e.g., toolchains('nightly', 10, 20) returns 20 nightly versions starting from recent 10th version
    • remove deprecated code
  • Frontend
    • [Toolchain] Use installed toolchain functions #684
  • unit test (if necessary)
    • backend impl
  • Find how to 'apt-get update' of a specific debian package #578
  • Solve prerequisite to use a specific debian repo
    • e.g., registrer a specific debian repo, installing required packages, e.g., ca-certificates, wget, gnupg2, etc.
    • Make backend provide prerequisite commands #627
• Show already-installed toolchain
  • Introduce method that returns installed toolchains #659
  • function & view UI
    • show list (draft: [Draft] Show toolchain list #657)
      • [Toolchain] Add toolchain tree provider #658
    • show dependency information (draft: [Draft] show toolchian information #688)
      • [Toolchain] Show dependency information on tooltip #690
  • unit test (if necessary)
    • view UI
    • backend impl
• Find out how to solve 'sudo' issue #577
  • [Backend] Add root boolean variable to Command class #589
  • Support to run root permission job #634
  • Add progress window while job is running #636
• Uninstall toolchain (draft: [Toolchain] Uninstall toolchain #699)
  • check backend API
    • Add automatic yes and quiet option to uninstall command (PR 54)
  • function & view UI
    • [Toolchain] Add uninstall command #665
    • [Toolchain] Uninstall toolchain #707
  • unit test (if necessary)
    • view UI
• Install toolchain #653
  • check backend API
    • Set install and uninstall to root (PR 45)
    • Use aptitude tool when installing toolchain (PR 51)
  • function & view UI
    • [Toolchain] Input password in case root request #652
  • unit test (if necessary)
    • view UI

Improvement point

• Revise backend API
  • class Compiler -> class Toolchain
• Toolchain view
  • Improve dependency information UI
• Toolchain API
  • [Toolchain] Add success and failure callback to job request #704
• Install
  • frontend (one-vscode)
    • Improve UI
      • [Toolchain] Auto refresh toolchain view when toolchain is installed #706
      • Improve progress UI
      • Encrypt user password
    • advanced functions
      • Install latest official toolchain ([Backend] Use ProblemResolver to install older packages #779)
      • Install old official toolchain ([Backend] Use ProblemResolver to install older packages #779)

[jyoungyun]

There are a few parts to consider.

Enhanced "show installable toolchains"

• If the artifactory data is changed when user requests toolchain lists, how can we control this situation?

Show already-installed toolchain

• backend impl (May not be needed?)
  • The current implementation asks if it is installed to all available lists. It takes a lot of resource to ask it. How about returning an information whether it is installed together when it first returns the list?

[hyunsik-yoon]

If the artifactory data is changed when user requests toolchain lists, how can we control this situation?

Maybe we can have setInterval() that keeps calling apt-get update one or twice per day while ONE-vscode is up and running.
However, some users may not call apt-get update so we may need to find out some way to call apt-get update for backend Debian repo.

• backend impl (May not be needed?)
  • The current implementation asks if it is installed to all available lists. It takes a lot of resource to ask it. How about returning an information whether it is installed together when it first returns the list?

How about having the following API?

Toolchain.getBackendInfo(backendVersion: string): backendInfo;

ONE-vscode refreshes its toolchain list view when it is up for the first time. At that time, the UI can call the above function to get more specific info.

[jyoungyun]

ONE-vscode refreshes its toolchain list view when it is up for the first time. At that time, the UI can call the above function to get more specific info.

How about adding installed variable to ToolchainInfo structure? Then we do not need to make an additional call for this job.

[jyoungyun]

Toolchain View Scenario

Initial loading

No toolchain

• Nothing to do
• 

Installed toolchain

• Show installed toolchain in toolchain view
• 

Install

Not set prerequisites

• Show information message Prerequisites has not been set yet. Do you want to set it up now?
  • If yes, call prerequisites
  • 
  • If no, nothing to do
  • 

Install : Assumption

• The latest package: install debian package
• Older package: install docker image
• 

Install debian package

• No installed toolchain (initial state)
  • not yet
• Already installed toolchain
  • Show information message Backend toolchain can be installed only one. Do you want to remove the existing installed toolchain?
  • If yes, remove the existing installed toolchain and then install the selected toolchain
  • 
  • If no, show canceled information message Installation is canceled.
  • 

[jyoungyun]

Almost features were merged. So I will close this issue at this point and I will continue the related job on another issue.