| I think the approaches of the blueprint components are highly faulty-- especially with the use of dojo.bind. You are dealing with pure URI negotiation which is orthogonal to the communication capabilities of JSF. Example, the autocomplete example uses Shale Remoting via an EL _expression_-- but doesn't carry context, so yeah, you can put #{foo.suggest} but only if 'foo' is globally available which is a huge gotcha for developers and pushing the JSF solution back to where we were with JSP 2.0 and JSF 1.1 issues again with the disconnect. | |
On 4/27/06, Werner Punz <[EMAIL PROTECTED]> wrote: Yes, we've refactored the entire library of components to use dojo.io.bind for asynchronous communication. In addition, we're experimenting with wrapping DOJO widgets (such as the Rich Textarea Edtior).
Craig McClanahan schrieb: Besides having some interesting components to play with, the other desired outcome of this effort is a set of BluePrints Catalog solution entries that document best practices for building AJAX enabled components. Since the MyFaces developers are rapidly gaining experience in this area as well, it would be interesting to have you review the catalog entries that have been developed so far, and see how they stack up with your own work. (Who knows ... might even learn a thing or two as well :-). Craig | |
- Re: 'Progress Bar' component Craig McClanahan
- Re: 'Progress Bar' component jacob
- Re: 'Progress Bar' component Adam Winer
- Re: 'Progress Bar' component Craig McClanahan
- Re: 'Progress Bar' component Jacob Hookom
- Re: 'Progress Bar' component Martin Marinschek
