Hi, I'm pretty happy with what I've seen of the Click framework so far -- it's actually the ONLY java framework I've yet found (and I've used/evaluated most of them) that comes close to doing things in a logical and sensible way, according to my sense of logic and sensibility.
One strange design decision that I don't understand however is why ordinary components can't also use the same elegant auto-mapping of java-to-htm files that the Page classes use. I assume I must be missing/overlooking something, so maybe someone can clarify. Section 3.7 of the User Guide presents what to me are two rather unsatisfactory approaches to custom-rendering a Form -- it says you can either create a custom template for the entire Page on which the form is used (meaning the Form's presentation can't be reused elsewhere else), or you can programmatically embed the display code in the Form subclass itself (which throws away all the nice benefits of a dedicated view template). But why is it only Pages that can be auto-mapped to view templates? Why can't individual components also auto-map (or even manually map) to their own template, so you can reuse them anywhere without having to redefine their display? For example, you could define the class MyEmployeeForm extends Form, and then have a template called my-employee-form.component.htm which controls its display. That way you can include it in anywhere in a Page template with the simple $myEmployeeForm syntax. It seems so straightforward that I assume I must have misunderstood something and this is probably already possible. Can someone point the way? Thanks
