I should clarify further. In trying to develop these RIA's then maybe it's acceptable to utilize table based layouts, that's what I mean. As for aspects like behavioral markup for purely progressive enhancement I think that's not really going to matter as you're likely to be dependant on javascript in the first place, ie most/all interface updates will be done via DOM manipulation.
TiM ------------ My interest is in building 'Rich Internet Applications', these are characterised by positionable windows, drag/drop functionality, complex UI interactivy etc. I just hate the term RIA hence I usually refer to Web Applications but this is really the catchall for any web content that is dynamically driven. So yeah apologies for not being clear here. Doh doh doh... Of course for traditional webpage apps/sites your HTML should be devoid of inline CSS, structural markup (eg tables etc), and inline javascript. The so called three layers of separation (structural, presentational, and behavioral) have been widely discussed since mid 2004 in web development circles. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
