Community
Participate
Working Groups
Smart import should not offer special option whether to run in background. We already have a global preference for that.
+1 for this but I think Mickael had concerns that the import in background might be confusing for the user.
(In reply to Lars Vogel out-of-office until 21.10.2016 from comment #1) > +1 for this but I think Mickael had concerns that the import in background > might be confusing for the user. Actually, I have concerns about several operations in the background that can be confusing for users. Basically, for any operation that needs to be completed before user can continue their workflow (import in one instance of those), I believe it's better to present progress to user rather than presenting some incomplete or unusable state. That said, I'm also for consistency, so +1 on using the global property to decide whether to show report or not. If this is an issue in term of usability, that will be an interesting example to consider when deciding to change the global preference value.
Before we changed the default, the user got the progress dialog with an option to run everything in the background. Obviously, the other way is harder to achieve.
(In reply to Mickael Istria from comment #2) > (In reply to Lars Vogel out-of-office until 21.10.2016 from comment #1) > > +1 for this but I think Mickael had concerns that the import in background > > might be confusing for the user. > > Actually, I have concerns about several operations in the background that > can be confusing for users. Basically, for any operation that needs to be > completed before user can continue their workflow (import in one instance of > those), I believe it's better to present progress to user rather than > presenting some incomplete or unusable state. Well, for those cases, the option to run in the background should not be there at all.
(In reply to Dani Megert from comment #0) > Smart import should not offer special option whether to run in background. > > We already have a global preference for that. +1 I discussed the current behavior with several of my customers and either: 1.) They don't care (no opinion) 2.) Find the current blocking import wizard annoying I suggest we remove this extra option and use the global preference.
Jonas, this is a bit more challenging, as promised. Can you have a look? To trigger the dialog, use for example the Git repository view -> Import projects. On the page after pressing finish you see a "Run in background" flag which should get removed and the global constant from Window -> Preference -> Always run in background should be used.
New Gerrit change created: https://git.eclipse.org/r/117938
Just to document this: We have the "Always run in Background" option. Offering another "Always run in Background" option specialize for a dialog is very confusing for the end users who expects that all dialogs honor the "Always run in Background". This bug does not change the logic of the dialog, projects are either imported in the foreground or background, depending on the user choice. It just removes the UX inconsistency.
NOTE: OTHER import wizards do not allow to run in the background (even if the preference says so) for arguments brought up here. It can be very confusing for users to see partially imported state/projects.
Thanks, Jonas.
Gerrit change https://git.eclipse.org/r/117938 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=28b07a52698cefa82501c4e0efb20d2057ba55d8
