[development] Early Drupal 6 review from Chris Messina

Shakur shakur at techarena.co.uk
Mon Nov 12 13:49:06 UTC 2007

Guys, Greg is using the pathauto module as an example of UI that
contains to much info whether he should allow things to go allow
features or not is really beside the point.
What we talked about and the aim of his email was...how does cutting
down of interface's by removing rarely used UI's sound
e.g. in the comment setting page[1] there is frankly too much info which
right allows a use who knows/wants to configure how comments are set to
do so, but the truth of the matter is with most users the default
setting suffices and all they care about is whether comments should be
allow or not (default comment setting)...so why cant we remove those
options we think are to detailed and have a variable setting in one
place (setting.php?) whereby advance users can turn those on?


Gerhard Killesreiter wrote:
> Greg Knaddison schrieb:
> > On Nov 12, 2007 6:10 AM, Xavier Bestel <xavier.bestel at free.fr> wrote:
> >> Options should be:
> >> - thrown away if useless (e.g. don't ask me to enable a feature, I
> >>   have enabled the module already).
> >> - detected automatically whenever possible (and thrown away).
> >> - rationally grouped together when they must stay.
> > How about one more option on that list:
> > - Hidden, but configurable by admins
> > I am quite embarrassed by the current pathauto admin settings page.[1]
> > It is _insanely_ long.  But many people have begged to have those
> > features added so I can't just drop features.
> IMO part of being a module maintainer is the task to say "no" to
> requested features if they aren't generally useful.
> Cheers,
>     Gerhard

More information about the development mailing list