That looks great! I'm sure tacos can benefit from working with it, but the only problem that I'd think tapestry would have would be navigation. It may be a personal peeve, but I don't like the idea of people having to navigate "away" from the main site to see the component docs.
To do something that would make it tap friendly would probably require generating xdox files instead of just html. Tapestry 4.1 is supposed to be moving towards using maven docs which are xdoc based I think (something-doc at least... ) . Does this sound unreasonable? Eithery way it looks really nice and would be a ~huge~ benefit for tapestry as anything that makes writing documentation easier is a big plus imho. jesse On 3/6/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: > > Hello, > > I'm actively working on TapDoc, you may check out the progress at > http://www.erinors.com/product/tapdoc/sample/index.html. > What's new: > - javadoc-like layout for easier navigation > - indicate component visuality (allow visual sample in case of visual > components, see Framework:RadioGroup for an example) > > What I'd like to do before release: > - @Parameter annotation support (almost done) > - Ant task > - user's guide > - wrap long default values (like in case of > Tacos:Autocompleter/listItemRenderer) > - code and XSLT template cleanup > > Future plans: > - handling hyperlinks in descriptions > - allow external linking to component docs > - include as many things as possible in the generated documentation > (like injected objects with links to hivedoc, referenced components, > referenced libraries, embedded components if any) > - include the XML template(s) in the docs (if any) > - examples (with live view by linking to a running tapestry app) > > If you have any comments or have an idea just e-mail me! > > Regards, > Norbi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
