codersdojo 1.2.11 → 1.2.12

data/app/meta_config_file.rb

@@ -0,0 +1,17 @@
+class MetaConfigFile
+
+	PROPERTY_FILENAME = '.meta'	
+	
+	def initialize shell
+		@shell = shell
+	end
+	
+	def framework_property
+		properties['framework']
+	end
+
+	def properties
+	  @shell.read_properties PROPERTY_FILENAME
+	end
+	
+end

data/app/scheduler.rb

@@ -27,7 +27,7 @@ class Scheduler
 		@view.show_kata_exit_message 
 		@last_action = @view.read_user_input.downcase
 		@commands.each do |command|
-			if @last_action == command.command_key
+			if @last_action.start_with? command.command_key
 				command.execute
 			end
 		end

data/app/start_command.rb

@@ -1,8 +1,12 @@
+require 'meta_config_file'
+require 'scheduler'
+
 class StartCommand
 	
 	def initialize shell, view, upload_command
 		@shell = shell
 		@view = view
+		@meta_file = MetaConfigFile.new @shell
 		@upload_command = upload_command
 	end
 	
@@ -14,7 +18,7 @@ class StartCommand
 		unless command then @view.show_missing_command_argument_error "start", "shell_command"; return end
 		unless file then @view.show_missing_command_argument_error "start", "kata_file"; return end
 		command = expand_run_command command
-	  @view.show_start_kata command, file, framework_property
+	  @view.show_start_kata command, file, @meta_file.framework_property
 	  dojo = Runner.new @shell, SessionIdGenerator.new
 	  dojo.file = file
 	  dojo.run_command = command
@@ -34,12 +38,4 @@ class StartCommand
 		end
 	end
 	
-	def framework_property
-		properties['framework']
-	end
-
-	def properties
-	  @shell.read_properties PROPERTY_FILENAME
-	end
-
 end

data/app/upload_command.rb

@@ -1,9 +1,8 @@
+require 'meta_config_file'
 require 'uploader'
 
 class UploadCommand
 
-	PROPERTY_FILENAME = '.meta'
-
 	attr_accessor :uploader
 
 	def initialize shell, view, hostname
@@ -11,10 +10,11 @@ class UploadCommand
 		@view = view
 		@hostname = hostname
 		@uploader = Uploader.new(hostname, '', '')
+		@meta_file = MetaConfigFile.new @shell
 	end
 
 	def execute
-		upload nil, nil
+		upload nil
 	end
 
 	def execute_from_shell params
@@ -23,7 +23,7 @@ class UploadCommand
 
 	def upload session_directory, open_browser=true
 		formatter = FilenameFormatter.new
-		framework = framework_property
+		framework = @meta_file.framework_property
 		if not session_directory then
 			session_directory = formatter.session_dir @shell.newest_dir_entry(FilenameFormatter.codersdojo_workspace) 
 		end
@@ -46,12 +46,4 @@ class UploadCommand
 		command == 'upload'
 	end
 	
-	def framework_property
-		properties['framework']
-	end
-
-	def properties
-	  @shell.read_properties PROPERTY_FILENAME
-	end
-	
 end

data/templates/clojure.is-test/README

@@ -9,3 +9,5 @@ Assumptions:
   - The whole kata source code is in the one %kata_file%.clj.
   - Java is installed on your system and 'java' is in the path.
   - clojure.jar and clojure-contrib.jar are placed in the 'lib' directory.
+
+The support for Clojure/Is-Test was contributed by Stefan Roock.

data/templates/cpp.gtest/README

@@ -12,3 +12,4 @@ Assumptions:
   - If your IDE does the compilation and linking, you should remove the first 3 lines
     in the run-once.%sh% file.
 
+The support for C++/GTest was contributed by Stefan Roock.

data/templates/csharp.nunit/README

@@ -12,3 +12,5 @@ Assumptions:
       nunit-console    (possible path=C:\Programme\NUnit 2.5.9\bin\net-2.0\)
   - nunit.framework.dll is in the same directory as %Kata_file%.cs.
   - The whole kata source code is in the one %Kata_file%.cs.
+
+The support for C#/NUnit was contributed by Meike Mertsch.

data/templates/forth.tester/README

@@ -7,3 +7,5 @@ Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-e
 
 Assumptions:
   - The whole kata source code is in the one %kata_file%.fth.
+
+The support for Forth/Tester was contributed by Stefan Roock.

data/templates/groovy.gunit/README

@@ -9,3 +9,5 @@ Assumptions:
   - Java and Groovy is installed on your system, 'groovy' is in the path and GROOVY_HOME is set.
   - groovy.jar is placed in the 'lib' directory.
   - The whole kata source code is in the one %Kata_file%Test.groovy.
+
+The support for Groovy/GUnit was contributed by Stefan Roock.

data/templates/java.junit/README

@@ -15,3 +15,5 @@ Assumptions:
   - The kata source file has a main method that starts the tests.
   - If your IDE (like Eclipse) compiles the source file, you should remove the first two lines
     in the run-once.%sh% file.
+
+The support for Java/JUnit was contributed by Stefan Roock.

data/templates/javascript.jspec/README

@@ -6,4 +6,6 @@ These files were created:
 Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-endless.%sh%.)
 
 Assumptions:
-  - The whole kata source code is in the one spec.js.
+  - The whole kata source code is in the one spec.js.
+
+The support for JavaScript/JSpec was contributed by Marko Schulz.

data/templates/javascript.vows/README

@@ -5,4 +5,6 @@ These files were created:
 Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-endless.%sh%.)
 
 Assumptions:
-  - The whole kata source code is in the one %kata_file%.js.
+  - The whole kata source code is in the one %kata_file%.js.
+
+The support for JavaScript/Vows was contributed by Matthias Lübken.

data/templates/perl.test/README

@@ -7,3 +7,5 @@ Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-e
 
 Assumptions:
   - The whole kata source code is in the one %kata_file%.pl.
+
+The support for Perl/Test was contributed by Stefan Roock.

data/templates/python.pytest/README

@@ -7,3 +7,5 @@ Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-e
 
 Assumptions:
   - The whole kata source code is in the one %kata_file%.py.
+
+The support for Python/PyTest was contributed by Sebastian Sanitz (github.com/sanitz).

data/templates/python.pyunit/README

@@ -7,3 +7,5 @@ Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-e
 
 Assumptions:
   - The whole kata source code is in the one %kata_file%.py.
+
+The support for Python/PyUnit was contributed by Steven Collins.

data/templates/ruby.rspec/README

@@ -7,3 +7,5 @@ Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-e
 
 Assumptions:
   - The whole kata source code is in the one %kata_file%.rb.
+
+The support for Ruby/RSpec was contributed by Stefan Roock.

data/templates/ruby.test-unit/README

@@ -7,3 +7,5 @@ Run run-endless.%sh% and start your kata. (On Mac/Linux you have to call ./run-e
 
 Assumptions:
   - The whole kata source code is in the one %kata_file%.rb.
+
+The support for Ruby/TestUnit was contributed by Stefan Roock.

data/templates/scala.junit/README

@@ -15,3 +15,5 @@ Assumptions:
   - The kata source file has a main method that starts the tests.
   - If your IDE (like Eclipse) compiles the source file, you should remove the first two lines
     in the run-once.%sh% file.
+
+The support for Scala/JUnit was contributed by Manuel Küblböck (Twitter: http://twitter.com/#!/ManuelKublbock, Web: http://qualityswdev.com).

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: codersdojo
 version: !ruby/object:Gem::Version 
-  hash: 9
+  hash: 7
   prerelease: false
   segments: 
   - 1
   - 2
-  - 11
-  version: 1.2.11
+  - 12
+  version: 1.2.12
 platform: ruby
 authors: 
 - CodersDojo-Team
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-05-07 00:00:00 +02:00
+date: 2011-05-09 00:00:00 +02:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -66,6 +66,7 @@ files:
 - app/generate_command.rb
 - app/help_command.rb
 - app/info_property_file.rb
+- app/meta_config_file.rb
 - app/progress.rb
 - app/property_file_missing_exception.rb
 - app/runner.rb