[drupal-devel] two minor usability issues, introduced recently
killesreiter at physik.uni-freiburg.de
Sun Sep 25 18:23:38 UTC 2005
On Sun, 25 Sep 2005, Larry Garfield wrote:
> I fully agree that the split and un-standardized configuration
> screens are a major usability pain. Also along the same lines is
> that I routinely go to settings when I should be going to modules,
> and vice versa. I'm not sure which I do more often but I think it's
> going to modules first when I want to get to "a module's settings"
> (as opposed to "the settings for a module").
> Currently it's possible to put the extra config screens for a module
> under the settings/modulename location, as a LOCAL_TASK. It's not
> documented as such, but I believe it's a good idea in many cases.
> They don't get the settings form magic, but who cares?
As I developer I usually decide where I put my config screen by a simple
rule of thumb:
- if it is only a simple setting which the settings form magic can cope
with, I use the settings hook.
- anything more complicated gets its own screen.
No, I am not defending this, just stating my current practice. I am
pretty sure that other developers handle it similarly.
More information about the drupal-devel