The UI and interface are a separate issue from the underlying
capability, IMO. The power.conf thing is clearly crap, and should be
replaced. I agree with Randy that we should not remove the capability
if it is useful. I also would therefore object to removal of the sole
interface to configure a feature *unless* an alternative were made
available.
That said, I doubt anyone is using autoshutdown in production, and if
the underlying implementation (and not just the UI) needs to be
scrapped, then I think we can make an exception here and allow for the
complete gutting of the feature *and* the UI associated with it --
provided you remove both together. It might be acceptable to do this
even understanding that a future integration might restore the basic
functionality in some improved (and more likely to be used) form.
Again, this would be an exceptional case, permissible (or at least
not-necessarily contentious) IMO only because nobody is likely to be
depending on the current implementation of the feature.
- Garrett
On 04/20/10 07:45 PM, Randy Fishel wrote:
Obviously Bart is on this list, and I know that Garrett is, and
there are also other smart and/or senior folks on this list. Please
feel free to chime in on the following process suggestion.
For the most part, we should just remove power.conf from the
discussion. At best it is a poor interface, and as Bart also suggests
"Trying to design your way to a correct interface from the current
pile is pointless". It's demise will come as a natural evolution to a
proper set of interfaces.
Start by defining how the "new" UI should work on a small set of
controls we know well and know will continue to be needed going
forward: CPUPM and Suspend/Resume. At least limiting ourselves to
things we know well should help shake out potential issues with the
interfaces.
After we define the new interfaces/controls, we can then go back and
remove the old interfaces/controls as superceded. The new interfaces
being more obvious and (hopefully) better.
Once we shake down the issues with the new UI (and I suspect there
will be several), then we can look at adding controls to other
features. And when we have exhausted all the desired features within
power management, then there is no longer a need for power.conf and it
can just die as well as anything that is remaining within it (OK, it
will be a last ARC case, but it will likely be another
closed-approved-automatic, and this can finally be laid to rest).
Thougts?
---- Randy
_______________________________________________
pm-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pm-discuss
_______________________________________________
pm-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pm-discuss
