Using dhtmlxGantt with Ruby on Rails [Tutorial]

| Comments (5)

There’s no limit to perfection. And no limit to our intentions of providing you with different possible ways of combining our components with your favorite development tools. For example, you can check this tutorial that describes how you can use our dhtmlxGantt along with the Laravel framework.

This time, we’ll go a little bit further and offer you to add a new skill to your knowledge baggage. Let us introduce to you this step-by-step tutorial that covers the using of dhtmlxGantt along with Ruby on Rails.

download gantt

Creating a New Project

If you don’t have Ruby on Rails installed, you can follow this installation guide. Installation method may difer according to the operating system you use, but it shouldn’t take long. After you finish installing Rails, you’ll be able to create a new project.

To do so, type in your terminal:

rails new path/to/your/project

Now, your first Ruby on Rails project is officially created. Before testing the application, let’s deal with creating a controller and routing.

Controllers and Routes

primary task is to receive requests that users send to an application. To define which controller will receive a particular request, you use routing. Usually, applications have several routes and controllers. Different routes can be served by different actions. Actions collect the information that will be provided to a view.

Let’s create a new controller named home. Besides the controller, we’ll create a new action named index.

cd path/to/your/project
rails generate controller home index

The output should confirm that new files were created. Now, let’s config the routing. Open the file config/routes.rb and find the following line at the very beginning of this file:

get 'home/index'

Then, replace it with this code:

root :to => 'home#index'

Now we can test our server. Run in your terminal:

rails server

Open in your browser http://localhost:3000/, and you’ll get this result:

run rails

Doesn’t look so impressive at this step, but everything works fine which is a good sign.

Let’s proceed with the views.

Unpacking dhtmlxGantt and Creating the Views

A view’s work is to display the information that was previously collected by an action in a human readable format. Before creating a new view, we need to download the dhtmlxGantt package.

The vendor directory of your project contains third-party code. This is where we’ll unpack the dhtmlxGantt files. It will take two steps:

1. Unpack the file codebase/dhtmlxgantt.js and the directory codebase/ext from the package to the directory vendor/assets/javascripts/ of your project
2. Unpack the file codebase/dhtmlxgantt.css and the directory codebase/skins from the package to the directory vendor/assets/stylesheets/ of your project

Now, we should add this new files to the precompile array. Open the config/initializers/assets.rb file and add the following code:

Rails.application.config.assets.precompile += %w( dhtmlxgantt.css )
Rails.application.config.assets.precompile += %w( dhtmlxgantt.js )

Let’s now create a view. If there’s no controller-specific layout, Rails will use the app/views/layouts/application.html.erb. This file is a template for all pages that have common elements. We’ll use it to include dhtmlxgantt.js and dhtmlxgantt.js to our project. Open this file and replace the existing code with the following:

<!DOCTYPE html>
    <%= stylesheet_link_tag    'application', media: 'all', 'data-turbolinks-track' => true %>
    <%= stylesheet_link_tag 'dhtmlxgantt', media: 'all', 'data-turbolinks-track' => true %>
    <%= javascript_include_tag 'application', 'data-turbolinks-track' => true %>  
    <%= javascript_include_tag 'dhtmlxgantt', 'data-turbolinks-track' => true %>
    <%= csrf_meta_tags %>

    <%= yield %>


Now we can define a view for the home controller that we have created earlier. Open the file app/views/home/index.html.erb and add the DIV container for the Gantt chart along with the code that initializes the chart:

<div id="gantt_here" style='width:100%; height:800px;'></div>


We can check the changes that we’ve made. If you’ve stopped the server you can run it again (rails server), and here’s what you’ll see in your browser:

gantt chart

It’s already something. There’s a Gantt chart that allows you create and change new tasks. But at the moment, your application can’t save the changes. Let’s fix it.

Creating the Models

Our application requires two models: one for the tasks and one for the links between them.

Let’s create a model for the tasks first. Run in your terminal:

rails generate model Task text:string start_date:datetime duration:integer progress:float sortorder:integer parent:integer

As you noticed an ordinary task consists of its name, start date, duration, etc.

Now we can create a second model. For the links this time:

rails generate model Link source:integer target:integer link_type:string:limit1

And, finally, we can create a new database:

rake db:migrate

Optionally, you can add some tasks and links to your database. Open the Rails console:

rails c

And then, add the new tasks and links. For example:

Task.create :text=>"Task 1", :start_date=>"2015-10-25",  :duration=>2;
Task.create :text=>"Task 2", :start_date=>"2015-10-27",  :duration=>3;
Link.create :source=>1, :target=>2, :link_type=>"0";

When you finish, just type exit to close the Rails console.

Now we should add the code that allows us to save and load the data.

Creating Controllers to Work with the Data

Let’s create a new action for loading the data. Open the app/controllers/home_controller.rb file and add the following code that creates the data action:

def data
    tasks = Task.all
    links = Link.all

    render :json=>{
              :data =>{|task|{
                          :id =>,
                          :text => task.text,
                          :start_date => task.start_date.to_formatted_s(:db),
                          :duration => task.duration,
                          :progress => task.progress,
                          :sortorder => task.sortorder,
                          :parent => task.parent
              :links =>{|link|{
                  :id =>,
                  :source => link.source,
                  :target =>,
                  :type => link.link_type

Now we should create a new controller task:

rails generate controller task

And add new actions for adding, changing, and deleting the data. To do so, open the app/controllers/task_controller.rb and add:


def update
    task = Task.find(params["id"])
    task.text = params["text"]
    task.start_date = params["start_date"]
    task.duration = params["duration"]
    task.progress = params["progress"]
    task.sortorder = params["sortorder"]
    task.parent = params["parent"]

    render :json => {:status => "ok"}

  def add
    task = Task.create :text => params["text"], :start_date=> params["start_date"], :duration => params["duration"],
                       :progress => params["progress"], :sortorder => params["sortorder"], :parent => params["parent"]

    render :json => {:tid =>}

  def delete
    render :json => {:status => "ok"}

As you may have guessed, now it’s time to create the controller named link. Creating a new controller:

rails generate controller link

And don’t forget to add the code required for adding, changing, and deleting. Open the app/controllers/link_controller.rb file and add:


 def update
   link = Link.find(params["id"])
   link.source = params["source"] = params["target"]
   link.link_type = params["type"]

   render :json => {:status => "ok"}

 def add
   link = Link.create :source => params["source"], :target => params["target"], :link_type => params["type"]
   render :json => {:tid =>}

 def delete
   render :json => {:status => "ok"}

Now we need to define the routes to our new controllers and actions. Open the config/routes.rb file and add:

match "home/data", :to => "home#data", :as => "data", :via => "get"

post "home/data/task", :to => "task#add"
put "home/data/task/:id", :to => "task#update"
delete "home/data/task/:id", :to => "task#delete"

post "home/data/link", :to => "link#add"
put "home/data/link/:id", :to => "link#update"
delete "home/data/link/:id", :to => "link#delete"

We’re almost there. One more step. Open the app/views/home/index.html.erb file and add the code that initializes the chart, loads, and saves the data. Insert it between the <script></script> tags:

gantt.config.xml_date="%Y-%m-%d %H:%i";

gantt.load("<%= data_path %>");

var dp = new dataProcessor("<%= data_path %>");

At least, we can check the final result. If you open your application in browser, you’ll see two tasks and a link between them. These are the tasks that we’ve created earlier.

gantt chart with rails

You can create new tasks and links and change them. The application will save the changes to the database.

Hopefully, this article will be useful to you. Here you can also learn how to use dhtmlxScheduler with Ruby on Rails. Do not forget to visit our blog from time to time. There will be more helpful tutorials for you.


  1. olsi gjeci July 10, 2016 at 7:34 pm

    HI. Im trying to follow the tutorial and at the end after implementing everything as you say, when i try to create a task i get this error: No route matches [POST] “/show/data/task1468164588503”
    i think im doing everything excartly the same with the exception of home controller’s name which i named show controller.
    here are my routes:
    match “show/data”, :to => “show#data”, :as => “data”, :via => “get”

    post “show/data/task”, :to => “task#add”
    put “show/data/task/:id”, :to => “task#update”
    delete “show/data/task/:id”, :to => “task#delete”

    post “show/data/link”, :to => “link#add”
    put “show/data/link/:id”, :to => “link#update”
    delete “show/data/link/:id”, :to => “link#delete”

    ca you please help?
    thank you

  2. Olivier September 17, 2016 at 2:07 am

    Great tuto. Is there a way to pass additional parameters on add/update task?
    I’m looking to retrieve the closest task where parent equals 0

    • Aras Kairys September 26, 2016 at 1:27 pm


      Yes, you can add additional request parameters using onBeforeUpdate event of the dataprocessor

      var dp = new dataProcessor(“”);
      dp.attachEvent(“onBeforeUpdate”, function(id, state, data){
      if(state == “inserted”){
      data.customProperty = “customValue”;
      return true;

  3. Joselo April 25, 2017 at 7:46 pm

    Thanks for this article, very useful, Just in case I had to add

    protect_from_forgery with: :null_session, if: { |c| c.request.format == ‘application/json’ }

    To avoid the problem related with authorization token

    • Aras Kairys (DHTMLX team) April 28, 2017 at 12:47 pm

      Hi Joselo,
      Seems like Ruby uses :null_session method by default.

Leave a Reply