taskjuggler 0.0.2

data/test/TestSuite/Syntax/Correct/csvtest

@@ -0,0 +1,16 @@
+No.;Name;Id;Effort;Revenue;Cost
+1;Accounting Software;AcSo;180.3;98,000;80,437
+2;  Specification;AcSo.spec;20.3;0;7,628
+3;  Software Development;AcSo.software;85.0;0;32,150
+4;    Database coupling;AcSo.software.database;20.0;0;7,400
+5;    Graphical User Interface;AcSo.software.gui;35.0;0;13,650
+6;    Back-End Functions;AcSo.software.backend;30.0;0;11,100
+7;  Software testing;AcSo.test;25.0;0;8,425
+8;    Alpha Test;AcSo.test.alpha;5.0;0;1,770
+9;    Beta Test;AcSo.test.beta;20.0;0;6,655
+10;  Manual;AcSo.manual;50.0;0;16,856
+11;  Milestones;AcSo.deliveries;0.0;98,000;0
+12;    Project start;AcSo.deliveries.start;0.0;21,000;0
+13;    Technology Preview;AcSo.deliveries.prev;0.0;31,000;0
+14;    Beta version;AcSo.deliveries.beta;0.0;13,000;0
+15;    Ship Product to Customer;AcSo.deliveries.done;0.0;33,000;0

data/test/TestSuite/Syntax/Correct/manual2example.rb

@@ -0,0 +1,24 @@
+#!/usr/bin/env ruby -w
+# encoding: UTF-8
+#
+# = manual2example.rb -- The TaskJuggler III Project Management Software
+#
+# Copyright (c) 2006, 2007, 2008, 2009 by Chris Schlaeger <cs@kde.org>
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of version 2 of the GNU General Public License as
+# published by the Free Software Foundation.
+#
+
+def removeTags(fileName)
+  oFile = File.open('../../../../examples/' + fileName, 'w')
+  File.open(fileName, 'r') do |iFile|
+    while line = iFile.gets
+      oFile.puts line unless line =~ /^# \*\*\* EXAMPLE:/
+    end
+  end
+  oFile.close
+end
+
+removeTags('tutorial.tjp')
+

data/test/TestSuite/Syntax/Correct/tutorial.tjp

@@ -0,0 +1,485 @@
+/*
+ * This file contains an example project. It is part of the
+ * TaskJuggler project management tool. It uses a made up software
+ * development project to demonstrate some of the basic features of
+ * TaskJuggler. Please see the TaskJuggler manual for a more detailed
+ * description of the various syntax elements.
+ */
+# *** EXAMPLE: header1 +
+# *** EXAMPLE: header2 +
+project acso "Accounting Software" "1.0" 2002-01-16 - 2002-04-28 {
+# *** EXAMPLE: header1 -
+  # Hide the clock time. Only show the date.
+# *** EXAMPLE: formats +
+  timeformat "%Y-%m-%d"
+# *** EXAMPLE: formats -
+  # Use US format for numbers
+# *** EXAMPLE: formats +
+  numberformat "-" "" "," "." 1
+# *** EXAMPLE: formats -
+  # Use US financial format for currency values. Don't show pence.
+# *** EXAMPLE: formats +
+  currencyformat "(" ")" "," "." 0
+# *** EXAMPLE: formats -
+  # Pick a day during the project that will be reported as 'today' in
+  # the project reports. If not specified, the current day will be
+  # used, but this will likely be outside of the project range, so it
+  # can't be seen in the reports.
+# *** EXAMPLE: now +
+  now 2002-03-05-13:00
+# *** EXAMPLE: now -
+  # The currency for all money values is the Euro.
+# *** EXAMPLE: currency +
+  currency "USD"
+# *** EXAMPLE: currency -
+
+  # We want to compare the baseline scenario to one with a slightly
+  # delayed start.
+# *** EXAMPLE: scenario +
+  scenario plan "Plan" {
+    scenario delayed "Delayed"
+  }
+# *** EXAMPLE: scenario -
+# *** EXAMPLE: extend +
+  extend resource {
+    text Email "Email"
+    text Phone "Phone"
+  }
+# *** EXAMPLE: extend -
+# *** EXAMPLE: header1 +
+}
+# *** EXAMPLE: header1 -
+# *** EXAMPLE: header2 -
+
+# This is not a real copyright for this file. It's just used as an example.
+# *** EXAMPLE: copyright +
+copyright "© 2002 Crappy Software, Inc."
+# *** EXAMPLE: copyright -
+
+# The daily default rate of all resources. This can be overridden for each
+# resource. We specify this, so that we can do a good calculation of
+# the costs of the project.
+# *** EXAMPLE: rate +
+rate 390.0
+# *** EXAMPLE: rate -
+
+# Register Good Friday as a global holiday for all resources.
+# *** EXAMPLE: vacation +
+vacation "Good Friday" 2002-03-29
+# *** EXAMPLE: vacation -
+
+# *** EXAMPLE: flags +
+flags team
+# *** EXAMPLE: flags -
+
+# This is one way to form teams
+# *** EXAMPLE: macro +
+macro allocate_developers [
+# *** EXAMPLE: expandedmacro +
+  allocate dev1
+  allocate dev2
+  allocate dev3
+# *** EXAMPLE: expandedmacro -
+]
+# *** EXAMPLE: macro -
+
+# In order to do a simple profit and loss analysis of the project we
+# specify accounts. One for the development costs, one for the
+# documentation costs, and one account to credit the customer payments
+# to.
+# *** EXAMPLE: accounts +
+account cost "Project Cost" {
+  account dev "Development"
+  account doc "Documentation"
+}
+account rev "Payments"
+# *** EXAMPLE: accounts -
+# The Profit&Loss analysis should be rev - cost accounts.
+# *** EXAMPLE: balance +
+balance cost rev
+# *** EXAMPLE: balance -
+
+# *** EXAMPLE: resources +
+resource dev "Developers" {
+  resource dev1 "Paul Smith" {
+    Email "paul@crappysoftware.com"
+    Phone "x362"
+    rate 350.0
+  }
+  resource dev2 "Sébastien Bono" {
+    Email "SBono@crappysoftware.com"
+    Phone "x234"
+  }
+  resource dev3 "Klaus Müller" {
+    Email "Klaus.Mueller@crappysoftware.com"
+    Phone "x490"
+    vacation 2002-02-01 - 2002-02-05
+  }
+
+  flags team
+}
+resource misc "The Others" {
+  resource test "Peter Murphy" {
+    Email "murphy@crappysoftware.com"
+    Phone "x666"
+    limits { dailymax 6.4h }
+    rate 310.0
+  }
+  resource doc "Dim Sung" { 
+    Email "sung@crappysoftware.com"
+    Phone "x482"
+    rate 300.0 
+    vacation 2002-03-11 - 2002-03-16
+  }
+
+  flags team
+}
+# *** EXAMPLE: resources -
+
+# Now we specify the work packages. The whole project is described as
+# a task that contains subtasks. These subtasks are then broken down
+# into smaller tasks and so on. The innermost tasks describe the real
+# work and have resources allocated to them. Many attributes of tasks
+# are inherited from the enclosing task. This saves you a lot of typing.
+# *** EXAMPLE: task1 +
+# *** EXAMPLE: charge +
+task AcSo "Accounting Software" {
+# *** EXAMPLE: task1 -
+# *** EXAMPLE: charge -
+
+  # All work-related costs will be booked to this account unless the
+  # subtasks specify something different.
+# *** EXAMPLE: charge +
+  chargeset dev
+# *** EXAMPLE: charge -
+  # For the duration of the project we have running cost that are not
+  # included in the labor cost.
+# *** EXAMPLE: charge +
+  charge 170 perday
+# *** EXAMPLE: charge -
+
+# *** EXAMPLE: task1 +
+# *** EXAMPLE: spec +
+# *** EXAMPLE: charge +
+  task spec "Specification" {
+# *** EXAMPLE: charge -
+# *** EXAMPLE: task1 -
+# *** EXAMPLE: spec -
+    # The effort to finish this task is 20 man-days.
+# *** EXAMPLE: spec +
+    effort 20d
+# *** EXAMPLE: spec -
+    # Now we use the macro declared above to allocate the resources
+    # for this task. Because they can work in parallel, they may finish this
+    # task earlier than in 20 working-days.
+# *** EXAMPLE: spec +
+    ${allocate_developers}
+# *** EXAMPLE: spec -
+    # Each task without subtasks must have a start or an end
+    # criterion and a duration. For this task we use a reference to a
+    # milestone defined further below as the start criterion. So this task
+    # can not start before the specified milestone has been reached.
+    # References to other tasks may be relative. Each exclamation mark (!)
+    # means 'in the scope of the enclosing task'. To descent into a task, the
+    # fullstop (.) together with the id of the tasks have to be specified.
+# *** EXAMPLE: spec +
+    depends !deliveries.start
+# *** EXAMPLE: task1 +
+  }
+# *** EXAMPLE: task1 -
+# *** EXAMPLE: spec -
+
+# *** EXAMPLE: task1 +
+# *** EXAMPLE: software +
+  task software "Software Development" {
+# *** EXAMPLE: task1 -
+# *** EXAMPLE: software -
+
+    # The software is the most critical task of the project. So we set
+    # the priority of this task (and all its subtasks) to 1000, the top
+    # priority. The higher the priority, the more likely the task will
+    # get the requested resources.
+# *** EXAMPLE: software +
+    priority 1000
+# *** EXAMPLE: software -
+
+    # All subtasks depend on the specification task.
+    depends !spec
+
+# *** EXAMPLE: software +
+# *** EXAMPLE: database +
+    task database "Database coupling" {
+# *** EXAMPLE: software -
+      effort 20d
+      allocate dev1, dev2
+# *** EXAMPLE: software +
+    }
+# *** EXAMPLE: database -
+# *** EXAMPLE: software -
+
+# *** EXAMPLE: software +
+# *** EXAMPLE: gui +
+    task gui "Graphical User Interface" {
+# *** EXAMPLE: software -
+      effort 35d
+# *** EXAMPLE: gui -
+      # This task has taken 5 man-days more than originally planned.
+      # We record this as well, so that we can generate reports that
+      # compare the delayed schedule of the project to the original plan.
+# *** EXAMPLE: gui +
+      delayed:effort 40d
+      depends !database, !backend
+      allocate dev2, dev3
+# *** EXAMPLE: software +
+    }
+# *** EXAMPLE: gui -
+# *** EXAMPLE: software -
+
+# *** EXAMPLE: software +
+# *** EXAMPLE: backend +
+    task backend "Back-End Functions" {
+# *** EXAMPLE: software -
+      effort 30d
+# *** EXAMPLE: backend -
+      # This task is behind schedule, because it should have been
+      # finished already. To document this, we specify that the task
+      # is 95% completed. If nothing is specified, TaskJuggler assumes
+      # that the task is on schedule and computes the completion rate
+      # according to the current day and the plan data.
+# *** EXAMPLE: backend +
+      complete 95
+      depends !database
+      allocate dev1, dev2
+# *** EXAMPLE: software +
+    }
+# *** EXAMPLE: backend -
+# *** EXAMPLE: task1 +
+  }
+# *** EXAMPLE: task1 -
+# *** EXAMPLE: software -
+
+# *** EXAMPLE: task1 +
+# *** EXAMPLE: test +
+  task test "Software testing" {
+# *** EXAMPLE: task1 -
+
+    task alpha "Alpha Test" {
+# *** EXAMPLE: test -
+      # Efforts can not only be specified as man-days, but also as
+      # man-weeks, man-hours, etc. By default, TaskJuggler assumes
+      # that a man-week is 5 man-days or 40 man-hours. These values
+      # can be changed, of course.
+# *** EXAMPLE: test +
+      effort 1w
+# *** EXAMPLE: test -
+      # This task depends on a task in the scope of the enclosing
+      # task's enclosing task. So we need two exclamation marks (!!)
+      # to get there.
+# *** EXAMPLE: test +
+      depends !!software
+      allocate test, dev2
+      note "Hopefully most bugs will be found and fixed here."
+    }
+
+    task beta "Beta Test" {
+      effort 4w
+      depends !alpha
+      allocate test, dev1
+    }
+# *** EXAMPLE: task1 +
+  }
+# *** EXAMPLE: test -
+# *** EXAMPLE: task1 -
+
+# *** EXAMPLE: task1 +
+# *** EXAMPLE: manual +
+  task manual "Manual" {
+# *** EXAMPLE: task1 -
+    effort 10w
+    depends !deliveries.start
+    allocate doc, dev3
+    purge chargeset
+    chargeset doc
+# *** EXAMPLE: task1 +
+  }
+# *** EXAMPLE: manual -
+# *** EXAMPLE: task1 -
+
+# *** EXAMPLE: task1 +
+# *** EXAMPLE: deliveries +
+  task deliveries "Milestones" {
+# *** EXAMPLE: deliveries -
+# *** EXAMPLE: task1 -
+
+    # Some milestones have customer payments associated with them. We
+    # credit these payments to the 'rev' account.
+# *** EXAMPLE: deliveries +
+    purge chargeset
+    chargeset rev
+
+    task start "Project start" {
+# *** EXAMPLE: deliveries -
+      # A task that has no duration is a milestone. It only needs a
+      # start or end criterion. All other tasks depend on this task.
+# *** EXAMPLE: deliveries +
+      start 2002-01-16
+# *** EXAMPLE: deliveries -
+      # For some reason the actual start of the project got delayed.
+      # We record this, so that we can compare the planned run to the
+      # delayed run of the project.
+# *** EXAMPLE: deliveries +
+      delayed:start 2002-01-20
+# *** EXAMPLE: deliveries -
+      # At the beginning of this task we receive a payment from the
+      # customer. This is credited to the account associated with this
+      # task when the task starts.
+# *** EXAMPLE: deliveries +
+      charge 21000.0 onstart
+    }
+
+    task prev "Technology Preview" {
+      depends !!software.backend
+      startcredit 31000.0
+    }
+
+    task beta "Beta version" {
+      depends !!test.alpha
+      charge 13000.0 onstart
+    }
+
+    task done "Ship Product to Customer" {
+# *** EXAMPLE: deliveries -
+      # The next line can be uncommented to trigger a warning about
+      # the project being late. For all tasks, limits for the start and
+      # end values can be specified. Those limits are checked after the
+      # project has been scheduled. For all violated limits a warning
+      # is issued.
+# *** EXAMPLE: deliveries +
+      # maxend 2002-04-17
+      depends !!test.beta, !!manual
+      charge 33000.0 onstart
+    }
+# *** EXAMPLE: task1 +
+  }
+}
+# *** EXAMPLE: deliveries -
+# *** EXAMPLE: task1 -
+
+# Now the project has been specified completely. Stopping here would
+# result in a valid TaskJuggler file that could be processed and
+# scheduled. But no reports would be generated to visualize the
+# results.
+
+# A traditional Gantt chart with a project overview.
+# *** EXAMPLE: planoverview +
+htmltaskreport "ProjectPlanOverview.html" {
+  prolog '
+== Accounting Software Project ==
+----
+=== Project Overview ===
+
+The project is structured into 3 phases.
+
+# Specification
+# [[Development]]
+# Testing
+
+=== Project Plan ===
+'
+
+  headline "Project Plan Overview"
+  columns hierarchindex, name, start, end, effort, duration, cost,
+          revenue, chart
+  # For this report we like to have the abbreviated weekday in front
+  # of the date. %a is the tag for this.
+  timeformat "%a %Y-%m-%d"
+  loadunit days
+  hideresource 1
+  balance cost rev
+  caption '
+All effort values are in man days.
+'
+
+  epilog '
+=== Staffing ===
+
+All project phases are properly staffed. See [[ResourceGraph]] for
+detailed resource allocations.
+
+=== Current Status ===
+
+The project started off with a delay of 4 days. This slightly affected
+the original schedule. See [[Deliveries]] for the impact on the
+delivery dates.
+'
+}
+# *** EXAMPLE: planoverview -
+
+# A list of tasks showing the resources assigned to each task.
+htmltaskreport "Development.html" {
+  headline "Development - Resource Allocation Report"
+  columns hierarchindex, name, start, end, effort { title "Work" },
+          duration, chart { scale day }
+  timeformat "%Y-%m-%d"
+  loadunit days
+  hideresource ~isleaf()
+  sortresources name.up
+}
+
+# A list of all tasks with the percentage completed for each task
+htmltaskreport "Deliveries.html" {
+  headline "Project Deliveries"
+  columns hierarchindex, name, start, end, complete, chart
+  timeformat "%a %Y-%m-%d"
+  taskroot AcSo.deliveries
+  loadunit days
+  hideresource 1
+  scenarios plan, delayed
+}
+
+# A list of all employees with their contact details.
+htmlresourcereport "ContactList.html" {
+  headline "Contact list and duty plan"
+  columns name, Email { cellurl "mailto:$${Email}" }, Phone,
+          chart { scale day }
+  hideresource ~isleaf()
+  sortresources name.up
+  hidetask 1
+}
+
+# A graph showing resource allocation. It identifies whether each
+# resource is under- or over-allocated for.
+htmlresourcereport "ResourceGraph.html" {
+  headline "Resource Allocation Graph"
+  columns no, name, effort, rate, weekly #, utilization, freeload, chart
+  loadunit shortauto
+  hidetask ~isleaf()
+  sorttasks plan.start.up
+}
+
+# A list of all project resources, both human and material resources,
+# together with the associated costs.
+htmlresourcereport "ResourceSheet.html" {
+  headline "Resource Sheet"
+  columns no, name, id, effort, weekly, rate, cost
+  loadunit days
+  hidetask ~isleaf()
+  sorttasks plan.start.up
+  balance cost rev
+}
+
+# A list of resources and each task associated with each resource.
+htmlresourcereport "ResourceUsage.html" {
+  headline "Resource Usage Report"
+  columns no, name, chart { scale day } #, utilization, freeload, cost, chart
+  loadunit days
+  sorttasks plan.start.up
+  hidetask ~isleaf()
+  end 2002-02-10
+}
+
+csvtaskreport "csvtest.csv" {
+  columns no, name, id, effort, revenue, cost
+  loadunit days
+}
+