Search

What the Quote?

"Vista does add something useful.... it takes all the complicated dynamics of a work slow-down off the shoulders of the users and automates it."

Steven Rodgers

"I think the Pope resembles a jack-o-lantern. He's just got the kind of face you wanna carve into a pumpkin."

Pete Oberlin

"Genome. And special sauce (primordial soup)."

Laura Tripcony

« Loopy | Main| Personalized Plates »

Purty charts in Domino

Category show-n-tell thursday
If necessity is the mother of invention, boredom must be the weird aunt that has 87 cats and always smells like cheese.TM

I was going stir crazy here in my hotel room, so I started playing with the XML/SWF Charts library I stumbled upon the other night. Here's a sample of what I came up with. That's live data, generated by 11 lines of code (not counting variable declarations). The sample database contains the chart library (comprised of various SWF files stored as file resources), an example page to demonstrate the markup syntax for embedding the main SWF, and an agent to demonstrate generating the source XML. In this case it's navigating the referrers by date view in my blog. Nothing too fancy in this example, but this library allows all sorts of wacky output formats. Check out the gallery to see some of what it's capable of.


Comments

Gravatar Image1 - pretty cool Tim, I fussed around with some of the JavaScript graphing libraries in the past. I think { Link } is pretty cool. It uses canvas tags in FF or SVG for other browsers and can do a variety of graph types.

Gravatar Image2 - This is pretty sweet actually. Amazingly simple and so (dare I say?) sexy.

Gravatar Image3 - Cool trick. The down-loadable nsf works on my server, but I can't figure out how to make it chart anything but the default graph. What should the filename be of the XML source for the chart data, and where should the file be placed?

Gravatar Image4 - @Paul, actually, the "filename" is pointing to an agent named "chartsource.xml"; it's not actually a file. So you can either change the code of that agent to generate different XML, or change the "xml_source" attribute to point to a different location: a different agent, an XPage that behaves like an agent { Link } , or a static XML file that conforms to the same format... in the latter case, you could store the file as a file resource in the application design, an attachment in a report document, or some location external to the application (or even to Domino).

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)