Changes between Version 30 and Version 31 of TimeVisualizerPlugin


Ignore:
Timestamp:
Jan 18, 2016, 5:29:30 PM (8 years ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TimeVisualizerPlugin

    v30 v31  
    11[[PageOutline(2-5,Contents,pullout)]]
    22
    3 = Plugin to render burndown SVG images
     3= Render burndown images in svg format
    44
    55'''Links:'''
    6 [query:status!=closed&component=TimeVisualizerPlugin&order=priority open #]
    7 | [http://trac-hacks.org/newticket?component=TimeVisualizerPlugin&owner=mape new #]
     6[query:status!=closed&component=TimeVisualizerPlugin&order=priority open tickets]
     7| [/newticket?component=TimeVisualizerPlugin new ticket]
    88| [/svn/timevisualizerplugin svn]
    9 | [browser:timevisualizerplugin browse]
     9| [browser:timevisualizerplugin browse code]
    1010
    1111== Description
    1212
    13 This component draws customizable burndown graphs from ticket history provided by TimingAndEstimationPlugin. Dynamic graphs can be easily embedded to wiki pages.
     13This plugin creates customizable burndown graphs from the ticket history provided by TimingAndEstimationPlugin. Dynamic graphs can be easily embedded into Trac wiki pages.
    1414
    1515Developed and tested with Trac 0.10.4, Python 2.4, sqlite, mod_python and Apache on Windows. The 0.6 version works on Trac 0.11.
    … …  
    1717== Bugs/Feature Requests
    1818
    19 Existing bugs and feature requests for TimeVisualizerPlugin are [query:?status=new&status=assigned&status=reopened&group=&component=TimeVisualizerPlugin&order=priority here].
     19Existing bugs and feature requests for TimeVisualizerPlugin are
     20[report:9?COMPONENT=TimeVisualizerPlugin here].
    2021
    21 If you have any issues, create a [/newticket?component=TimeVisualizerPlugin new ticket].
     22If you have any issues, create a
     23[/newticket?component=TimeVisualizerPlugin new ticket].
    2224
    2325[[TicketQuery(component=TimeVisualizerPlugin,group=type,format=progress)]]
    … …  
    2527== Installation
    2628
    27 '''Dependencies:''' TimingAndEstimationPlugin was needed in 0.4 and earlier versions to feed database with estimates and totalhours custom tickets. Browser must render SVG natively and support the html tag iframe. Latest Firefox, Opera and Safari browser versions should work.
     29'''Dependencies:''' TimingAndEstimationPlugin was needed in 0.4 and earlier versions to feed the database with estimates and totalhours custom tickets. Browser must be able render SVG natively and support the html tag iframe. The latest Firefox, Opera and Safari browser versions should work.
    2830
    29  1. Get source installation & install it
    30 {{{#!sh
     31 1. Get source files and install it:
     32 {{{#!sh
    3133svn co http://trac-hacks.org/svn/timevisualizerplugin/branches/TimeVisualizer_0.6
    3234cd TimeVisualizer_0.6
    3335python setup.py install
    3436}}}
    35  2. Edit your `trac.ini` file and modify components section:
    36 {{{#!ini
     37 1. Edit your `trac.ini` file to enable the plugin:
     38 {{{#!ini
    3739[components]
    3840<...other components...>
    3941tractimevisualizerplugin.* = enabled
    4042}}}
    41  3. Restart server to propagate changes.
     43 1. Restart server to propagate changes.
    4244
    4345For details, see browser:/timevisualizerplugin/branches/TimeVisualizer_0.6/release_notes.txt
    … …  
    4547== Usage
    4648
    47 To test graphs & filtering, access "http://server:port/path_to_trac_env/tractimevisualizer". It will render hours from whole project life cycle.
     49To test graphs and filtering, access "http://server:port/path_to_trac_env/tractimevisualizer". It will render the hours from the whole project's life cycle.
    4850
    49 More practical is to get graphs from some certain time frame and filter hours based on milestone and/or component. This is achieved with macro !BurnDown (wrote this plugin to replace ScrumBurndownPlugin because its graphing capabilities were limited and it modifies the database schema).
     51More practical is to get graphs from some a certain time frame and filter the hours based on milestone and/or component. This is achieved with macro !BurnDown. I wrote this plugin to replace ScrumBurndownPlugin because its graphing capabilities were limited and it modifies the database schema.
    5052
    51 In my example project, I have wiki page with following content:
     53In my example project, I have a wiki page with following content:
    5254{{{
    5355[[BurnDown(width=800,height=200,query=targetmilestone=mile1&datestart=08/8/07&dateend=8/22/07)]]
    … …  
    5759}}}
    5860
    59 It renders the following graphs (picture is cropped to fit better on this page)
     61It renders the following graphs (picture is cropped to fit better on this page):
    6062
    6163[[Image(TracTimeVisualizerPlugin_ss1.PNG)]]
    … …  
    6769== Feedback
    6870
    69 [wiki:TimeVisualizerPlugin/FeedBack Feel free to give feedback]
     71Feel free to [wiki:TimeVisualizerPlugin/FeedBack give feedback].
    7072
    7173== Recent Changes
    7274
    73 [[ChangeLog(timevisualizerplugin, 5)]]
     75[[ChangeLog(timevisualizerplugin, 3)]]
    7476
    7577== Author/Contributors