The project for an client agency, not our own use. The primary applications are internal -- one drives a call center where bilingual operators take complaints from the general public on fraud and identity theft. There's a public-facing component, in the shape of web forms that allow direct submission of complaints.
We've run into one big issue on the U.I. side -- we've been perfecting our WebObjects framework for Ajax, but we are struggling to get a Section 508 compliant interface that satisfies the business customer.
We have been using a pretty sophisticated _javascript_ browser detect, but there's another wrinkle: we are pushing all the internal apps through a Plumtree portal. Its gatewaying of behind-the-firewall applications is pretty useful, but makes _javascript_ problematic (PT re-writes URLs to ensure a secure connection, shielding the web app from direct contact with the user).
Regarding Michael's response, I am curious. What are you employing PHP for in your stack?
Tony, I think we've become pseudo-experts on the standards. I think your advice on keeping things Java-standard as much as possible is spot on. While I really like WoMonitor (ever thought anyone would write that??), my developers have been perfecting builds as you mentioned -- to deploy in other app servers. The trick has been to write build scripts that honor Xcode/Wo as well as Eclipse. The biggest headache has been in SVN, keeping an Xcode version and an Eclipse version of each project.
Part of our architecture has been to build a rules engine that allows the business customers (not the government IT operations staff) to make modifications to business logic. All the web services can make calls to that rules engine (itself a web service) -- changes to the rules propagate auto-magically. No code changes, no developer intervention. Kind of nifty, in a nerdy sort of way.
-- Ubique, Tom Termini -- -- BlueDog Knowledge worker applications via the internet from the Premier WebObjects Application Service Provider
On Jul 21, 2006, at 4:25 PM, Brian Raymond wrote:
Deleted..
In regards to IE, MS bends the rules a lot, trying to make new standards with their proprietary stuff.... Windows Vista adds a lot of proprietary items to web development, however, Firefox is quickly gaining on IE, so at this point I say FF is more important to develop for than IE... IE will have to adapt or lose out.
Is this development for personal purposes or for your organization and is it for internal applications or external applications. I'm asking because right or wrong IE still holds a majority of the browser market and will for years to come so it's usually not a browser you can ignore.
- Brian
|