On 3/22/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > during the last months, the desire for a more "modern" user interface > has become a major point of critique. The review in iX magazine > mentioned our "outdated" GUI, and some customers have put a GUI update > quite high on their priority list. > > It can't be denied that AJAX offers some options to simplify the user's > life. Of course there are other technologies to add more interaction > capabilities to the client, but IMO we should stick to the W3C standards > as close as possible. > > Is anyone in the developer community familiar with different AJAX > approaches and maybe could recommend a framework? Dojo ships with > Cocoon, but I have to admit that I have no idea if it's the right tool > for our requirements. Another question is if we should consider > migrating the GUI to an AJAX framework completely, or just add some bits > here and there where HTML forms aren't appropriate. > > WDYT? > -- Andreas
The free online sample of the iX report includes just the introduction. Can someone post the text relevant to Lenya? What is meant by "outdated" and "more modern"? I have been doing partial webpage updates using a CORBA Applet since 1996 and AJAX since 1999; are partial updates"modern" now technical expertise is not required? Does "outdated" refer to the color scheme now that the 216 "Web safe colors" limit is mostly forgotten? Does "modern" ask for more and better graphics now that bandwidth is not limited to 56 Kbaud? Technology should perform tasks well. AJAX is great if real-time updates are needed, otherwise AJAX just complicates the program. (AJAX was great for an administration page with real-time monitoring of many threaded components. Alas, I programmed both ends of the communication without using a "framework".) I used DHTML for the Lenya-1.3's relations editor because the interface was much easier using JavaScript. But the submit-to-server should be handled once, not after each change, so using AJAX is not indicated. Colors and graphics should first be functional. Stable interfaces can be improved. Are any Committers also good graphic designers able to create a comprehensive scheme and willing to spend time on our default layout? (The migration to LCD monitors makes colors appear brighter and makes lighter colors indistiguishable from white. Webpages rarely look good on both CRTs and LCDs.) I agree with sticking to W3C standards. Apache software should use standards when it is not setting the standards. As with the recent Lenya-3 discussion, can we start with specifications? What changes will make our customers happy? solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
