Web Engineering: A New Discipline for Development of Web-Based Systems
Web Engineering, Software Engineering and Web Application Development
Web-Based Information Systems Development - A User Centered Engineering Approach
Web Engineering, Software Engineering and Web Application Development
"Ceci n'est pas une pipe": Observations on the Nature of Webware
WSE '02 Proceedings of the Fourth International Workshop on Web Site Evolution (WSE'02)
Rethinking software connectors
International workshop on Synthesis and analysis of component connectors: in conjunction with the 6th ESEC/FSE joint meeting
Measuring the functional size of web applications
International Journal of Web Engineering and Technology
Component-based Web page management environment
Information Sciences: an International Journal
| Hi-index | 4.10 |
The near parity between Microsoft's Internet Explorer and Netscape's Navigator is bringing what had been merely a developers' annoyance firmly into the realm of disaster. The problem is a relatively familiar one: nonconformance or incomplete implementation of standards makes building sophisticated Web pages that work across browsers a difficult and expensive job. Because Web developers have to spend extra time and effort working around quirks in different implementations, they almost always have to privilege general functionality over technological enhancements. Just trying to get pages to look the same across browsers by following the Cascading Style Sheet Level 1 (CSS1) standard-a W3C recommendation finished nearly two years ago (1996)-requires intimate knowledge of the peculiarities of each version of each browser on each platform. IE 4 on Windows, for example, supports about 80 percent of CSS1 and about the same amount on Macintosh, but not the same 80 percent. Navigator 4 supports a little less of CSS1 on both Windows and Macintosh, but again not the same subset and not in the same way. And CSS is just the tip of the iceberg