On Wed, 29 Dec 2004 13:59:17 -0800, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On Wed, 29 Dec 2004 16:50:51 -0500, Sean Schofield > <[EMAIL PROTECTED]> wrote: > > [snip] > > Probably a little bit off topic, but I wanted to respond to your > > theory. If your theory is correct, then yes, JSF is a dead-end. I > > don't agree with that theory, but I'm not sure that JSF will be the > > next step either. That will depend on how fast developers evaluate > > and then adopt the technology. And that will depend on how fast JSF > > evolves to address various issues (see an earlier post of mine about > > current JSF limitations.) > > Assuming that JSF and "highly dynamic" apps (i.. where a high degree > of interactivity happens on the client side via DHTML and JavaScript) > are mutually exclusive is too simplistic. The standard components in > 1.0/1.1 don't help you do this sort of thing, but there are already > JSF component libraries available that do. Such libraries use the JSF > components to persist the page author's design decisions (i.e. set the > correct attributes on the correct tags or whatever), rather than do > the actual rendering -- so they still fit nicely into development > tools that know how to manipulate components.
Toolkits like FacesClient Components and ADF Faces are a step in the right direction, but they do not address most of the things I mentioned. At least as far as I'm aware, neither can handle drag and drop in the browser, real time updates, or wizard pages in the client. They do handle some of the simple cases for dynamic apps, but they don't tackle the hard problems. When you get to more complex components, and more complex interactions, I don't see how this is going to be handled in a way that makes it make sense to use JSF. (Also, I don't know about ADF Faces, but FacesClient Components appears to commit the cardinal sin of believing it owns the JavaScript global namespace, which is pretty much guaranteed to cause problems when any other JavaScript is used in the app.) -- Martin Cooper > > > > sean > > > > Craig > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
