Patch: Basic Views2 integration
yhahn - January 4, 2009 - 09:46
| Project: | API |
| Version: | HEAD |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Jump to:
Description
I've added preliminary Views 2 integration for API. Currently it adds integration against api_documentation as a new base table only -- there is more work to be done for sure. I've also provided an exported default view and integrated it against hook_menu() such that all of the main object listings (functions/files/groups/etc.) have now been replaced by Views functionality.
Full tarball attached since a patch would be somewhat silly given many new files and a new directory.
Patched against CVS checkout of HEAD on Jan 4.
| Attachment | Size |
|---|---|
| api_views.tar_.gz | 25.46 KB |
#1
I don't like significantly switching around code without a clear win in the UI or otherwise. What are the big wins this gives us? I do think the listing pages do need an overhaul. What new UI is possible with Views and how will this make developers more efficient?
I won't consider committing this until the existing API module is stable and branched for Drupal 6. Giant new features have too much of a tendency of ruining stability.
#2
Hey drumm,
That's perfectly understandable that the Drupal 6 API branch should become more stable before adding this in.
Just to let you know I'll be running this out further locally. The main big win is that this allows the API module to be more flexible and used for other use cases other than strictly api.drupal.org. It also allows many things (the fields on listing views, adding exposed search filters, etc.) to be overridden without any need to architect things specifically into the API module.
As we're working on a project that is making use of the API module but needs further customization/integration with our user story, Views is a huge win here.