This looks like a great head start. On 8/6/05, Norbert Sándor <[EMAIL PROTECTED]> wrote: > I have successfully used TapDoc to generate skeleton Forrest XML files for > the Framework component reference. I attached the output files. > You are right that it is not trivial to automatically generate documentation > because of links, etc. > But it would be great :) > > The current state of TapDoc helps also to build the docs more easily: > - Component and parameter descriptions should be copied to the jwc files > - TapDoc can be used to generate skeleton Forrest XML files > - Custom parts like "see also" and examples should be manually copied to the > XMLs currently. But it would not be difficult to merge the generated XMLs > with static hand-written ones (eg. example sections), so copy-paste could be > eliminated. > > I would help (if you accept it) in: > - copying documentation from current XMLs to component specifications > - generating Forrest XML skeletons > > BR, > Norbi > > ----- Original Message ----- > From: "Howard Lewis Ship" <[EMAIL PROTECTED]> > To: "Tapestry development" <[email protected]> > Sent: Saturday, August 06, 2005 4:43 PM > Subject: Re: [IMPORTANT] Community effort to supply documentation > > > As appealing as that is, there's also examples, hyperlinks, > cross-refererences to other classes and components, etc. > > >
-- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
