Be the first to post a text review of Django-dataplot. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Code committed

  tdhock committed revision 198 to the Django-dataplot SVN repository, changing 1 files

  posted by tdhock 47 days ago

• Code committed

  tdhock committed revision 197 to the Django-dataplot SVN repository, changing 2 files

  posted by tdhock 47 days ago

• django-dataplot 0.6 file released: dataplot-0.6.tgz

  posted 167 days ago

• File released: /django-dataplot/0.6/dataplot-0.6.tgz

  posted 167 days ago

• File released: /django-dataplot/0.5/dataplot-0.5.tgz

  posted 615 days ago

• django-dataplot 0.5 file released: dataplot-0.5.tgz

  Django-dataplot By Toby Dylan Hocking Revision history 1.0 SVG plots -- with links -- rather than PDF. Other app model introspection to make plots. Akin to databrowse. PIL backend? possible to read PDF? Python-gnuplot backend? any demand? Django-graphs backend? Shellscript backend: examples of extending -- weblogo plot. Better example docs -- web!! 0.5 2008-03-03 Autoconfiguration code in now in plotmodels.py, so you can do "from dataplot import plotmodels as models" in your models.py instead of "from django.db import models". Basically this is the most DRY plot definitions can possibly be. Just define DATAPLOTS or MANAGER_DATAPLOTS in your model (see examples in demo soccer app), and you'll automatically get functional dataplots and data-gathering methods. Automatic update on save via Model in plotmodels.py. Each time a model calls save, we look for attributes which are plots, and makefiles() is automatically called for each of them (if enable_caching is set for the plot). Also, any manager-level plots with enable_caching=True will also be remade. If you want to have a custom save method, just call super(YourModel,self).save() within your save method, and plot updating will proceed as usual. If this plot updating behavior is undesired, just make a custom save method for your model and do what you need to. See bike and soccer demo apps for examples. Use in dirs other than django/contrib. Now, just put it anywhere on the PYTHONPATH (sys.path) and do import dataplot. For settings.INSTALLED_APPS, use 'dataplot'. If you still want to keep it in django/contrib, simply add that directory to your PYTHONPATH. Otherwise, move your dataplot directory to a location on the PYTHONPATH, i.e. for Debian/Ubuntu, a good place would be /usr/local/lib/python2.4/site-packages/. All dataplot classes may now take default plotting keyword arguments via the default_kwargs attribute, which should be set to a dictionary. This is useful for plots like the new ScatterCorr, which has the same R code as Scatter but uses different default arguments. When SAVE_DATA_ON_MAKEFILE is set to True for R.Plot instances, save_data is executed whenever makefile is executed. This makes it easy to get some sample datasets for debugging your R code: just turn on SAVE_DATA_ON_MAKEFILE, then load the page containing the plot on the testing server. After the page loads, the data and test code will be in the same directory as the image files. Now get_plot_args is standard for each plot backend, and the callable specified at dataplot instatiation is saved in instance.tocall. New python backend for making plots using a generic python function that accepts keyword arguments. Bike app now automatically loads data (using the RideManager.create_from_file_default method) when you load the homepage. You don't have to populate data from the shell anymore. Soccer app included for more plot demos/examples. Automatic data loading included. Bugfixes and refinements to the R.Scatter plot class. Also note that fit.line argument has changed to fit.lty, which should specify the lty value of the least squares fit line. Bugfix for enable_caching attribute of all plots. When set to False, it should remake the plot on every page view. However, for objects that were persistent between page views, it was caching them. Fixed. 0.4 2007-11-28 Support for plots made with generic command line tools via the shellscript backend. Nice error handling when settings.DEBUG is off: exceptions are caught and displayed on the webpage instead of the plot (rather than throwing a 500 internal server error page). R plots take on a value for r_code_filename of "class.name.R" by default, where class_name is the name of the subclass of dataplot.R.Plot (previously there was no default and you had to minimally specify r_code_filename). 0.3 2007-07-24 R test plots working on bike app: Scatter, Histogram, NormalQQPlot, TimeSeries. R autosave to R source and Rdata files upon data processing error. Allows you to easily drop into the R debugger and see what is going wrong. GenericPlot introduced to allow for backends other than R. Support for matplotlib. 0.2 2007-07-11 No longer use settings DJANGO_RPY_ENABLE_CACHING_DEFAULT, CONVERT_BINARY, R_CODE_DIRS_PATH, instead use attributes enable_caching, convert_binary of RPlot subclass or instance. For R_CODE_DIRS_PATH, code is searched for in R/ subdirs of app directories (convention over configuration). Custom plots tested and working, i.e. work.and.back.plot in the bike app. 0.1 2007-07-06 First public version.

  posted 616 days ago

• 0.4, plans for 0.5

  This new release is now available with these features: Support for plots made with generic command line tools via the shellscript backend. Nice error handling when settings.DEBUG is off: exceptions are caught and displayed on the webpage instead of the plot (rather than throwing a 500 internal server error page). R plots take on a value for r_code_filename of "class.name.R" by default, where class_name is the name of the subclass of dataplot.R.Plot (previously there was no default and you had to minimally specify r_code_filename). These are the features I am planning to implement for release 0.5: Examples for the shellscript backend. Better example docs, including a website with HTML documentation. OK to use in when installed in directories other than django/contrib.

  posted by tdhock 711 days ago

• django-dataplot 0.4 file released: dataplot-0.4.tgz

  posted 711 days ago

• File released: /django-dataplot/0.4/dataplot-0.4.tgz

  posted 711 days ago

• Plans for 0.4

  By working with the RPy team, I finally resolved a bug with rpy that was causing a segfault when unicode strings were passed to R. Consequently, I've been working on Django-dataplot development vigorously over the past week. I am now planning on trying to make Django-dataplot compatible with the SVN development versions of both Django and RPy. Here is a list of a few new features planned for release 0.4, which are now present in Django-dataplot SVN: - Shellscript backend streamlines plot generation from generic external command line programs. - Nice error handling when settings.DEBUG is off makes for easier debugging. - R backend automatically assumes same R function name as python class name (convention over configuration). I will formalize a release as 0.4 as soon as I feel the features are stable enough. Until then I will be working on coding and writing documentation.

  posted by tdhock 752 days ago