I've bounced this same problem around to a couple of different places with different solutions. I think using configuration data to drive appearance is a great approach. It adds a bit of complexity but it addresses your first hurdle - touch-point dependencies. At least with configurable data, you're down to editing a list of keywords or values on a single document.
The bigger problem, as you alluded to, is where do I punt my cross-platform issues to? Do I use flex/flash and punt to the plugin? Do I try to use browser side libraries like dojo and punt tot he pre-packaged server code?
I don't think there's a perfect answer. I do think there's the narrow path approach though. Choose the best platform for the need, choose the best approach for the application. If it's a template you're going to roll out again and again, writing a HTA ( http://msdn.microsoft.com/en-us/library/ms536496%28VS.85%29.aspx ) to generate your style sheet for you each time is no big deal (assuming you're just doing text and graphic files with no data). A more complex version of this could be done with Domino or ASP.NET. Then you get into 'fitting the need'. Again no perfect solution but you pick the best fit.
While there's been lots of effort to standardize the web, there will always be competitive product differentiation, early adopters and emerging trends and technology upsetting the cart. We'll never have a unified approach that reduces everything to a neat configurable package with a minimum of fuss that has universal adoption. We might see wide adoption of certain technologies and methods, but thank God, you and I have a job because nobody can agree on the best way to get things done with IT. :-)
Hi Rob,
I've bounced this same problem around to a couple of different places with different solutions. I think using configuration data to drive appearance is a great approach. It adds a bit of complexity but it addresses your first hurdle - touch-point dependencies. At least with configurable data, you're down to editing a list of keywords or values on a single document.
The bigger problem, as you alluded to, is where do I punt my cross-platform issues to? Do I use flex/flash and punt to the plugin? Do I try to use browser side libraries like dojo and punt tot he pre-packaged server code?
I don't think there's a perfect answer. I do think there's the narrow path approach though. Choose the best platform for the need, choose the best approach for the application. If it's a template you're going to roll out again and again, writing a HTA ( http://msdn.microsoft.com/en-us/library/ms536496%28VS.85%29.aspx ) to generate your style sheet for you each time is no big deal (assuming you're just doing text and graphic files with no data). A more complex version of this could be done with Domino or ASP.NET. Then you get into 'fitting the need'. Again no perfect solution but you pick the best fit.
While there's been lots of effort to standardize the web, there will always be competitive product differentiation, early adopters and emerging trends and technology upsetting the cart. We'll never have a unified approach that reduces everything to a neat configurable package with a minimum of fuss that has universal adoption. We might see wide adoption of certain technologies and methods, but thank God, you and I have a job because nobody can agree on the best way to get things done with IT. :-)