My experience with JMaki has been bad. I've also built a fairly large app with Dojo and would not use it again because despite all the optimization build / development techniques suggested, certain files are requested synchronously that causes browser freezes. Also too many gremlins that cause a Dojo app to get very sluggish. I can almost recognize a site that is built using Dojo as soon as I visit it.
My 2c, Sanjiv On 3/16/07, VJ22 <[EMAIL PROTECTED]> wrote:
Hi everyone, Do you think it would be a good choice to use JMaki as the wrapper class for any AJAX widget in an Appfuse architecture.... I am thinking of integrating it within Appfuse.....any thoughts on this ? Reason being I do not want to have too many UI widgets cluttered across the app Design strategy: JMaki wrapper classes for any AJAX (DOJO/scriptaculous) widgets DWR for any remoting facility not the in-built ProxyXMLHTTPRequest that comes bundled with JMaki Rgds...Vijay -- View this message in context: http://www.nabble.com/JMaki-tf3412742s2369.html#a9509116 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
