Drupal 5

In Part three of our CCK field widget tutorial, we will finish our skeleton module and create our default formatter. Implementing a Formatter requires implementing hook_field_formatter_info(), hook_field_formatter, and usually a theme callback, so theme developers can override the HTML output of the formatter if necessary.

hook_field_formatter_info
Like our previous info hooks, this hook returns a simple array, keyed on the machine readable name of the formatter and has an internal array of the fields the formatter can be applied to.

<?php
/**

Now that we've defined our Data Layer with the field hooks we can move on to widgetry. We're only going to assemble one widget for this part, the manual input widget. We will cover advanced widgets in Part 4. We've got three hooks to work with again hook_widget_info, hook_widget_settings, and hook_widget.

You do not have to implement widgets with your field module, but you should probably provide at least one widget by default.

hook_widget_info

We begin our Journey in to CCK 1.x Wonderland by defining a field. Developing a CCK Field requires working with three systems of hooks: Fields(Data Model), Widgets(User Interfaces/Field Input), and Formatters(Ouput).

We're going to start with Field hooks, since they let CCK know we offer a field.

hook_field_info
This hook lists the fieldtypes implemented in our module. It returns an associative array of machine readable names and human readable labels for each of the field types implemented in the module.

<?php
/**
* Implementation of hook_field_info().
*