Posted by tstoeckler on June 6, 2010 at 1:39pm
6 followers
| Project: | Libraries API |
| Version: | 7.x-1.x-dev |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
This patch implements a UI for Libraries at /admin/reports/libraries.
The code can probably be cleaned up a bit, but I guess the basic layout/design needs to be decided upon first.
This depends on #719896: Add a hook_libraries_info().
Screenshot attached. I just enabled the test module from #719896: Add a hook_libraries_info() and visited /admin/reports/libraries and that's what you see.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| libraries_ui.png | 53.35 KB | Ignored: Check issue status. | None | None |
| libraries_ui.patch | 3.95 KB | Ignored: Check issue status. | None | None |
Comments
#1
OH!
There has been some discussion around Wysiwyg's UI already: #487690: Improve installation instructions
#2
Great, will look into that. I hadn't looked into WYSIWYG at all so far. Initially I just wanted something to test #719896: Add a hook_libraries_info(), but then I liked it enough to roll a patch =).
#3
I know this isn't particularly high on the list currently, but I needed to do something soothing :)
This implements the concept of one centralized libraries overview at admin/reports/libraries (similar to drush libraries-list) and detailed per-library installation instructions.
Just turn on libraries_test.module and visit admin/reports/libraries.
I could of course provide screenshot, if needed.
#4
a screenshot would be nice...
#5
Bump. Anything more on this? A UI seem critical to end-user troubleshooting...
#6
Patch broken... I think it should be the module defining the Library to provide the UI on this. I could be convinced other-wise though.
#7
Here's a re-roll (wow, this was still a CVS patch...).
I also attached some screenshots, which, at this point, are more important than the patch.
There are a bunch of things wrong with the patch code-wise, but I think we should settle on something desing-wise first, and then we can nit-pick the code.
I attached a screenshot of the Libraries overview, and two example screens of a library that is installed, and one that is missing. There are similar screens for libraries that e.g. have an unsupported version.
#8
Don't really have time to test this right now, but just wanted to say THIS IS AWESOME!!! :-)