[WSG] Out of Office AutoReply: digest for wsg@webstandardsgroup.org
Title: Out of Office AutoReply: digest for wsg@webstandardsgroup.org I will be out of the office the week of July 13 and returning on Monday July 18
Re: [WSG] Making a container div the same height as the longest div in it in mozilla browsers.
Ben Wrighton - StraightForward wrote: Works in IE and Opera but in all the Mozilla browsers I've tested in (Netscape, Firefox and Mozilla) the container doesn't wrap around the divs. I know it's something to do with all the divs in the container div being floated. If anyone can tell me how to solve it or point me in the direction of the relevant resource I would really appreciate it. Besides the P.I.E. method others have already linked to, floating the container will also work. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Sliding Panels
On 15 Jul 2005, at 4:34 AM, Chris Kennon wrote: Has anyone a sliding panel solution, such as this(http://www.siteexperts.com/tips/techniques), that is cross-browser and standards compliant ? Your sample: Directory Listing Denied. This Virtual Directory does not allow contents to be listed. But try Doug Bowman's Sliding Doors: http://www.alistapart.com/articles/slidingdoors/ and http://www.alistapart.com/articles/slidingdoors2/ N ___ Omnivision. Websight. http://www.omnivision.com.au/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Sliding Panels[corrected URL]
Hi, The following shows the correct request: (http://www.siteexperts.com/tips/techniques/panels/page1.asp) The example works in Safari and IE but fails in FF. Many Pardons and Thanks, C On Jul 14, 2005, at 3:14 PM, Nick Gleitzman wrote: On 15 Jul 2005, at 4:34 AM, Chris Kennon wrote: Has anyone a sliding panel solution, such as this(http:// www.siteexperts.com/tips/techniques), that is cross-browser and standards compliant ? Your sample: Directory Listing Denied. This Virtual Directory does not allow contents to be listed. But try Doug Bowman's Sliding Doors: http://www.alistapart.com/articles/slidingdoors/ and http://www.alistapart.com/articles/slidingdoors2/ N ___ Omnivision. Websight. http://www.omnivision.com.au/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Prototype Framework
Has anyone checked out the JavaScript Prototype framework? http://prototype.conio.net/ Are there any good resources around that explain how it works? ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Longhorn Avalon - seismic shift for web standards?
Hello folks, I was reading the June 2005 issue of APC (Australian Personal Computer) magazine which has a cover story on unique features built into the long-awaited Windows Longhorn OS including the Avalon presentation system/user interface. This section really got me thinking: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. In a nutshell, Avalon means developers are now free to code without considering the resolution of users' monitors. This ensures that apps developed in this environment will work on just about any display, from mobile phones and PDAs to wide-screen notebooks and high-end desktop systems. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? I searched the archives and no-one seems to have asked this question to the list before? What are peoples thoughts...? Regards PAUL ROSS SkyRocket Design Co http://www.skyrocket.com.au ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. As many systems use for some time... (KDE, Aqua/Quartz, ?) What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? There was some mentioning in this thread: http://lists.w3.org/Archives/Public/www-style/2005Jun/0248.html Web page is mostly document. Not an application GUI. I'd compare Avalon's XAML to XUL+SVG. -- Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
On 15 Jul 2005, at 9:54 am, Paul Ross wrote: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. Apple (OS X, Core graphics), recent KDE (using SVG) and recent Gnome already have this build. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? That will depend on what the browser supports. A webpage is not an application. SVG (and the canvas tag) is the obvious answer here. Firefox nightly builds (and DeerPark dev. preview) already have full SVG support build in. Opera 8: idem (only SVG tiny, atm). Safari and Webkit supports the canvas tag, SVG support (the patches made by the KDE team) has landed recently in the CVS tree, meaning you can already build Webkit with SVG support yourself. Konqueror recent builds should support SVG as well. Internet exploder: no support, except via the Adobe plugin. Maybe in the elusive Longhorn. As far as webstandards goes: no shift. You can use svg as a background-image, or for a series of buttons, or... Philippe --- Philippe Wittenbergh http://emps.l-c-n.com/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
But, if you're in the business of building web apps that target a specific platform.. :) We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. On 7/15/05, Philippe Wittenbergh [EMAIL PROTECTED] wrote: On 15 Jul 2005, at 9:54 am, Paul Ross wrote: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates.Apple (OS X, Core graphics), recent KDE (using SVG) and recent Gnomealready have this build. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? That will depend on what the browser supports. A webpage is not anapplication.SVG (and the canvas tag) is the obvious answer here.Firefox nightly builds (and DeerPark dev. preview) already have full SVG support build in.Opera 8: idem (only SVG tiny, atm).Safari and Webkit supports the canvas tag, SVG support (the patchesmade by the KDE team) has landed recently in the CVS tree, meaning youcan already build Webkit with SVG support yourself. Konqueror recent builds should support SVG as well.Internet exploder: no support, except via the Adobe plugin. Maybe inthe elusive Longhorn.As far as webstandards goes: no shift. You can use svg as a background-image, or for a series of buttons, or...Philippe---Philippe Wittenberghhttp://emps.l-c-n.com/** The discussion list forhttp://webstandardsgroup.org/See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help**
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
On 15/07/2005, at 11:40 AM, David Pietersen wrote: But, if you're in the business of building web apps that target a specific platform.. :) We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. No, we're not. Yes, my Windows box has IE on it. Due to the way Windows is built, it's almost impossible to remove it. But do I use it? Not if I can help it (aside from testing purposes). I'd much rather use Mozilla or Firefox, but it doesn't stop me from having to have IE on my computer. Oh, and just an aside: I'm curious to know where your current research comes from, I must admit. If you're going to quote statistics, quote the source. Otherwise, it's really difficult to take them seriously. My $0.02 anyway. Seona. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Longhorn Avalon - seismic shift for web standards?
hmmmI smell Troll... You don't work for Microsoft do you David? :) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Pietersen Sent: Friday, July 15, 2005 1:41 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Longhorn Avalon - seismic shift for web standards? But, if you're in the business of building web apps that target a specific platform.. :) We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. On 7/15/05, Philippe Wittenbergh [EMAIL PROTECTED] wrote: On 15 Jul 2005, at 9:54 am, Paul Ross wrote: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. Apple (OS X, Core graphics), recent KDE (using SVG) and recent Gnome already have this build. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? That will depend on what the browser supports. A webpage is not an application. SVG (and the canvas tag) is the obvious answer here. Firefox nightly builds (and DeerPark dev. preview) already have full SVG support build in. Opera 8: idem (only SVG tiny, atm). Safari and Webkit supports the canvas tag, SVG support (the patches made by the KDE team) has landed recently in the CVS tree, meaning you can already build Webkit with SVG support yourself. Konqueror recent builds should support SVG as well. Internet exploder: no support, except via the Adobe plugin. Maybe in the elusive Longhorn. As far as webstandards goes: no shift. You can use svg as a background-image, or for a series of buttons, or... Philippe --- Philippe Wittenbergh http://emps.l-c-n.com/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. Bluntly, if you want by business you had better. I've been using Linux for far longer than I've been building websites and, if I have to go to another box in order to use your site... I'll go else where. Even if I have to open IE (since when I'm on a windows box I generally am using firefox) I'll likely go elsewhere. Even though statistics may show that the OS in question is Windows, IE to the last of my knowledge is loosing market share. My $0.02 Randall -- R. Potter Design and Development Lead Midnight Oil Design: http://www.midnightoildesign.com Pragmatic Programming Principle #59: Costly Tools Don't Produce Better Designs. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
Really, are we mad to develop for anything else? Um, yes? Bridges are also built for conditions that don't occur most of the year. I mean - you should not 'develop' for a platform, but in compliance with some guidelines and compatibility in mind. -- Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
Hi all Please try and keep this conversation on topic. We're not in the business of getting into a mine's better than yours conversation here (take them off list if you wish). The topic of web standards and how they complement proprietary techs like XUL, XAML , Flash etc is quite interesting, lets stick to that. Thanks James admin On 7/15/05, Paul Bennett [EMAIL PROTECTED] wrote: hmmmI smell Troll... You don't work for Microsoft do you David? :) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Pietersen Sent: Friday, July 15, 2005 1:41 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Longhorn Avalon - seismic shift for web standards? But, if you're in the business of building web apps that target a specific platform.. :) We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. On 7/15/05, Philippe Wittenbergh [EMAIL PROTECTED] wrote: On 15 Jul 2005, at 9:54 am, Paul Ross wrote: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. Apple (OS X, Core graphics), recent KDE (using SVG) and recent Gnome already have this build. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? That will depend on what the browser supports. A webpage is not an application. SVG (and the canvas tag) is the obvious answer here. Firefox nightly builds (and DeerPark dev. preview) already have full SVG support build in. Opera 8: idem (only SVG tiny, atm). Safari and Webkit supports the canvas tag, SVG support (the patches made by the KDE team) has landed recently in the CVS tree, meaning you can already build Webkit with SVG support yourself. Konqueror recent builds should support SVG as well. Internet exploder: no support, except via the Adobe plugin. Maybe in the elusive Longhorn. As far as webstandards goes: no shift. You can use svg as a background-image, or for a series of buttons, or... Philippe --- Philippe Wittenbergh http://emps.l-c-n.com/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
HA HA HA Not exactly, I work for the Government. I don't think the statistic is that hard to believe really.My website gets 30,000 unique visitors a day, and the number of those using a non-windows OS is not even worth counting. I love Firefox, but playing Devil's advocate, how can we justify to our employers spending any time developing for alternate browsers when all an end user has to do is click on one icon over another to access your content? It is fine for HTML content, and even new stuff I guess, but when you have over 20 legacy apps facing the outside world that a few (very vocal) people are screaming to be made compliant, is it really worth evenconsidering? Just my 2 cents worth. On 7/15/05, Paul Bennett [EMAIL PROTECTED] wrote: hmmmI smell Troll...You don't work for Microsoft do you David?:) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of David PietersenSent: Friday, July 15, 2005 1:41 PM To: wsg@webstandardsgroup.orgSubject: Re: [WSG] Longhorn Avalon - seismic shift for web standards? But, if you're in the business of building web apps that target a specific platform.. :) We all do, really.I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows.Every one of these machines has IE on it.Really, are we mad to develop for anything else?Discuss. On 7/15/05, Philippe Wittenbergh [EMAIL PROTECTED] wrote: On 15 Jul 2005, at 9:54 am, Paul Ross wrote: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. Apple (OS X, Core graphics), recent KDE (using SVG) and recent Gnome already have this build. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? That will depend on what the browser supports. A webpage is not an application. SVG (and the canvas tag) is the obvious answer here. Firefox nightly builds (and DeerPark dev. preview) already have full SVG support build in. Opera 8: idem (only SVG tiny, atm). Safari and Webkit supports the canvas tag, SVG support (the patches made by the KDE team) has landed recently in the CVS tree, meaning you can already build Webkit with SVG support yourself. Konqueror recent builds should support SVG as well. Internet exploder: no support, except via the Adobe plugin. Maybe in the elusive Longhorn. As far as webstandards goes: no shift. You can use svg as a background-image, or for a series of buttons, or... Philippe --- Philippe Wittenbergh http://emps.l-c-n.com/ ** The discussion list forhttp://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help The discussion list for http://webstandardsgroup.org/See http://webstandardsgroup.org/mail/guidelines.cfmfor some hints on posting to the list getting help **
RE: SPAM: RE: [WSG] Longhorn Avalon - seismic shift for web standards?
Now cut that out (smile or no smile)! I use Windows machines exclusively and prefer to browse using IE as that's what my main audience uses. I pick up many things that Russ on his non Win/IE combination misses (not that he doesn't check but they are not his defaults and things do slip through). I'll check on the boutique browsers but until one of them gains the market share, IE is the default target. Keep in mind that I am an application developer, not a designer so I care little about the 'look', that's for the designer to look after. I am a huge standards advocate, but I'm also a realist that has real clients with real audiences. The previous comment was a good one. But, if you're in the business of building web apps that target a specific platform.. :) This reference to web applications could mean an Intranet Application (known audience technology) for booking resources, filling in leave applications, database editing, phone lists etc. or a CMS Administration console or an online banking tool where you can specify (or test for) a specific user_agent and design a really great application in that framework. I often limit CMS Administration consoles to IE as I may well use an inline HTML editor (an Ektron one for example) that invokes a dll on the client. In my experience this is a lot more stable than Java applets and other stuff that will allow stand-alone (non operating system-integrated) browsers to use them. Peter hmmmI smell Troll... You don't work for Microsoft do you David? :) ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
On 7/15/05, David Pietersen [EMAIL PROTECTED] wrote: We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. Windows and Microsoft is a touchy subject for some people at the best of times. The numbers speak for themselves really (well, after you subtract Windows 98/NT/2000 and CE-based operating systems it may be something like randomfigure60%/randomfigure, but in saying that, it all depends on your target market. If you're making websites using (X)HTML/CSS/JS and following web standards then you aren't targetting a specific OS/platform/user-agent - and that's what web standards are all about. You build things according to standards so that you aren't tied to OS/platform/user-agent X, thus (hopefully) making your site accessible as possible. The difference is when you are purposefully targetting an /application/ to a specific group of people who are known to run platform X or user-agent X. In the case of Avalon development, we'll have nice, new, powerful tools to create desktop or web-based applications for the target audience who runs Windows XP and Longhorn. Great! But at the end of the day, web standards should be unphased by Avalons arrival. Web sites will go on being web sites, and Avalon will open a new market. Just my 2c anyway :) ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
I work for the Government. So, that's sad. You shlould have DDA/WCAG in mind. Accessible page must be universal as far as posible. 30,000 unique visitors a day, and the number of those using a non-windows OS is not even worth counting. I love Firefox, but playing Devil's advocate, how can we justify to our employers spending any time developing for alternate browsers We don't 'develop' for alternative browsers in my company. We just build web sites that adhere to standards (+ some insane IE tweaking). when all an end user has to do is click on one icon over another to access your content? You shold be more forward-thinking if you're responsilbe for .gov web site. (No offence, please.) over 20 legacy apps facing the outside world That's different. Many webapps (GIS, panoramas) have some requirements. Even if I'm convinced that making an app compatible (see google maps) is possible, repairing the old ones is not worth it, if it is not requested. -- Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longhorn Avalon - seismic shift for web standards?
We all do, really. I am at home, and don't have the research here, but current statistics show that 97.4% of all devices accessing web content are running on Windows. Every one of these machines has IE on it. Really, are we mad to develop for anything else? Discuss. I realise you said devices, but I'd like to stress that Windows does not equate with desktop PC running IE. It could (more and more these days) be a hand-held device where thoughtful design and accessibility are very important. (I'm talking less about screen- readers here as the original post was about graphics.) It *could* also be an Opera user (Opera defaults to telling websites it visits it is WinIE). This is apart from the growing number of people - even non-techie folks - using Firefox. The way in which the internet is being used is changing. Just because we (as individuals) might not have changed the way we use it, does not mean a general shift is not occurring - and the hand-held issue for one is big and getting bigger. Just food for thought. Vicki. :-) ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Longhorn Avalon - seismic shift for web standards?
I dont think XAML needs to be hosted inside IE? From: [EMAIL PROTECTED] on behalf of Justin Carter Sent: Fri 15/07/2005 02:19 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Longhorn Avalon - seismic shift for web standards? I dont think Avalon and XAML will directly impact the production of ordinary websites, but I think it may well stir up the world of web applications. Yes you will be able to host an application using XAML inside a web browser (presumably only IE?), but building a website this way would be a little bit crazy and severely limit your audience. Avalon will actually run on Windows XP as well as Longhorn - so there is the potentional for it to be quite widespread - however that still means that it'll be restricted to these two OS's which really isn't good enough if you're dedicated to accessibility. But, if you're in the business of building web apps that target a specific platform.. :) On 7/15/05, Paul Ross [EMAIL PROTECTED] wrote: Hello folks, I was reading the June 2005 issue of APC (Australian Personal Computer) magazine which has a cover story on unique features built into the long-awaited Windows Longhorn OS including the Avalon presentation system/user interface. This section really got me thinking: The most important difference between Avalon and the current Windows display architecture is that Avalon is vector based. The vector structure allows scalable graphics (windows, fonts icons), meaning designers can specify shapes and objects onscreen instead of mapping elements using pixels and x/y coordinates. In a nutshell, Avalon means developers are now free to code without considering the resolution of users' monitors. This ensures that apps developed in this environment will work on just about any display, from mobile phones and PDAs to wide-screen notebooks and high-end desktop systems. What does all this mean for the web standards community? Am I reading too much into this by thinking this is a seismic shift in the way we could be building websites in the future? In particular - what are the implications in the XHTML/CSS path versus something like Flash? I searched the archives and no-one seems to have asked this question to the list before? What are peoples thoughts...? Regards PAUL ROSS SkyRocket Design Co http://www.skyrocket.com.au ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** winmail.dat
