tau 0.1.0 → 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 38c4dff2363ca430cd01fca3bff75b5d3cebbb11
+  data.tar.gz: 6ab29e90496e18e8b035d0c0e1d0a51191b6e4e9
+SHA512:
+  metadata.gz: e2882456f5986a5ea2ab5b8979739829fa61668b6c45065a9a54679271815f939641aa72e3740e3331489c410ae4ece9367e91f8175b67ce34d3db095347b685
+  data.tar.gz: 6188a8b0c7d8898cd9a406259f16e0867ec2ec354e411347c889021206f3abefe4017845d26a1a8b3e4ee41549575c536fde929d97624d9fab1865c6de4dafc0

data/.travis.yml

@@ -0,0 +1,4 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0.0

data/Gemfile

@@ -2,3 +2,7 @@ source "http://rubygems.org"
 
 # Specify your gem's dependencies in tau.gemspec
 gemspec
+
+group :test do
+  gem 'rake'
+end

data/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Dmitry Zhlobo
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,93 +1,99 @@
-Tau
-===
-
-Tau provides you write code of webpages using modern technologies such as 
-haml, sass, coffee-script. You dont't need to compile your code to HTML and
-CSS by hand everytime you something change.
-
-Installation
-------------
-
-    gem install tau
-
-Usage
------
-
-It's pretty simple.
-
-### Getting started
-
-1. Start new coding project and switch to that. In the command prompt run:
-
-    `tau new example.com; cd example.com` *(where example.com is the project name)*
-
-2. Create html or haml file on code directory:
-
-    `echo "%h1 Hello <strong>tau</strong>!" > code/hello.haml`
-
-3. Start server and go to [http://localhost:15000/hello.html](http://localhost:15000/hello.html):
-
-    `tau server`
-
-Attend even if you write hello.**haml** file you can see it by hello.**html**
-in browser.
-
-### Creating new project
-
-Run `tau new projectname` and tau will make directory tree for you:
-  
-    projectname
-    |--code - for your .html and .haml files
-    |  |--js - for .js and .coffee files
-    |  |--css - for .css, .sass and .scss
-    |  `--img - for any type of images
-    |
-    `--tau.yaml - config file 
-
-### Coding
-
-Run `tau server` in your project directory. Then put any html or haml files
-into **code** directory, js or coffee files into **code/js**, css, sass or
-scss into **code/css**. Now you can view files in browser by 
-http://localhost:15000/page.html or http://localhost:15000/css/style.css or 
-http://localhost:15000/js/script.js.
-
-Attend that tau changes files extensions in browser from haml to html, from 
-coffee to js, from sass and scss to css. For example if you have 
-**code/js/myscript.coffee** file you can see it in browser by 
-http://localhost:15000/js/myscript.js.
-
-In html or haml file you can include scripts written in coffee and styles 
-written in sass or scss. For example if you have **code/js/script.coffee** 
-script and **code/js/style.sass** spreadsheet you can include it to html by 
-lines:
-```html
-    <script src='js/script.js'></script>
-    <link rel="stylesheet" href="css/style.css">
-```
-Anytime you change any file you can see updated version in browser. You don't 
-need to compile anything by hand.
-
-### Building project
-
-If you want to compile all files for releasing it in internet you don't need do
-it by hand. `tau build` command compiles all sass, haml and other files and put
-them into **build/** directory. Any files from **img** directory and not a haml, sass 
-or coffee-script files will copied without any changes. For example:
-```
-code/index.haml  ->  build/index.html
-code/js/script.coffee  ->  build/js/script.js
-code/img/logo.png  ->  build/img/logo.png
-code/humans.txt  ->  build/humans.txt
-etc...
-```
-
-License
--------
-
-You can use tau by MIT License.
-
-Contributing
-------------
-
-Feel free to fork and pull request.
+Tau [![Build Status](https://secure.travis-ci.org/Proghat/tau.png?branch=master)](http://travis-ci.org/Proghat/tau) [![Gem Version](https://badge.fury.io/rb/tau.png)](http://badge.fury.io/rb/tau)
+===
+
+Tau provides you write code of webpages using modern technologies such as
+haml, sass, coffee-script. You dont't need to compile your code to HTML and
+CSS by hand everytime you something change.
+
+Requirements
+------------
+
+You need ruby version **1.9.3** installed. See [rvm](https://rvm.io/).
+
+
+Installation
+------------
+
+    gem install tau
+
+Usage
+-----
+
+It's pretty simple.
+
+### Getting started
+
+1. Start new coding project and switch to that. In the command prompt run:
+
+    `tau new example.com; cd example.com` *(where example.com is the project name)*
+
+2. Create html or haml file on code directory:
+
+    `echo '%h1 Hello <strong>tau</strong>!' > code/hello.haml`
+
+3. Start server and go to [http://localhost:15000/hello.html](http://localhost:15000/hello.html):
+
+    `tau server`
+
+Attend even if you write hello.**haml** file you can see it by hello.**html**
+in browser.
+
+### Creating new project
+
+Run `tau new projectname` and tau will make directory tree for you:
+
+    projectname
+    |--code - for your .html and .haml files
+    |  |--js - for .js and .coffee files
+    |  |--css - for .css, .sass and .scss
+    |  `--img - for any type of images
+    |
+    `--tau.yaml - config file
+
+### Coding
+
+Run `tau server` in your project directory. Then put any html or haml files
+into **code** directory, js or coffee files into **code/js**, css, sass or
+scss into **code/css**. Now you can view files in browser by
+http://localhost:15000/page.html or http://localhost:15000/css/style.css or
+http://localhost:15000/js/script.js.
+
+Attend that tau changes files extensions in browser from haml to html, from
+coffee to js, from sass and scss to css. For example if you have
+**code/js/myscript.coffee** file you can see it in browser by
+http://localhost:15000/js/myscript.js.
+
+In html or haml file you can include scripts written in coffee and styles
+written in sass or scss. For example if you have **code/js/script.coffee**
+script and **code/js/style.sass** spreadsheet you can include it to html by
+lines:
+```html
+    <script src='js/script.js'></script>
+    <link rel="stylesheet" href="css/style.css">
+```
+Anytime you change any file you can see updated version in browser. You don't
+need to compile anything by hand.
+
+### Building project
+
+If you want to compile all files for releasing it in internet you don't need do
+it by hand. `tau build` command compiles all sass, haml and other files and put
+them into **build/** directory. Any files from **img** directory and not a haml, sass
+or coffee-script files will copied without any changes. For example:
+```
+code/index.haml  ->  build/index.html
+code/js/script.coffee  ->  build/js/script.js
+code/img/logo.png  ->  build/img/logo.png
+code/humans.txt  ->  build/humans.txt
+etc...
+```
+
+License
+-------
+
+You can use tau by MIT License.
+
+Contributing
+------------
+
+Feel free to fork and pull request.

data/Rakefile

@@ -1 +1,8 @@
 require "bundler/gem_tasks"
+require "cucumber/rake/task"
+
+Cucumber::Rake::Task.new(:test) do |t|
+  t.cucumber_opts = "features --format pretty"
+end
+
+task :default => :test

data/bin/tau

@@ -1,4 +1,4 @@
 #!/usr/bin/env ruby
 require 'tau/cli'
 
-Tau::Cli.start
+Tau::Cli.start

data/features/builder.feature

@@ -1,41 +1,41 @@
-Feature: Builder
-  In order to avoid compiling all files by hand
-  As a web developer
-  I want tau compile all files for me
-
-  Background: making project
-    Given I successfully run `tau new project2build`
-    And I cd to "project2build"
-
-  Scenario: building project
-    Given a file named "code/hamltest.haml" with:
-      """
-      %h1 Hello, world!
-      %strong I'm tau ;)
-      """
-    And a file named "code/js/coffeetest.coffee" with:
-      """
-      square = (x) -> x * x
-      cube   = (x) -> square(x) * x
-      """
-    And a file named "code/css/sasstest.sass" with:
-      """
-      $blue: #3bbfce
-      .content-navigation
-        border-color: $blue
-        color: darken($blue, 9%)
-      """
-    And a file named "code/css/scsstest.scss" with:
-      """
-      $blue: #3bbfce;
-      .content-navigation {
-        border-color: $blue;
-        color:
-          darken($blue, 9%);
-      }
-      """
-    When I successfully run `tau build`
-    Then I should see file "build/hamltest.html" compiled from haml in "code/hamltest.haml"
-    And I should see file "build/js/coffeetest.js" compiled from coffee-script in "code/js/coffeetest.coffee"
-    And I should see file "build/css/sasstest.css" compiled from sass in "code/css/sasstest.sass"
-    And I should see file "build/css/scsstest.css" compiled from scss in "code/css/scsstest.scss"
+Feature: Builder
+  In order to avoid compiling all files by hand
+  As a web developer
+  I want tau compile all files for me
+
+  Background: making project
+    Given I successfully run `tau new project2build`
+    And I cd to "project2build"
+
+  Scenario: building project
+    Given a file named "code/hamltest.haml" with:
+      """
+      %h1 Hello, world!
+      %strong I'm tau ;)
+      """
+    And a file named "code/js/coffeetest.coffee" with:
+      """
+      square = (x) -> x * x
+      cube   = (x) -> square(x) * x
+      """
+    And a file named "code/css/sasstest.sass" with:
+      """
+      $blue: #3bbfce
+      .content-navigation
+        border-color: $blue
+        color: darken($blue, 9%)
+      """
+    And a file named "code/css/scsstest.scss" with:
+      """
+      $blue: #3bbfce;
+      .content-navigation {
+        border-color: $blue;
+        color:
+          darken($blue, 9%);
+      }
+      """
+    When I successfully run `tau build`
+    Then I should see file "build/hamltest.html" compiled from haml in "code/hamltest.haml"
+    And I should see file "build/js/coffeetest.js" compiled from coffee-script in "code/js/coffeetest.coffee"
+    And I should see file "build/css/sasstest.css" compiled from sass in "code/css/sasstest.sass"
+    And I should see file "build/css/scsstest.css" compiled from scss in "code/css/scsstest.scss"

data/features/making_projects.feature

@@ -1,20 +1,20 @@
-Feature: Making new projects
-  In order to avoid making project directory myself
-  As a web developer
-  I want tau make project for me
-
-  Scenario: making new project by tau
-    When I successfully run `tau new test_project`
-    Then there should be right project directory "test_project"
-
-  Scenario: making project with dot in project name
-  	When I successfully run `tau new .test.project.`
-  	Then there should be right project directory ".test.project."
-
-  Scenario: making project with cyrillic name
-    When I successfully run `tau new тест`
-    Then there should be right project directory "тест"
-
-  Scenario: making project with "-" symbol in project name
-    When I successfully run `tau new -test-project-`
-    Then there should be right project directory "-test-project-"
+Feature: Making new projects
+  In order to avoid making project directory myself
+  As a web developer
+  I want tau make project for me
+
+  Scenario: making new project by tau
+    When I successfully run `tau new test_project`
+    Then there should be right project directory "test_project"
+
+  Scenario: making project with dot in project name
+  	When I successfully run `tau new .test.project.`
+  	Then there should be right project directory ".test.project."
+
+  Scenario: making project with cyrillic name
+    When I successfully run `tau new тест`
+    Then there should be right project directory "тест"
+
+  Scenario: making project with "-" symbol in project name
+    When I successfully run `tau new -test-project-`
+    Then there should be right project directory "-test-project-"

data/features/step_definitions/fs.rb

@@ -1,20 +1,20 @@
-Then /^there should be right project directory "(.*)"$/ do |project_dir|
-  tau_dirs = ['/code', 'code/js', 'code/css', 'code/img'].map { |dir| "#{project_dir}/#{dir}" }
-  check_directory_presence(tau_dirs, true)
-  tau_files = ['tau.yml'].map { |file| "#{project_dir}/#{file}" }
-  check_file_presence(tau_files, true)
-end
-
-Then /^I should see file "(.*)" compiled from (haml|sass|scss|coffee-script) in "(.*)"$/ do |compiled_file, lang, src_file|
-  compiled_file_content = nil
-  src_file_content = nil
-  in_current_dir do
-    compiled_file_content = File.read compiled_file
-    src_file_content = File.read src_file
-  end
-  compiled_file_content.should == render(src_file_content, lang)
-end
-
-Given /^I'm on sandbox project directory$/ do
-  @dirs = [SANDBOX_PROJECT_DIR]
-end
+Then /^there should be right project directory "(.*)"$/ do |project_dir|
+  tau_dirs = ['/code', 'code/js', 'code/css', 'code/img'].map { |dir| "#{project_dir}/#{dir}" }
+  check_directory_presence(tau_dirs, true)
+  tau_files = ['tau.yml'].map { |file| "#{project_dir}/#{file}" }
+  check_file_presence(tau_files, true)
+end
+
+Then /^I should see file "(.*)" compiled from (haml|sass|scss|coffee-script) in "(.*)"$/ do |compiled_file, lang, src_file|
+  compiled_file_content = nil
+  src_file_content = nil
+  in_current_dir do
+    compiled_file_content = File.read compiled_file
+    src_file_content = File.read src_file
+  end
+  compiled_file_content.should == render(src_file_content, lang)
+end
+
+Given /^I'm on sandbox project directory$/ do
+  @dirs = [SANDBOX_PROJECT_DIR]
+end

data/features/support/env.rb

@@ -1,4 +1,4 @@
-# Include useful steps. 
+# Include useful steps.
 # See full list at https://github.com/cucumber/aruba/blob/master/lib/aruba/cucumber.rb
 require 'aruba/cucumber'
 
@@ -6,6 +6,12 @@ require 'aruba/cucumber'
 # See https://github.com/cucumber/aruba/blob/master/lib/aruba/api.rb for more information
 require 'aruba/api'
 
+# Prepare test environment.
+# Build and intall our gem.
+# `tau something` command will be executed in test environment.
+require File.expand_path("#{File.dirname(__FILE__)}/cukegem.rb")
+CukeGem.setup('tau.gemspec')
+
 # Making test project and start server on it
 require 'childprocess'
 FileUtils::mkdir_p('tmp/sandbox')
@@ -13,11 +19,11 @@ server_process = nil
 Dir.chdir('tmp/sandbox') do
   FileUtils::rm_rf('servertesting')
   # Create new project. TODO: think what if tau projecter not works correctly
-  ChildProcess.build('tau new servertesting').start.wait
+  ChildProcess.build('tau', 'new', 'servertesting').start.wait
 
   # Run server on test project directory
   Dir.chdir('servertesting') do
-    server_process = ChildProcess.build('tau server')
+    server_process = ChildProcess.build('tau', 'server')
     server_process.start
   end
 end
@@ -27,9 +33,3 @@ SANDBOX_PROJECT_DIR = File.expand_path('tmp/sandbox/servertesting')
 at_exit do
   server_process.stop
 end
-
-# Prepare test environment.
-# Build and intall our gem.
-# `tau something` command will be executed in test environment.
-require File.expand_path("#{File.dirname(__FILE__)}/cukegem.rb")
-CukeGem.setup('tau.gemspec')