Changes between Version 4 and Version 5 of DygraphsVisualizationPlugin


Ignore:
Timestamp:
Aug 24, 2015, 12:51:48 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes, updated code.google link and license

Legend:

Unmodified
Added
Removed
Modified
  • DygraphsVisualizationPlugin

    v4 v5  
    55== Description
    66
    7 This plugin is based on Rob Guttman's [[VisualizationPlugin|Visualization Plugin]], except that it uses the MIT-licensed [[http://dygraphs.com|Dygraphs]] charting library instead of the [[http://code.google.com/apis/chart/|Google Visualization API]].
     7This plugin is based on Rob Guttman's [[VisualizationPlugin|Visualization Plugin]], except that it uses the MIT-licensed [[http://dygraphs.com|Dygraphs]] charting library, instead of the https://developers.google.com/chart/?csw=1&safe=on Google Visualization API].
    88
    99This means that it can be legally used offline, which the Google APIs don't allow. There are corporate Trac installations that for various reasons can't be connected to the Internet.
    1010
    11 Only tested with Trac 0.12 and 1.0 so far.
     11Tested with Trac 0.12 and 1.0.
    1212
    1313== !Bugs/Feature Requests
     
    3535Once installed, enable graphical output for a particular report in the `trac.ini` file:
    3636
    37    {{{
    38    #!ini
    39    [dyviz]
    40    reports = 10
    41    options = width:1000,height:400
    42    }}}
     37{{{#!ini
     38[dyviz]
     39reports = 10
     40options = width:1000,height:400
     41}}}
    4342
    4443Customise options for a particular report:
    4544
    46    {{{
    47    #!ini
    48    [dyviz.report/10]
    49    options = plotter:barChartPlotter,labels:labels,colors:['red','orange','green'],includeZero:true,animatedZooms:true,legend:'follow'
    50    }}}
     45{{{#!ini
     46[dyviz.report/10]
     47options = plotter:barChartPlotter,labels:labels,colors:['red','orange','green'],includeZero:true,animatedZooms:true,legend:'follow'
     48}}}
    5149
    5250The options are generally passed directly to the Dygraphs library. To allow the `labelsDiv` option to be used effectively, the plugin inserts empty divs "dyviz_above" and "dyviz_below" above and below the chart, respectively.
     
    5654=== Report the history of tickets open and closed
    5755
    58 It's often useful to be able to generate reports that span a period of time, for monitoring the progress of a project.
     56It ioften useful to be able to generate reports that span a period of time, for monitoring the progress of a project.
    5957
    6058Constructing such reports is not always straightforward. Here's an example of a report that plots the number of tickets that were opened and closed throughout the duration of the project. It also plots the growth of the "backlog": the number of currently-open tickets at that time.
    6159
    62 Note that this query uses Common Table Expressions. These have only been present in SQLite since [[http://www.sqlite.org/releaselog/3_8_3.html|version 3.8.3]]. It will usually be necessary to update the version of `SQLITE3.DLL` in your Python installation's top-level `DLLs` folder to one compiled from SQLite 3.8.3 or later.
     60Note that this query uses Common Table Expressions. These have only been present in SQLite since [[http://www.sqlite.org/releaselog/3_8_3.html|version 3.8.3]]. It will usually be necessary to update the version of `SQLITE3.DLL` in your Python installation's top-level `DLLs` folder to one compiled from SQLite 3.8.3 or later:
    6361
    64 {{{
    65 #!sql
     62{{{#!sql
    6663WITH
    6764  cutoff_time(n, usec) AS
     
    113110=== Report the number of open tickets with particular values of a custom field over time
    114111
    115 Here's a more complex report that looks for tickets of type 'fault' that have a custom field 'safety_related'. At any time, this field can have one of three values that classify the safety status of the ticket: 'Not assessed', 'Safety related' or 'Not safety related'. The report plots the count of the number of open tickets with each safety status at the start of every week for the past three years.
     112Here ia more complex report that looks for tickets of type 'fault' that have a custom field 'safety_related'. At any time, this field can have one of three values that classify the safety status of the ticket: 'Not assessed', 'Safety related' or 'Not safety related'. The report plots the count of the number of open tickets with each safety status at the start of every week for the past three years:
    116113
    117 {{{
    118 #!sql
     114{{{#!sql
    119115WITH
    120116  -- Select the time period of interest here, e.g. last three years.