Last edited Apr 9, 2010 at 1:11 PM by Thecentury, version 2

Comments

Nihau Aug 5, 2013 at 8:41 AM 
Idite nahuy.

johncblacker Feb 19, 2013 at 11:04 PM 
A "good program" is one that is well documented and this program doesn't qualify. Unfortunately, there seems to be a plethora of good programs being produced by great programmers from reputable companies that fall into this category. Google, Microsoft and Yahoo come to mind almost immediately as companies that seem to be allowing some of their employees to pursue areas of interest to themselves and these people are producing some good work; however, good programs alone don't measure up to what's really needed. Not everyone wants to or has the ability to plow through code to find out how to make a program do what they want to do, thus the need for good documentation. Even samples don't always provide enough help for many individuals. D3 is an example of what is probably a great package but without the documentation it ends up very limited in usability. Perhaps what happens is that when someone realizes they've created a good package, they get $$ in their eyes and commercialism takes over; or, perhaps people don't really want to commit the time to document their work, maybe they just wanted to create a package to prove to themselves they could do it? Whatever, trying to use some of these "good programs" can be a most frustrating experience. On the other hand, I've also seen some commercial work that has very poor documentation, as well.

redfoxufa Feb 3, 2013 at 3:01 AM 
The program is really good. But I couldn't clear the plot before display other data set.

mypascal2000 Dec 20, 2012 at 2:09 AM 
The wiki link provided is nothing but useless.

jmborde Aug 26, 2012 at 5:22 PM 
All this code and no comprehensive documentation makes this project pretty much worthless for anything other than experimentation.

somos Mar 26, 2012 at 8:40 PM 
It's unexcusable that such a good developed product like this one full of different capabilities is not documented. An undocumented feature is an nonexistent feature for the end user and it's wasted time of the developer. Documentation and code are not separated thing. One without the other are useless.

erikvullings May 18, 2011 at 9:13 AM 
For an example, see also the MSDN article "Generating Graphs with WPF": http://msdn.microsoft.com/en-us/magazine/ff714591.aspx.
For a good example of how to use data binding (MVVM), see http://dynamicdatadisplay.codeplex.com/discussions/228122 (note that you have to bind to a readonly ObservableCollection), or download it from http://cid-996b1960e19fab56.skydrive.live.com/self.aspx/.Documents/LineGraph.zip.

holyfetzer Oct 24, 2010 at 3:53 PM 
Unfortunetaly as FrauHolle mentioned the lack of documentation or good tutorials (at least up to this point) makes D3 almost unusable for certain applications

FrauHolle Oct 13, 2010 at 11:52 AM 
The given link can not be called a "documentation" by any means. It is a mere collection of random topics. Please provide at least a usable "getting-started" guide or 90% of your work will be completely meaningless to the vast majority of the audience.