cck types detailed
mojzis - March 23, 2009 - 01:16
| Project: | Site Documentation |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Description
do you plan to ever include a report also on the field in cck types ?
#1
I hadn't planned on it because I think something like that would be more appropriate in #154931: Hook_sitedoc.
But I did do a bit of playing and came up with the attached picture. There is an awful lot of information available and it will not possibly fit on one row. I picked out a few items that I thought were important.
#2
#3
I'm interested in something like this as well, and am willing to work on it. But do you think it would make more sense in this module, or in CCK, or in a 3rd module?
#4
This is the type of thing I had in mind for hook_sitedoc, which would place the burden of producing this either in CCK or a CCK add-on (which might be distributed with this module). However, with Fields now being in core, I doubt the core developers would be thrilled with supplying data to a contrib.
#5
The great thing about properly defined hooks is that anyone can feed anything to anyone on another module's behalf. :-)
I don't know why there would need to be any extra feeding done, however. The majority of the data needed can be gotten from the CCK tables directly. I'm half tempted to just views-ify them, but I'm not sure that would give us the UI we'd want.
#6
The intent of hook_sitedoc was to allow other modules to say what was worthwhile to include in the report. One example might be for CCK to show information about fields within content types. Another might be for Views to detail what views were available. There might even be something that DBTNG would like to document (perhaps a list of stored procedures).
Only in Drupal-land would we "views-ify." ;-)