Cart
[Home] [By Thread] [By Date] [Recent Entries]
I agree. It is much simpler to build up libraries of CSS property sets and for some applications, eg those that attach behaviors, the easiest game. Months to build a stylesheet is excessive unless the requirements keep perturbating. I have seen organizations where combinations of political influence, changes of management, undiscovered requirements etc. make for high uncertainty. Again, much depends on the kind of experience they come to the task with as others have noted. Given the abundance of examples on the web, there are plenty of good resources to start from once one understands the basics. There are a couple of conceptual hurdles. I did spend some time working out when variables and params were to be applied and of course, level of support in the framework makes a difference. Len http://www.mp3.com/LenBullard Ekam sat.h, Vipraah bahudhaa vadanti. Daamyata. Datta. Dayadhvam.h -----Original Message----- From: John E. Simpson [mailto:simpson@p...] I do agree that XSLT isn't something to be taken too lightly. OTOH someone else's reply on this thread suggested that a stylesheet could take months of work. That sounds excessive to me. The original poster's (John L. Thoms) message, trimmed version below, actually didn't specify *XSLT* stylesheets, or whether he was looking primarily to style or to transform his contractor's documents, and I wondered if he could make do with CSS. Browser support (or otherwise) aside, I'd think styling it with CSS would be a lot simpler than undertaking some kind of large-scale transformation project.
|
