I completely agree with Jacob; this is not the path we
should be carving out in JSF. There's a better way!
-- Adam
On 4/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> 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:
> Craig McClanahan schrieb:
> > On 4/26/06, *Sean Schofield* <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED] >> wrote:
> >
> > Is there something like this in ADF faces? I haven't looked at the
> > donation yet with all of the other stuff going on but they have a
> > pretty complete set of widgets in there. I agree it would be
> > something nice to have.
> >
> >
> > It would definitely be nice to have in MyFaces. But, there's no reason
> > to be shy about using the BluePrints ones either ... they are open
> > source and BSD licensed :-).
> >
> Yes the BluePrints stuff is neat, and the license is even better.
> Btw. I have not checked the latest code, have you guys moved the
> progress bar towards dojo, the old one afair, was straight
> on top of ajax.
>
> 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).
>
> 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
>
>