Based on the discussion at yesterday's update center meeting, we need to
close on couple of UI design related issues. Steve, Rochelle, I know
that you already discussed some of this offline but there were some
concerns raised with the current approach, so I am sending this out to
whole dev alias so that everyone has an idea where we are and we can
reach some conclusion.
I also updated corresponding issue comments where appropriate to capture
this.
* Requirement to show module license(s) prior to download/installation
https://updatecenter.dev.java.net/issues/show_bug.cgi?id=16
For most components we are dealing with we cannot rely on showing and
accepting the license at the time the component is first used so we'll
need to show it in updatecenter UI. One approach we discussed yesterday
is to implement license dialog which will show licenses for multiple
selected modules in wizard-like fashion. Each screen would have text of
module license and offer user choices to accept or decline license (each
choice should automatically send user to the next license screen to
minimize number of clicks necessary for navigation). We would also like
to add "Accept all licenses" choice but this may not fly well with legal
- in any case we can put it there and remove if necessary.
* Requirement to notify user of newly available updates when UI is not
started through tray
https://updatecenter.dev.java.net/issues/show_bug.cgi?id=5
Nazrul already added some comments to the issue, in a nutshell, we don't
believe that it will be enough to preselect appropriate updates to
convey to the user that these are newly downloaded and available
updates. Note that we will have a way to distinguish whether UI is
running from tray process or has been started as standalone process, so
that should control whether to show the explicit message about module
availability or not (if message was already shown in tray popup).
* Requirement to provide generic tokenization support (UI part)
https://updatecenter.dev.java.net/issues/show_bug.cgi?id=8
We will need to provide rather generic way to interact with user and
gather appropriate configuration parameters in order to perform initial
configuration of some components. I will work on backend implementation
of this, but from UI standpoint we need to show dialog with dynamically
created content in the course of installation progress. UI will get
prompt text for each field that needs to be shown, construct text field
with appropriate label, gather information from the user and send it
back to the backend.
* Requirement to ask for user permission before deploying an application
(or other runtime modules)
https://updatecenter.dev.java.net/issues/show_bug.cgi?id=17
For some module types (applications and addons) we need to warn user
that these are runtime modules and ask explicit permission to
deploy/install them. Since the module type is known in advance prior to
download/installation, what would be the best point to get this
permission? Before the download, or between download and installation?