\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\tableofcontents

Horde\_Rdo\_FormBugsPeopleDescriptionComments

\part{Horde\_Rdo\_Form}
Autogenerate Horde\_Form objects

\section{Bugs}
List any tickets on http://bugs.horde.org/\footnote{http://bugs.horde.org/} that cover this issue or are relevant to it.

\section{People}
Duck duck@obala.net\footnote{mailto:duck@obala.net}

\section{Description}
Extends RDO and Horde\_Form to autogenerate basic CRUD forms (create, read, update, delete) based on the metadata already available in RDO.

\section{Comments}
I doubt this works as intended without adding new meta information. I use Rdo quite extensively but a database schema or even an Rdo Mapper won't tell you if a 1-digit integer is a checkbox, a radio or an enum of 0 and 1 (and possibly 2-9). Not every limited-choice field like a multiselect or an enum dropdown is stored in a limited-choice database field - a varchar may be just right or reasonable because the limited choices are entirely based on application state.

-- Ralf


\noindent\rule{\textwidth}{1pt}
Back to the Project List\footnote{http://example.com/index.php?page=Project}

\end{document}
