I wanted to replace the download buttons with links, so I could see what I was getting into before I clicked. One thing led to another, and I ended up changing several things on the releases page.

The attached experimental patch makes several changes to the layout of the release monitor page (http://example.com/admin/build/releases).

  • The project description is moved into the same column as, and below, the project name.
  • The major and minor release columns are combined. Available releases are marked "major" and "minor", and appear one over the other if both are available.
  • The download buttons are replaced with links.
  • An option is added on the settings page (http://example.com/admin/settings/releasemonitor) to hide the descriptions, making the releases page more compact. This especially makes a difference when CVS information is displayed.
  • The column headings are tweaked a bit.

Partly to understand better, and partly to get variable access to some previously constant string fragments, I also ended up refactoring some of the code in function releasemonitor_page(). As a side benefit, now no string in that function gets assigned more than once before it's output. As far as I can tell it's functionally unchanged, just more straightforward.

CommentFileSizeAuthor
ui_rearrange.patch5.61 KBewhipple

Comments

douggreen’s picture

douggreen commented

Thanks for the suggestions. I originally had a like interface, and a user said that it was too confussing, which led to the buttons. I installed it and had a quick look, and I agree that it looks cleaner. But I need a little more time to review than I have right now.

A quick question, could you do everything (other than the description option) with theming?

ewhipple’s picture

ewhipple commented

Could one do that? Well sure, assuming I know what you mean. If you had full control of the .css, and you're willing to assume a CSS-competent browser, you could even handle hiding the descriptions. On the other hand, I might be tempted to use JavaScript, just because I'm a little less ignorant on that side, and there's more browser support.

There would still need to be code changes in the module, for the sake of embedding fewer presentation-related assumptions in the structure of the output.

Or did you have in mind php templates and whatnot? I would think yes, but I know even less about that.

Could I do it? Well, I'm not sure. My Drupal experience and my keyboard time are both limited, and I should focus them on the module changes and additions I need for the site at work. If it were a matter of you already knowing what to do but not having time, so you could point me in the right direction, I guess I could try. I do need to concentrate on getting some other modules ported to Drupal 5, though.

Andy Ramblings’s picture

Andy Ramblings commented

another idea, if possible, is to have the button/clickable areas open a new tab or new window, instead of opening in the current window. Otherwise a very neat product.

It would work brilliant with Module Installer

Thanks for the module.

Andy

douggreen’s picture

douggreen commented
Status: Active » Closed (duplicate)

Even though this was the first such request, I am closing it as a "duplicate", because I used the patch from 121004.