As has been discussed on Friday Apr 17, 2009 we need to change Plugin manager in following way:
> * activate button will be replaced by Activate/Deactivate buttons on the
> left right, in the same area as the disable button. Column of checkboxes
> will be renamed to "Select" and both buttons will work upon selection in
> this column (the list should not allow multiselection, then)
> * Ondra will suggest different location (and possibly also form) of the
> simple/advanced switch by the end of the next week.
Dmitry is it OK if I prepare a patch (like the one I sent on Friday, plus support for multiselection) and then let you
deal with this issue?
*** Issue 162850 has been marked as a duplicate of this issue. ***
yes, please go ahead.
Created attachment 80782 [details]
Activate/Deactivate/Uninstall support checkbox multiselection and are at bottom of the dialog
*** Issue 163646 has been marked as a duplicate of this issue. ***
Ondřeji, did you find better UI representation for the "Advanced Mode" switcher? We need your advice to more further
with issue 162819.
I`d played with it a little bit an it looks fine for me (no issues). Thanks!
Jarda, Tonda, I apologize for the delay. I played with it and I came with 4 alternatives out of which I most liked the
one which is similar to the current one, only with different location of the checkbox and also a different name. 5th
alternative could be two tabs, but that doesn't very well work for same data - different views and also contradicts most
guidelines (tabs in tabs).
Let me explain why I think this is the best one:
1) Visually, it seems there is only one view on list of plugins (no switch, which would put an equal weight on both
views). Majority of our users should only need the large granularity list, and it is there available for them at the
first sight. For those who will struggle to find what they are looking for (and/or will want to disable a particular
plugin), the checkbox is at easy-to-spot location and should be the obvious way to continue if user is stuck and d
2) Location-wise, if solves the original problem (reported somewhere) that the switch should be visually bound to list
3) Language-wise, we have been talking a lot about simple/advanced view, but when trying to see this from users' eyes, a
use-case they would want to see the "advanced view" in is when they are looking for a particular pack and can not find
it. In this context, they want to see the content of individual bundles - details of individual bundles. Therefore "show
What do you think?
Created attachment 81415 [details]
advanced view switch
BTW, the left (list of plugins) and right (plugin info) panels are separated by a splitter.
In other words, user can make one panel be wide and the other one be narrow.
The "show details" checkbox should be always at the middle (by X axis), right?
"Show details" can't be aligned with the splitter - it's very problematic to implement and would IMHO look strange when
the user drag the splitter. Another issue with this is that in reality the checkbox would be quite close to the
Uninstall, Activate and Deactivate buttons (BTW the Deactivate button is missing on the picture). It might look like
related to the buttons. Is that intended?
After long and heated argument :-), we've found a solution that is acceptable by both parties. It makes clear the simple
view is main and expected, yet puts the switch into a prominent (a little nudge ... maybe too prominent? ;-) ) position.
A drawback from my point of view is that two IMO least used elements are put to the upper left corner, but it is the
only acceptable solution we can implement for 6.7.
Created attachment 81533 [details]
suggested solution fro 6.7
The new patch is attached, I`ll wait for its integration till Thursday evening so that everyone interested (Jarda?:)
BTW, it also makes a better fix for 162820 and fixes 163355.
Created attachment 81538 [details]
proposed patch due to the UI Ondrej suggested
The patch seems to be OK. It works and it follows the new UI spec.
I can have only one minor "architectural" comment. The "InitialTab" and "plugin.manager.detail.view.selected"
properties shall be documented as exported API in autoupdate.ui/arch.xml (if it existed) or
autoudate.services/arch.xml. Their stability does not need to be high friend (as welcome screen uses that) and private
(as it is only for advanced end users).
Otherwise I am looking forward to see this patch integrated.
*** Issue 162819 has been marked as a duplicate of this issue. ***
Fixed (arch.xml has been also updated), thanks Jarda for the initial patch and further reviews.
Integrated into 'main-golden', will be available in build *200905070201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dmitry Lipin <email@example.com>
Log: Issue #163411 Activate button + simple/advanced switch must have more natural place