ursm-ditz 0.4

data/lib/views.rb

@@ -0,0 +1,136 @@
+require 'view'
+require 'html'
+
+module Ditz
+
+class ScreenView < View
+  def initialize project, config, device=$stdout
+    @device = device
+    @config = config
+  end
+
+  def format_log_events events
+    return "none" if events.empty?
+    events.reverse.map do |time, who, what, comment|
+      "- #{what} (#{who.shortened_email}, #{time.ago} ago)" +
+      (comment =~ /\S/ ? "\n" + comment.gsub(/^/, "  > ") : "")
+    end.join("\n")
+  end
+  private :format_log_events
+
+  def render_issue issue
+    status = case issue.status
+    when :closed
+      "#{issue.status_string}: #{issue.disposition_string}"
+    else
+      issue.status_string
+    end
+    desc = if issue.desc.size < 80 - "Description: ".length
+      issue.desc
+    else
+      "\n" + issue.desc.gsub(/^/, "  ") + "\n"
+    end
+    @device.puts <<EOS
+#{"Issue #{issue.name}".underline}
+      Title: #{issue.title}
+Description: #{desc}
+       Type: #{issue.type}
+     Status: #{status}
+    Creator: #{issue.reporter}
+        Age: #{issue.creation_time.ago}
+    Release: #{issue.release}
+ References: #{issue.references.listify "  "}
+ Identifier: #{issue.id}
+EOS
+
+    self.class.view_additions_for(:issue_summary).each { |b| @device.print(b[issue, @config] || next) }
+    puts
+    self.class.view_additions_for(:issue_details).each { |b| @device.print(b[issue, @config] || next)  }
+
+    @device.puts <<EOS
+Event log:
+#{format_log_events issue.log_events}
+EOS
+  end
+end
+
+class HtmlView < View
+  def initialize project, config, dir
+    @project = project
+    @config = config
+    @dir = dir
+    @template_dir = File.dirname Ditz::find_ditz_file("index.rhtml")
+  end
+
+  def render_all
+    Dir.mkdir @dir unless File.exists? @dir
+    FileUtils.cp File.join(@template_dir, "style.css"), @dir
+
+    ## build up links
+    links = {}
+    @project.releases.each { |r| links[r] = "release-#{r.name}.html" }
+    @project.issues.each { |i| links[i] = "issue-#{i.id}.html" }
+    @project.components.each { |c| links[c] = "component-#{c.name}.html" }
+    links["unassigned"] = "unassigned.html" # special case: unassigned
+    links["index"] = "index.html" # special case: index
+
+    @project.issues.each do |issue|
+      fn = File.join @dir, links[issue]
+      #puts "Generating #{fn}..."
+
+      extra_summary = self.class.view_additions_for(:issue_summary).map { |b| b[issue, @config] }.compact
+      extra_details = self.class.view_additions_for(:issue_details).map { |b| b[issue, @config] }.compact
+
+      erb = ErbHtml.new(@template_dir, links, :issue => issue,
+        :release => (issue.release ? @project.release_for(issue.release) : nil),
+        :component => @project.component_for(issue.component),
+        :project => @project)
+
+      extra_summary_html = extra_summary.map { |string, extra_binding| erb.render_string string, extra_binding }.join
+      extra_details_html = extra_details.map { |string, extra_binding| erb.render_string string, extra_binding }.join
+
+      File.open(fn, "w") { |f| f.puts erb.render_template("issue", { :extra_summary_html => extra_summary_html, :extra_details_html => extra_details_html }) }
+    end
+
+    @project.releases.each do |r|
+      fn = File.join @dir, links[r]
+      #puts "Generating #{fn}..."
+      File.open(fn, "w") do |f|
+        f.puts ErbHtml.new(@template_dir, links, :release => r,
+          :issues => @project.issues_for_release(r), :project => @project).
+          render_template("release")
+      end
+    end
+
+    @project.components.each do |c|
+      fn = File.join @dir, links[c]
+      #puts "Generating #{fn}..."
+      File.open(fn, "w") do |f|
+        f.puts ErbHtml.new(@template_dir, links, :component => c,
+          :issues => @project.issues_for_component(c), :project => @project).
+          render_template("component")
+      end
+    end
+
+    fn = File.join @dir, links["unassigned"]
+    #puts "Generating #{fn}..."
+    File.open(fn, "w") do |f|
+      f.puts ErbHtml.new(@template_dir, links,
+        :issues => @project.unassigned_issues, :project => @project).
+        render_template("unassigned")
+    end
+
+    past_rels, upcoming_rels = @project.releases.partition { |r| r.released? }
+    fn = File.join @dir, links["index"]
+    #puts "Generating #{fn}..."
+    File.open(fn, "w") do |f|
+      f.puts ErbHtml.new(@template_dir, links, :project => @project,
+        :past_releases => past_rels, :upcoming_releases => upcoming_rels,
+        :components => @project.components).
+        render_template("index")
+    end
+    puts "Local generated URL: file://#{File.expand_path(fn)}"
+  end
+end
+
+end

data/man/ditz.1

@@ -0,0 +1,38 @@
+.TH "ditz" "1" "0.4" "" ""
+.SH "NAME"
+ditz \- simple, light\-weight distributed issue tracker
+.SH "SYNOPSIS"
+\fBditz\fR [ \fIoptions\fR ] \fIcommand\fR [ \fIarguments\fR ]
+
+To list all available commands, use \fBditz help\fR.  To get help for a specific command, use \fBditz help
+command\fR.
+.SH "DESCRIPTION"
+Ditz is a simple, light\-weight distributed issue tracker designed to work with
+distributed version control systems like darcs and git. Ditz maintains an issue
+database directory on disk, with files written in a line\-based and human\-
+editable format. This directory is kept under version control alongside
+project code. Changes in issue state is handled by version control like code
+change: included as part of a commit, merged with changes from other
+developers, conflict\-resolved in the standard manner, etc.
+
+Ditz provides a simple, console\-based interface for creating and updating the
+issue database files, and some rudimentary HTML generation capabilities for
+producing world\-readable status pages. It offers no central public method of
+bug submission.
+.SH "AUTHOR"
+ditz was written by William Morgan <\fIwmorgan\-ditz@masanjin.net\fR>.
+
+This manpage was written for the Debian package of ditz by Christian Garbs
+<\fIdebian@cgarbs.de\fR>.
+.SH "LICENSE"
+Copyright (c) 2008 William Morgan.
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.

metadata

@@ -0,0 +1,90 @@
+--- !ruby/object:Gem::Specification 
+name: ursm-ditz
+version: !ruby/object:Gem::Version 
+  version: "0.4"
+platform: ruby
+authors: 
+- William Morgan
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2008-08-21 00:00:00 -07:00
+default_executable: ditz
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: hoe
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 1.7.0
+    version: 
+description: "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN.  Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code.  There are several different ways to use ditz:  1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.  Ditz provides a simple, console-based interface for creating and updating the issue database file, and some rudimentary static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). It currently offers no central public method of bug submission.   Synopsis:  # set up project. creates the bugs.yaml file. 1. ditz init 2. ditz add-release  # add an issue 3. ditz add"
+email: wmorgan-ditz@masanjin.net
+executables: 
+- ditz
+extensions: []
+
+extra_rdoc_files: 
+- README.txt
+files: 
+- Changelog
+- README.txt
+- Rakefile
+- ReleaseNotes
+- bin/ditz
+- lib/component.rhtml
+- lib/ditz.rb
+- lib/hook.rb
+- lib/html.rb
+- lib/index.rhtml
+- lib/issue.rhtml
+- lib/issue_table.rhtml
+- lib/lowline.rb
+- lib/model-objects.rb
+- lib/model.rb
+- lib/operator.rb
+- lib/release.rhtml
+- lib/trollop.rb
+- lib/style.css
+- lib/unassigned.rhtml
+- lib/util.rb
+- lib/view.rb
+- lib/views.rb
+- lib/plugins/git.rb
+- lib/plugins/issue-claiming.rb
+- lib/vendor/yaml_waml.rb
+- contrib/completion/ditz.bash
+- contrib/completion/_ditz.zsh
+- man/ditz.1
+has_rdoc: true
+homepage: http://ditz.rubyforge.org
+post_install_message: 
+rdoc_options: 
+- --main
+- README.txt
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+requirements: []
+
+rubyforge_project: ditz
+rubygems_version: 1.2.0
+signing_key: 
+specification_version: 2
+summary: A simple issue tracker designed to integrate well with distributed version control systems like git and darcs. State is saved to a YAML file kept under version control, allowing issues to be closed/added/modified as part of a commit.
+test_files: []
+