Magnity invited me to post my thoughts here about the Storm UI. What I found is drawn from the demo at http://drupal6storm.beta-web.co.uk/, so I'm not sure whether these findings are configuration issues there or opportunities for improving this module. I'm also aware that many of the latter issues in the UI may be actually missing features in other Drupal modules.

Find attached my 6 pages. Looking forward to your feedback.

CommentFileSizeAuthor
Improving Storms User Experience.pdf167.28 KBjoergvk

Comments

Magnity’s picture

Magnity commented

@joergvk, thanks for dropping by with your comments. I've taken a read through and your points seem quite sensible. Do feedback on whether you end up using Storm.

When I get a minute, i'll think through a few solutions for these problems and post as separate issues.

Also very open for comments from other users...

jurgenhaas’s picture

jurgenhaas
he/him
Primary language German
Location Gottmadingen
commented

The above document is a great analysis and description, we've had very similar experiences here and therefore developed the extra module http://drupal.org/project/storm_dashboard which is addressing lots of those issues. Maybe @joergvk you want to give this a try too and give us feedback on that in a similar way? We're always looking for areas of possible improvements and our feedback is more than welcome.

Magnity’s picture

Magnity commented
Version: 6.x-1.9 » 6.x-1.x-dev
Status: Active » Fixed

Split the following so that each can be dealt with separately:

#671164: Move '+' links in table headers
#671172: Ensure table headers are logical and consistent
#671186: Differentiate between lists linked from dashboard and node views

Some other of the points have been wholey or partly covered by other issues.

Hence this (now meta) issue is now fixed.

Thanks again to @joergvk for spending the time to think about these things.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.