Post by banshee858 Post by David Roberts Post by banshee858
Let me be more precise: the XML file generated is the semi-stable
artifact which the graphic designers and UI people use to work
their magic. From my understanding, once you define what the XML
DOM will look like, you can give the designers an XML file to work
on and the programmers can then code to the XML interface.
Have you seen this work? I don't even see passing UML documents
around as something that works, let alone XML.
I am only providing calarification to a statement I wrote which was
not that clear, not explaining how I implemented a solution using this
technique. My answer to your question would be "That is probably a
good question for the authors of the book - Doug Wallace, Isobel
Raggett and Joel Aufgang."
Personal disclaimer: I have NOT used this method\technique for
creating webpages, so I cannot comment as to how effective it is for
Agile teams. I believe I understand the concept they were trying to
impart. I was simply reporting that "Extreme Programming for Web
Projects" had a few diamonds in the rough worth hunting for.
After mostly not understanding this conversation for a while, it
occurs to me that I sort of know something that might be sort of
XProgramming.com is generated using articles that are formatted in
XML. It's a simple format, just a few tags like
<title>Under the Bleachers</title>
and a pass-through for XHTML.
Then I have some XSLT that creates tagged HTML, and the pretty card
look and the wrappers is created by some CSS that was created with
the help of Deb Hartmann and Anna Lissa Cruz.
The indexes are created from the articles using some Ruby code with
XPath parsing to pull out what's needed, some sorting, some more
XSLT, and voila! it's a web site.
It works pretty well, and the site reformatting not so long ago went
pretty easily. It wasn't /just/ a matter of plugging in the CSS
because the original site wasn't fully CSS'd, just generated
directly to HTML from the XSLT. Still, it was very easy, and a new
packaging would be relatively straightforward.
So ... XML is a good way of communicating between the various chunks
of code that build the site. It's a pain in the tail, however, to
create articles, and they're certainly not easy to read until they
get formatted. The XSLT "programs" are hard to write and I never did
figure out a decent way to TDD them. Same with CSS: all we could
figure out to do was create the CSS and view the pages.
There's a bug in there right now: the index pages for topics like
"documentation" (which are presently inaccessible because I forgot
to put their links there), are also badly formatted. There's
something odd going on between how that page is generated, and the
CSS. That's on my list to figure out, but I only recently even
noticed (a) that the indexes were not shown as links and (b) that
when you look at them, they don't look right.
Not exactly a triumph of TDD and Acceptance Testing. Still pretty
A lot of preconceptions can be dismissed when you actually
try something out. -- Bruce Eckel
To Post a message, send it to: ***@eGroups.com
To Unsubscribe, send a blank message to: extremeprogramming-***@eGroups.com
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to: