Community
Participate
Working Groups
I think we need to do more work on streamlining the install process for a single product install. Right now it is just too many steps, as I have documented in my blog post http://ianskerrett.wordpress.com/2010/05/10/marketplace-client-easy-as-1-2-3/ I really think the UI could be a lot simplier if we just did single installs, so I am not sure I agree that the main use case should be multiple product installs. What do others think?
Some suggestions for streamlining the install: - Finish button should be activated once one product has been selected. - The Confirmation page should not be shown, especially if one product has been selected.
I understand why it's desirable to streamline the install process. Personally I'm in favor of enabling multiple installs, since this is my most common use case. Others may differ. A middle-ground might work well -- for example, pressing install could take the user directly to the next wizard page (as if they had pressed Next after Install in the current design). This would make it possible to press Back to select more solutions. It would be less than optimal for multiple installs, but would be easier for single installs. (In reply to comment #1) > - Finish button should be activated once one product has been selected. Currently the Finish button is only enabled when the user has agreed to licenses. How do you propose the UI would enable users to accept licenses? > - The Confirmation page should not be shown, especially if one product has been > selected. The confirmation page is important in that it allows people to deselect optional components for solutions with multiple features and it facilitates error/warning display and resolution in the case where the provisioning operation has errors or warnings.
(In reply to comment #2) > I understand why it's desirable to streamline the install process. Personally > I'm in favor of enabling multiple installs, since this is my most common use > case. Others may differ. David, can you describe the use case for multiple installs. The use case I see for the single install is a developer who uses Eclipse as an IDE, looking to search and discover a tool to accomplish a task, once the found a solution they will want to try to install and test. The emphasis for me is on the search, discover and install. > > A middle-ground might work well -- for example, pressing install could take the > user directly to the next wizard page (as if they had pressed Next after > Install in the current design). This would make it possible to press Back to > select more solutions. It would be less than optimal for multiple installs, > but would be easier for single installs. This might work? > > (In reply to comment #1) > > - Finish button should be activated once one product has been selected. > > Currently the Finish button is only enabled when the user has agreed to > licenses. How do you propose the UI would enable users to accept licenses? I think of Finish as being finish the search and discover steps. Finish means to start the install. Activating Finish after the license accept seems like you are already at the finish of the process? > > > - The Confirmation page should not be shown, especially if one product has been > > selected. > > The confirmation page is important in that it allows people to deselect > optional components for solutions with multiple features and it facilitates > error/warning display and resolution in the case where the provisioning > operation has errors or warnings. I understand the issue of handling errors and warnings but for a single install I am not sure the option to deselect is that valuable for most cases?
Per our discussion on the call the wizard will be modified so that the *Install* button will advance the wizard to the next page (as suggested in comment#2) Suggestion that the wizard page description indicate that the back button will allow the user to select more solutions.
implemented
Created attachment 170039 [details] mylyn/context/zip
(In reply to comment #5) > implemented Are you sure this got implemented? I don't see if working as we discussed? It seems like it is the same workflow?
reopening
Crap, I just realized that you marked this fixed today, so I assume it is coming in RC2. I will check then.
:) It's in RC2
