Skip to content

Draw gantt chart using frappe-gantt.js module for pyexcel data

License

Notifications You must be signed in to change notification settings

pyexcel-renderers/pyexcel-gantt

Repository files navigation

pyexcel-gantt - Let you focus on presentation with gantt

https://raw.githubusercontent.com/pyexcel/pyexcel.github.io/master/images/patreon.png https://api.travis-ci.org/pyexcel/pyexcel-gantt.svg?branch=master https://readthedocs.org/projects/pyexcel-gantt/badge/?version=latest

Support the project

If your company has embedded pyexcel and its components into a revenue generating product, please support me on patreon to maintain the project and develop it further.

If you are an individual, you are welcome to support me too on patreon and for however long you feel like to. As a patreon, you will receive early access to pyexcel related contents.

With your financial support, I will be able to invest a little bit more time in coding, documentation and writing interesting posts.

Introduction

pyexcel-gantt draws gantt chart using frappe-gantt.js for pyexcel data. Credit goes to frappe's gantt chart

Here is a sample csv file:

id,name,start,end,progress,dependencies,custom_class
Task 1,Writing pyexcel-gantt,2017-07-17,2017-07-18,80,,
Task 2,Test pyexcel-gantt,2017-07-19,2017-07-20,10,Task 1,,
Task 3,Write up the documentation,2017-07-21,2017-07-22,0,Task 1,,
Task 4,Release pyexcel-gantt,2017-07-23,2017-07-23,0,"Task 2, Task 3",,bar-milestone

What you can do is to view it with pyexcel's command line interface:

pyexcel view --in-browser --output-file-type gantt.html demo/tasks.csv

https://github.com/pyexcel/pyexcel-gantt/raw/master/pyexcel-gantt.gif

Programmatically, you can do the following:

import pyexcel as p


p.save_as(file_name='tasks.csv',
          dest_file_name='tasks.gantt.html')

Alternatively, you can save the file as:

$ pyexcel transcode tasks.csv tasks.gantt.html

Installation

You can install it via pip:

$ pip install pyexcel-gantt

or clone it and install it:

$ git clone https://github.com/pyexcel/pyexcel-gantt.git
$ cd pyexcel-gantt
$ python setup.py install

Development guide

Development steps for code changes

  1. git clone https://github.com/pyexcel/pyexcel-gantt.git
  2. cd pyexcel-gantt

Upgrade your setup tools and pip. They are needed for development and testing only:

  1. pip install --upgrade setuptools pip

Then install relevant development requirements:

  1. pip install -r rnd_requirements.txt # if such a file exists
  2. pip install -r requirements.txt
  3. pip install -r tests/requirements.txt

Once you have finished your changes, please provide test case(s), relevant documentation and update CHANGELOG.rst.

Note

As to rnd_requirements.txt, usually, it is created when a dependent library is not released. Once the dependecy is installed (will be released), the future version of the dependency in the requirements.txt will be valid.

How to test your contribution

Although nose and doctest are both used in code testing, it is adviable that unit tests are put in tests. doctest is incorporated only to make sure the code examples in documentation remain valid across different development releases.

On Linux/Unix systems, please launch your tests like this:

$ make

On Windows systems, please issue this command:

> test.bat

How to update test environment and update documentation

Additional steps are required:

  1. pip install moban
  2. git clone https://github.com/moremoban/setupmobans.git # generic setup
  3. git clone https://github.com/pyexcel/pyexcel-commons.git commons
  4. make your changes in .moban.d directory, then issue command moban

What is pyexcel-commons

Many information that are shared across pyexcel projects, such as: this developer guide, license info, etc. are stored in pyexcel-commons project.

What is .moban.d

.moban.d stores the specific meta data for the library.

Acceptance criteria

  1. Has Test cases written
  2. Has all code lines tested
  3. Passes all Travis CI builds
  4. Has fair amount of documentation if your change is complex
  5. Please update CHANGELOG.rst
  6. Please add yourself to CONTRIBUTORS.rst
  7. Agree on NEW BSD License for your contribution

License

New BSD License