Just don't lose track of what the Component Reference is ... a reference. Just because the other docs (dev guide and tutorial) are weak doesn't mean everything should be piled onto the Component Reference.
I myself use the reference to remind myself about parameter names and the like. More effort needs to go into the Tutorial as the primary way to get up-to speed in Tapestry. I don't think the Component Reference can ever fill this role, nor should it. -- [EMAIL PROTECTED] http://tapestry.sf.net > Component docs with complete copy/paste examples would be great. If the > example files were packaged separately and linked in the docs, that might > be even better, since Tap. Veterans would not need to slog thru > them. Understandably, components that access external resources could not > have complete examples. > > The comment was made that the component docs don't need examples since > developers would reference them only after obtaining a complete > understanding of Tap. from the Dev. Guide. I *strongly* disagree with > this. Tap. was going very slowly for me. I decided that this was due to > the fact that I did not have an application in mind for it. Without a > project, reading the Dev Guide just doesn't sink in -- so I invented a > project. Armed with my bogus project, I'm learning much faster, but I am > not learning in the order mandated by the Dev Guide; The component docs > are now my best reference. > > > Thanks all, > > Eric Everman > > > At 11/3/2002, Malcolm Edgar wrote: > >I've given some more thought to this. I think the current Component > >Reference format is good, especially when the Tutorial-2 comes online. > > > >Making full examples in the Component Reference is difficult, as they > >often would often refer Objects created from a database pull. > > > >There has also been a fair bit of churn in the Tapestry XML versions, > >which would need to be updated if complete .page/.jwc files were included. > > > >However creating full examples for things like the Upload would be fairly > >easy. A variation on Neils suggestion would be to include a link to an > >example .java/.page/.html files where appropriate. > > > >regards Malcolm > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, November 18-21 in > Las Vegas (supported by COMDEX), the only Apache event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
