-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would agree with this comment. I've just read Geoff's huge email re "Spindle, the *very* future" (well, ok, I summarised it a bit there :-).
I was actually just thinking that a middle ground might be to have a field mapper in Spindle, that allows you to join the components specified in the .page/.jwc to the underlying object. Nothing fancy - this one is pure 'make it easier' support for the user. I can imagine something like the Palette component, with the component id's on the left and available bean properties on the right. Click .... click ... click, done. Sure, more editing would be required to setup additional validation properties and the like, but at least this may go some way to assisting new people? (of course, the new tutorial will as well... when I complete it :-) Neil On Thursday 10 Oct 2002 6:54 am, Richard Lewis-Shell wrote: > I would like to suggest that anonymous components might not make Tapestry > simpler to learn. By adding anonymous components, you will be telling > newbies that there are two places to look for a component definition, > instead of just one. As I see it, the distinction is quite clear. Sure it > took me a while (in the WO days) to figure what goes where, but now I'm > there, I really like being able to see an exception/error report, and know > exactly which file contains the error. Full credit must go to Tapestry's > error reporting - top notch. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9pWVzLXcfQF3yrNoRAqEbAJ9xF4e7+i2UrKharpI0edhQj5UpugCdFVf9 qnhRWie55goG/52pDjKQYPY= =d64n -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
