Currently, when you view a release node that's a package containing other projects, it looks pretty bad:
http://d6.project.drupal.org/node/643523
Once you apply #645866: Expose {project_release_file} to Views for better UI of release file info it looks a little better, but it's still pretty bad:
Plus, some of the most important info is currently buried on a separate "Package items" tab:
That's no good at all, since that really needs to be more prominent. I was thinking that table should be inline on the release node, under the file info table, but that might get a little overwhelming. All of this needs some UI love, and a coherent plan for how to display all this data. We're finally to the point where it's all built with Views, which is great, since folks can tweak customize, etc. But, I'd really like to make the defaults elegant and clear, since drupal.org is going to run the defaults. ;)
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 645884-8.update_status_conditional_recommended.png | 61.97 KB | dww |
| #7 | 645884-7.update_status_conditional_recommended.patch | 10.7 KB | dww |
| #7 | 645884-7.update_status_conditional_recommended.png | 62.17 KB | dww |
| #4 | realeaseinformation.png | 84.01 KB | Bojhan |
| package-release-node-UI-included-items.png | 74.03 KB | dww |
Comments
Comment #1
dwwp.s. I'm not even sure technically how to do this in a generic way in views, but it'd also be nice to somehow describe the difference between:
*-core.tar.gz
*-no-core.tar.gz
*.tar.gz
Comment #2
dwwforgot to tag
Comment #3
yoroy commentedHey, tagging for visibility in my queue :)
Comment #4
Bojhan commentedUpdated comments on interface
Comment #5
yoroy commentedAnd:
"Releases included in this package:" can be
"Included in this package:"
I would also consider removing the second 'release' from the 'Recommended release' column
Comment #6
dww#645866: Expose {project_release_file} to Views for better UI of release file info is committed and deployed on d6.p.d.o.
I also committed and deployed most of the suggestions from #4, except the conditional "Recommended release" stuff based on the update status. That's going to require a bit more work. I'll see if I can get that done on Monday before we launch, but if not, what we have now is already pretty good. See also #645074: Provide mechanism to color-code the rows in various tables based on a field in the view -- it'd be nice to color-code the insecure and out-of-date rows.
Comment #7
dwwWoo hoo. Lots of crafty views handler hacking later, and this is working. ;) Attached patch and screenshot of conditionally showing the recommended version depending on the update status. The screenshot is a bit stale -- it's showing the icons last. They're really going to be first, I just can't take a picture of that on the test site right now since it hung while I was in the process of reloading the page. :/
Comment #8
dwwHere it is with icons first...
Comment #9
dwwAfter a few more tweaks from yoroy and Bojhan in IRC, committed to HEAD and deployed on d6.p.d.o. w00t!
All that remains now is conditional row coloring, but that's over at #645074: Provide mechanism to color-code the rows in various tables based on a field in the view. Calling this fixed.
Comment #10
dwwFYI: http://drupal.org/cvs?commit=295998
Comment #11
yoroy commentedIt's a pleasure working with you, Sir!