% tasklist.sty from c.t.t. of Network News
%
\newcommand\dates[2]{\leavevmode \nobreak \rlap
  {\hspace{\linewidth}\hspace{10pt}%
   \makebox[\datewidth]{#1}\hspace{10pt}\makebox[\datewidth]{#2}}%
  \ignorespaces}
%
\newlength\datewidth  \setlength\datewidth{40pt}
%
\newenvironment{tasklist}[1]%  Almost exactly like {enumerate}
{\ifnum \@enumdepth >3 \@toodeep\else \advance\@enumdepth\@ne
  \settowidth\datewidth{#1}%
  \edef\@enumctr{enum\romannumeral\the\@enumdepth}%
  \list{\csname label\@enumctr\endcsname}%
    {\usecounter{\@enumctr}\def\makelabel##1{\hss\llap{##1}}%
     \addtolength\rightmargin{2\datewidth}\addtolength\rightmargin{20pt}%
  }\fi}%
{\endlist}
%
\endinput
%
\documentstyle[tasklist]{article} % works on 209, Yes.
\begin{document}

\begin{tasklist}{date10}

\item \dates{date1}{} Design

\begin{itemize}
\item\dates{date2}{date3} Review requirements
\item\dates{date4}{date5} Review functional spec
\begin{itemize}
\item\dates{now}{never} ask a few buddies
\item\dates{now}{never} actually read spec for first time
\end{itemize}
\item\dates{date10}{date11} Staw-horse class hierarchy
\end{itemize}

\item \dates{date12}{} Implementation
\begin{itemize}
\item\dates{date13}{date14} A programmer working overnight eating twinkies
and drinking gallons of coffee.
\end{itemize}

\end{tasklist}

\end{document}

%-------------------------------------------
You may want less vertical space in the lists.  Set \topsep, \parsep, 
\partopsep, \itemsep.  Don't just change them in {tasklist}, but change 
them in the macros \@listi...\@listvi; otherwise, you can't use {itemize}
for the sub-lists.

Donald Arseneau                         asnd@reg.triumf.ca

-------------- article headings ------------
From: asnd@reg.triumf.ca (Donald Arseneau)
Newsgroups: comp.text.tex
Subject: Re: List of table rows
Date: 23 Sep 1994 00:06 PST
Organization: TRIUMF: Tri-University Meson Facility
In article <CwJDIL.BAo@world.std.com>, pd@world.std.com (Peter F Davis)
 writes...
	Working in LaTeX2e, I'm trying to keep track of project tasks and
	subtasks by creating a document something like:
	 
		TASK				BEGIN	END
		----				-----	---
	1 Design				date1
	  o  Review requirements		date2	date3
	  o  Review functional spec		date4	date5
	      o Revise based on feasibility	date6	date7
		studies
	      o	Delay priority 2 features	date8	date9
		to subsequent version
	  o  Staw-horse class hierarchy		date10	date11
