Module system names should be on admin/build/modules, as well as UI names

Attached, find two patches.

The first (system-admin-inc.193034.patch) satisfies the request raised with this issue as it renames the module 'Name' column to 'Module Name', and adds a new column called 'System Name'. Further, 'System Name' is populated using the path of the module.

As feared, this solution does clutter the system module list, therefore I am including an alternative patch (system-admin-inc.193034-alt.patch) that leaves the columns as they were, however, hovering your mouse over the module 'Name' causes the module path to appear in a pop-up.

The alternative patch has the advantage of not adding clutter to the system modules page, though it does have the disadvantage not being searchable.

Note that the alternative patch is complemented by an update to system.module (system-module.193034-alt.patch) to provide help that reveals the otherwise hidden feature.

These patches all work. Thanks galapas! If people like what they do, they're ready to be committed.

I'm still holding out for, somewhere -- maybe right before or right after the description, so most of the time we wouldn't even be taking up any more space on the page, vertically or horizontally, having just the system name (without the path). The path, which now that I've seen it on the modules page thanks to galapas' patch, is awesome to have but could be a pop-up, since there's not really any call to be able to search for it.

I tried to make a patch that did this, just a variation of galapas', but I screwed it up somehow. I'll try again in a day, several deadlines to make first.

Yes– and I think the best solution is the system name (without path) somewhere where it takes the least room, with the path as a pop-up ;-)

but accept other reviews. did not mean to change the status

I don't like this. It's not useful. It makes the UI confusing.

+1, I not only love this, I need this. System names of modules are very hard to find out without opening a shell, and finding out where the module is (the equivalent of "which" in Unix) is impossible without doing so - and looking at {system} if the module is installed in multiple places.

If four columns are too much clutter, consider removing the version column, which is only useful if you are neither using update status nor CVS to keep your modules updated.

One year after the last patch, the code has completely changed. I therefore rewrote the following variants:

1. Adding a separate column for the module's filename
2. Using a combined column for both the module's filename and the version
3. Using a combined column for both the module's filename and the version + adding a hover with the complete path of the module

Enclosed are 3 patches and 3 screenshots (including 'as-is' but not the hover version).
Now this is really CNR...

The last submitted patch failed testing.

I prefer the combined view as well. I wonder if we should also use the small font size for the combined column? No real preference, just floating the idea.

Hover gives the path. Not needed for search, but a big bonus in letting you know exactly what module is in use (a module could be located in profiles/example/modules, sites/default/modules/, or sites/all/modules for instance).

The occurrence of the problem is frequent for anyone who builds or maintains a Drupal sites with many modules. Modules file names (which are your main reference for the module in the Drupal.org project path and when you download or use Drush) are equivalent to the system names, so it is key that they appear, and be searchable, on the listing page. Over the version works very well (echoing the tar file packaging) and makes good use of space.

Here's a small tweak to remove the ".module" file extension from the display. (Using substr– there's probably a better way, but at least you can see it, slightly de-cluttered.)

^{benjamin, Agaric Design Collective}

The last submitted patch failed testing.

Here's a patch that does three things:

1. Adds the module key to the version so you get "blog-7.0-dev"
2. Moves the version column over to the right
3. Makes the font smaller and lighter in color, and aligns right... Should I align the table header right too? looks a little of balance

I like this because it unclutters the module name and description, AND gives me the full package name, so I think it solves both problems described here.

I also just think it looks better. The specific version information isn't all that helpful except in specific situations. This makes just browsing and visually searching the modules page easier on my eyes.

I am still convinced that this patch adds a lot of clutter (making it gray, doesn't account for the 100 words + column more on this page), especially concerning all of the new ideas that are for this page that might be more in line with the workflow - we should really find a way to fix this without this method.

I like this idea best out of the ones proposed so far. Mainly because it doesn't add another column, and only mimimal text. Its definitely a step up from the current ui, even if there could be a better alternative still.

First off, it doesn't add a column it just moves it.

Secondly, I think this page could use a multitude of enhancements.

Some information I think we should add:

1. Multiple modules found: If there are multiple modules found in various directories, it should at the very least indicate that, and show which copy of the module is being used.
2. Update status: If there is an update available it should show that here.
3. Link to project page: There should be a link to the drupal.org/project page.
4. Module Search: If the right Jquery is used, we could add an AHAH search to quickly filter the list down to what we're looking for. If this method is used, we could hide the version info altogether if we coded it to search that too. Note: I do understand that if we do this, we should provide the proper non-JS fallback code.

Of course, adding all of this extra information would clutter up the form. We should try to keep this page as simple and clean as possible if we are say we believe in making things easy for novices.

This issue is probably best merged with #363319: Redesign module page ...

I think any more work on this should be part of work towards a total redesign of the modules page.

Let's keep this issue for now. This is a small, focused usability win, whereas the other issue is a very big change.

And, last mention until D8 dev begins... as a general principal, i don't think we should veto small wins on the basis that a much bigger win is necessary. That said, the disparity between the *projects* on the admin/reports/updates page versus the *modules* on admin/modules makes me think that lacking the project name, rather than the module system name, is the key usability issue. So enforcing grouping by project (the lowercase end of the d.o/project/namehere path, not any fickle changeable title), and turning package into a tagging/sorting option is a better fix...