<div class="gmail_quote">On Tue, Dec 15, 2009 at 11:17 AM, Simon Lessard <span dir="ltr"><<a href="mailto:Simon_Lessard@dmr.ca">Simon_Lessard@dmr.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
<div dir="ltr">
<div dir="ltr"><font color="#000000" face="Arial" size="2">Well, I did need them in every single project I worked on in the past 4 years and web designers do use them. Anyway, I guess I'm in minority here so I'll drop the issue and we'll just create our own taglib internally and for us and our customers and not the use (or rather continue not using) the h: namespace.</font></div>
</div></div></blockquote><div><br>I don't think it's such a bad idea for a component library (I welcome it to be open source) to implement every HTML tag. Then, users have an option to use it, and that's great! I wouldn't want it in the standard HTML tag library because it is too easily perceived as being a burden and requirement (we would really catch flack for it then). But there is no reason to hide it internally. Using a component library certainly doesn't mean you think JSF is deficient. Really that's the whole idea (I'm probably speaking to the choir here). <br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>