Our final goal is to get rid of prototype and use dojo instead as our base-library for AJAX.
So we want to further AJAXify our component set with the help of dojo, and replace the existing implementations with dojo-functionality. The problem with prototype is lacking namespacing... regards, Martin On 2/3/06, Rogers Reilly <[EMAIL PROTECTED]> wrote: > Laurie Harper wrote: > > > Hmm, OK, thanks; that makes sense. So, it's either time to start > > wrapping Dojo widgets with JSF components, or time to learn about > > Shale's remoting features ;-) > > Picking up on this- I'm just about to refactor two Dojo/JSP projects > (one work, one personal) into Dojo/Shale/JSF/Hibernate projects, and > this sliver of the stack is exactly what I'm wrestling with. My first > thought was to define a relatively narrow Dojo interface for thick > client-side stuff (letting MyFaces do simple stuff like autocompletes), > keeping the server fairly decoupled, but now I'm wondering if they can > be wired more tightly. > > Somebody posted on the Dojo mailing list about weaving Dojo libraries > into MyFaces ... it wasn't clear (to me, at least) whether this was just > for the purpose of using it for behind-the-scenes utility functions, or > for AJAX-ifying current JSF components, or for wrapping Dojo widgets as > Laurie mentioned. Does anyone know where MyFaces is going in this > regard? I expect at first I'll be doing a lot of hand-wired Shale > remoting in widgets, but it'd be great to have some idea of where to > expect "help" in the future. > > -Rogers > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
