<div class="gmail_quote">On Sun, Dec 13, 2009 at 4:56 AM, Martin Marinschek <span dir="ltr"><<a href="mailto:mmarinschek@apache.org">mmarinschek@apache.org</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;">
Hi Dan,<br>
<div class="im"><br>
> I think he might have just been too lazy (or bored) to rip it out. The<br>
> pass-through is a different argument from jsfc. I think jsfc is completely<br>
> and utterly useless. I see no value in it. I do see the value in the<br>
> pass-through for quick stuff. But even then, all that is being passed<br>
> through is the xml and doctype declaration, and the CDATA, all which happen<br>
> to be causing us issues with IE. (Remember, I'm not objecting to passing raw<br>
> HTML tags straight through, that is why Facelets is so successful. I'm<br>
> talking more about the document wrappers).<br>
<br>
</div>no, I don't think so. Tapestry is built completely around this idea,<br>
so there is definitely people out there who think there is some value<br>
in this - not that I personally think it makes sense if you start<br>
using more sophisticated components. For the simple components, it has<br>
some merits for a fairly large user-base (which is not the JSF<br>
community).<br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
That said, I would much rather have a nice IDE supported WYSIWYG<br>
feature that works for all the component sets than this preview<br>
support.<br>
<br>
In any case, disabling this is not necessary for what you have in mind<br>
- and I definitely support your suggestion. Just saying that we should<br>
still leave the other option open as well, and we will need to do it<br>
for backwards compatibility anyways.<br></blockquote><div><br>I'll admit I'm being a bit overly dramatic to drive the point home. jsfc does
show okay in a demo and trivial case, so I could probably live with it staying there (if
we can confirm that it is officially part of JSF 2.0, as David pointed
out). But David brought up the point that I didn't get to (thanks
David) that once you start breaking up your page into templates, it
really because useless, and to some degree it is misleading to teach
jsfc. In general, we could just go with a soft change in that we
recommend that you don't use it (because you will eventually realize
you can't use it) but leave it in there for those that like it.<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>