[development] Being noisy on installation...
victorkane at gmail.com
Fri Apr 11 10:25:14 UTC 2008
Well, we should handle the noise in the same way Linux does: on the one hand
there are switches for noisy (-v) and quiet, and on the other, all utilities
provide comforting messages for the newbie by default, which more
experienced hands, justly horrified by so much need for calming insecurity,
know how to send to the bit bucket for automated or cron run processes via a
redirect to /dev/null.
Since this whole discussion seems to have evolved into a "how to improve the
module installation process" or even "what should our module installation
process be like", I think it should incorporate this time proven
administration pattern: provide switches for noise levels and have the
option to send all output to the bit bucket, but for heaven's sake, keep the
warm and fuzzies for the newbies!
On Fri, Apr 11, 2008 at 12:06 AM, Jeff Eaton <jeff at viapositiva.net> wrote:
> I'm also opposed to this -- vigorously. Having built a number of custom
> profiles and related solutions for clients, it is a *pain* to have those
> modules splattering their messages all over during a carefully managed
> chx and I actually tried to get drupal_set_message() moved out of submit
> handlers as well, so that automated form processing wouldn't do the same
> thing, but we ran out of time to push through minor features like that.
> On Apr 11, 2008, at 12:28 PM, Morbus Iff wrote:
> and saw one of my personal pet peeves jump out: "Even if your module
> > doesn't have need of a hook_install function, it's nice to Display a note
> > confiriming that the module is installed and ready for action." Core doesn't
> > do it at all and, as far as I can tell, it originated with Views (which most
> > folks take as an admonition that It's Right).
> > Thoughts from the peanut gallery? At first blush, I'm horrifically
> > opposed to it, because I think we have enough to worry about then reading
> > /successful/ messages - I'd much rather Drupal interrupt me when something
> > /bad/ has happened, not when something I /expect/ to happen actually
> > happened. But, playing my own devil's advocate, I could say that "well,
> > there's precedence already - we always inform the user when something has
> > been created, updated, or deleted successfully".
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development