Re:Why everyone should use Safari for rich web development
by zimbabwe on Thursday July 09, 2009 @10:30AM
(#695926)
That's an interesting idea. The problem with it is that it takes a very long time and, depending on the OS being used to develop, would be a pain to work with. I'd have to be in Windows constantly to test the IE pages as I built them, and since there are 3 separate Internet Explorers I'd probably have to build 3 separate pages. If you combine both browser usage and resolution detection, suddenly I've got to make a dozen pages for every page on my web site, which is time consuming and not exactly a comprehensive approach either.
This approach works for the iPhone, which is standardized completely, but not for the complex and varying desktop browser scene.
Re:Why everyone should use Safari for rich web development
by moe on Thursday July 09, 2009 @12:45PM
(#696209)
If browser differences cause you so much grief, why don't you just treat whatever goes out to the client as "object code" of your own engine.
You mean like, swf?
Browser differences are accomodated through maintenance to your engine, not every page or library.
You mean like, by adobe?
While you're at it, take a look at your user's resolution as well, and serve it the way they want to see it, not what you decided is best. No one likes horizontal scrolling or white space on the edges.
Well if these are your priorities then I suggest to take a look at Flex.
You limit your audience to clients who have the plugin - but other than that it just works™.
Exactly where does it say that HTML, CSS, & Javascript has to be source code? If browser differences cause you so much grief, why don't you just treat whatever goes out to the client as "object code" of your own engine.
That engine would have to create a different page for each browser that you decided to support. Sure, it would be 4 times the work for every page, but that's work done by your engine, not you. Browser differences are accomodated through maintenance to your engine, not every page or library.
IE is not going away any time soon, so your output better be able to handle it's DOM. While you're at it, take a look at your user's resolution as well, and serve it the way they want to see it, not what you decided is best. No one likes horizontal scrolling or white space on the edges.