Shawn Walker wrote:
> I think that most users are going to ignore a relative complex message
> like that.
I agree. It is just a bit difficult in email to show a [Details]
button that, when pressed, presents a list/table/... of "why", so
I simply showed them together. Obviously, if the info is available,
the GUI can choose to present it in many different ways.
> However, I would strongly discourage
> attempting to dynamically build a sentence
I also agree with this. My point was that you do have the
dependency graph, so you certainly can walk it back to the
package(s) or incorporations that triggered the reboot-needed
state; producing a readable list from that should be easy.
I see this being most useful with well built incorporations;
if you install the "[EMAIL PROTECTED]", you don't need to
reboot, but if you install "[EMAIL PROTECTED]", you may.
(it may be "good enough" to indicate "reboot *may* be needed"
and not "we are absolutely certain, based on a detailed
analysis of your system, that you will *have to* reboot".)
> As Bart and others indicated before, we can't provide this information
> anyway until the imageplan has been evaluated.
I think we have a conceptual problem here, then. This design
and/or implementation forces the user down an awkward path that
is likely to generate complaints.
I have a specific use-case in mind. I'm thinking of a Windows
Update or MacOS Software Update like scenerio that pops up with
a list of 2 or 3 product-focused updates:
New updates are available:
MySQL Update
GNOME Update (user logout/relogin is required)
VirtualBox bugfix
NetBeans service pack
ZFS security patch (reboot required)
I would *expect* that each of these would come with an indication
in the GUI that tells me that, if I choose to install that one, a
reboot would be required. Waiting for the user to click (install
now) before informing them of the consequences is (IMO) going to
be a significant user dissatisfier.
This may be a different use case than you are designing for - most
of the discussion and code I see today focuses on long lists of
packages, and not on shorter lists of "Products". (see the linear
list of thousands of packages on http://pkg.opensolaris.org/status)
-John
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
