The third way
Currently I see device independent web engineering as follows:
- The typical device dependent way. WRONG.
- The W3C device independence WG way. WRONG.
- Style and content are seperated with an emphasis on the UA to do its job. RIGHT.
The UA on a mobile would do this job really well if users can easily:
* Disable style sheets
* Disable images
* Scroll better (WTF should a server pagenate?)
* Allow larger sized documents than they do now
Read my thesis... there is a long list coming :)
The UA would also need to somehow recognize columns layouts and not budge up text. Text must flow full width on a typically small display of a mobile. Columns do not work. Possibily some screen scraping needs to be done with legacy HTML.
As for a longer term solution for images, lets get bitmaps scaling with relative dimensions I say, like your style sheet should be already! Hint: this is how NOT to create a style sheet.