From: Alex B. <en...@tu...> - 2001-05-17 18:30:48
|
> Yeah, all this stuff as been the XML hype for some time now, and as a > technology person I highly agree that XML (& XSLT) is the way to go, it > just makes sense. What my concern is how this affects the interface > designers. Right now, they know and understand HTML/CSS, and have picked > up the learning curve on how to fit it into a template language. So how > do they deal with XSLT? Learn a whole new concept/language? If they do, > how do they understand and control how XSLT outputs thier work into > HTML? They can be very picky, and may just get totally frustrated trying > to get things to look the way they want. They are already dealing with > browser bugs & inconsistancies, now they have to throw XSLT into the > mix. Speaking as a a designer (I have a strange hat on now, so I am qualified) - xslt is wonderful for all of the above. I get properly compressed output. I am forced to make clean, properly structured documents. I'm not forced, but it certainly helps to use CSS properly. etc. Yes, XSLT is a learning curve, but I don't have a problem with learning something new as long as it's better. Which is why I should re-iterate that TemplateManager can and (no doubt) will have support for all kinds of template systems, contributed by users. > Maybe I'm off base here, as I have only read about XML & XSLT and tried > rudimentary examples. I haven't tried to actually put it to use in a > production environment. But, I'm going to grab r2 and do some tests and > analysis. Well, if you grab the r2 snap I published, you don't be able to run it :) That's sort of a "directory structure" snap, it doesn't work. It will soon, though. _alex |