tag:blogger.com,1999:blog-27876765.post1580950537751069294..comments2024-03-20T13:37:39.909+01:00Comments on Day to day stuff: Profict Java Summer Camp - AJAXErik van Oostenhttp://www.blogger.com/profile/15976519439979651010noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-27876765.post-32609968977398180442006-08-28T22:19:00.000+02:002006-08-28T22:19:00.000+02:00O.k. just after typing my previous post I noted th...O.k. just after typing my previous post I noted this announcement on theserverside:<br /><br /><a href="http://www.theserverside.com/news/thread.tss?thread_id=41938">http://www.theserverside.com/news/thread.tss?thread_id=41938</a><br /><br />a conference with a couple of sessions on the topics I mentioned. To bad it's located in Boston!p3t0rhttps://www.blogger.com/profile/18324685808109803611noreply@blogger.comtag:blogger.com,1999:blog-27876765.post-30654717676962402272006-08-28T22:14:00.000+02:002006-08-28T22:14:00.000+02:00Ah, thanks for elaborating ;)
Most interface desi...Ah, thanks for elaborating ;)<br /><br />Most interface designers (more specifically webdesigners) seem to have a hard time designing a good interface with the endless possibilities introduced by the countless number of frameworks.<br /><br />Also designing the interface to be 'degradeable' for non-ajax browsers (i.e. blind people using screen readers, and crawlers) seems to be quite a challenge.<br /><br />Consistency between different applications is another problem.... <br />People often complain about the inconsistency of applications for linux; they rave about inconstent ajax apps all the time....<br /><br />'integration' Toolkits like jMaki seem to be in a perfect position to enforce standarization of interface components and look&feel. But, correct me if I'm wrong, not much seems to be happening on this front.<br /><br />I discussed the above with one of the Backbase guys a while ago, but it seems Backbase doesn't have any interest apart from a commercial one. Shame on them ;)<br /><br />I'm still waiting to see a good presentation on AJAX best practices. Not only technical but also stuff like division of roles/tasks in dev teams, <br />testing (different browsers, different security settings in browsers, degradeability, handling of timeouts etc.). I know a couple of testing frameworks for AJAX, but all are far to complex and timeconsuming to fit into most projects I know of.<br /><br />Concluding: I know which stuff is availlable, I know how it works... but found it to be the most complex part of my recent/current project (due to the above) to manage.<br />Now how DO you sensibly use AJAX on a project without going over budget?p3t0rhttps://www.blogger.com/profile/18324685808109803611noreply@blogger.comtag:blogger.com,1999:blog-27876765.post-12973057559364270502006-08-27T21:22:00.000+02:002006-08-27T21:22:00.000+02:00Given the amount of time, the presentations were r...Given the amount of time, the presentations were rightly, but only slightly beyond superficial (well, except for the really short BackBase presentation).<br /><br />Though Greg's presentation focused on the widgets in jMaki, he did list the transport technologies (XMLHttpRequest, hidden frame and script tag includes) and the common protocols (XML, JSON, etc.). Both Dojo and DWR support the first two transport technologies.<br /><br />Greg mentioned Dojo's ability to show a 'loading' message. No other interaction design issues were mentioned. Peter, can you name some?<br /><br />The DWR presentation was definitely better then the DWR chapter in the Spring MVC book. The book only shows an example. The presentation also made you understand it. In addition Bram showed some of the less used features and some newer stuff.Erik van Oostenhttps://www.blogger.com/profile/15976519439979651010noreply@blogger.comtag:blogger.com,1999:blog-27876765.post-60381534566327130382006-08-26T14:03:00.000+02:002006-08-26T14:03:00.000+02:00I think it's to bad most presentations on AJAX see...I think it's to bad most presentations on AJAX seem to be a bit superficial. The presentation on DWR you describe sounds very similar to the chapter in the Spring MVC book.<br /><br />Complex problems like cancelling open requests, browser compatibility (yes this is STILL a huge issue), fallback to non xmlhttp based solutions and interaction design are often skipped...<br /><br />I do however really like DWR, it is well focussed and seems to just work.p3t0rhttps://www.blogger.com/profile/18324685808109803611noreply@blogger.com