-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd suggest going straight to the xdocs section. When working, it's easier to just look at project specifics without having to the wiki.
(as long as it's done somewhere, it'd be a good thing) My .02 Jesse Kuhnert wrote: > That sounds like a very good idea to me. I ran across one particular > situation today where I wasn't sure what type of exception to throw for a > component parameter error. (the @Script ability to take String or IAsset). > > I'd say it should go in the wiki, but it's been performing so slow lately it > almost seems better to have it in a separate developer xdocs section. > > On 3/10/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: >> Howard M. Lewis Ship: +1 >> >> I can see that he's been active on the Tapestry lists as well. >> >> I think that with the growing number of new members, we need to take >> on some work to set coding guidelines (not standards!) and otherwise >> provide more help for those new to working on the Tapestry code base >> and community. >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEEfimaCoPKRow/gARAludAKDKHXm3EIw2EcBy7GcdTPib89pJgACg6r5C fofT9KEZqRnWetJqsvqg524= =bNZ/ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
