RubyGems - bookshop - Versions diffs - 0.0.15 → 0.0.16 - Mend

bookshop 0.0.15 → 0.0.16

Files changed (26) hide show

data/CHANGELOG CHANGED Viewed

@@ -1,3 +1,19 @@
+0.0.16:
+	Features
+		Added importing <%= import(your_source_file.html.erb) %> functionality for ERB source
+			files, providing subtemplating, allowing for cleaner code layouts.
+	Documentation
+		Edited the example book which is generated with 'bookshop new'. The new layout
+			demonstrates how to utilize the <%= import(your_source_file.html.erb) %> for
+			including sub-files.
+	Removed 'Tools' subfolder including Kindlegen and Epubcheck - I will include them
+		in a future release. But removed for now to save bandwidth and reduce gem size.
+	Made 'book/' the assumed directory for source in 'bookshop build' command and
+		removed 'book/' prefix in all of the layout imports
 0.0.15:
 	Features
 		Added ERB functionality to the book source

data/README.rdoc CHANGED Viewed

@@ -1,10 +1,10 @@
 == Welcome to bookshop
-bookShop is a publishing framework for html-to-(e)book toolchain happiness and sustainable productivity. The framework is optimized to help developers quickly ramp-up, allowing them to more rapidly jump in and develop their html-to-(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over configuration, setting them up with best practices, standards and tools from the start.
+bookShop is a publishing framework for html-to-pdf/(e)book toolchain happiness and sustainable productivity. The framework is optimized to help developers quickly ramp-up, allowing them to more rapidly jump in and develop their html-to-(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over configuration, setting them up with best practices, standards and tools from the start.
 bookshop hopes to simplify the process by:
 * using common developer tools like HTML, CSS, etc. to make the creation of your book comfortable and familiar, greatly reducing the learning curve for your developers, authors, agents, and other team members
-* providing a Ruby Gem to make building a book from HTML as easy as 'sudo gem install bookshop'
+* providing a Ruby Gem to make building a book from HTML as easy as 'gem install bookshop'
 * pulling all the html-to-(e)book tools together into one place (wkhtmltopdf, kindlegen, epubcheck)
 * sticking with open-source tools
 * giving the developer a set of scripts to automate the redundant stuff
@@ -17,7 +17,6 @@ bookshop hopes to simplify the process by:
 * Ruby v1.8.7 or v1.9.2 http://www.ruby-lang.org/en/downloads/
 * Rubygems v1.3.6 http://docs.rubygems.org/read/chapter/3
-* Java v1.6 http://www.java.com/
 == Installation
@@ -62,13 +61,18 @@ All of the source documents/code/assets (yay... HTML/CSS) for your book are stor
   or
+    items = [ "ball", "stick", "corgi" ]
     <ul>
-      <% for @item in @shopping_list %>
-        <li><%= @item %></li>
+      <% items.each do |item| %>
+        <li><%= item %></li>
       <% end %>
     </ul>
 * include other files or template structures
+    <%= import(your_source_file.erb.html) %>
 * explore other creative ways to structure and enhance your book (we'd love to see how you are doing it)
 When the book is built, your master +book/book.html.erb+ file will be compiled into the final HTML which will be used to build the book types.
@@ -164,5 +168,4 @@ We would like to thank:
 * The Ruby/Rubygems Team www.ruby-lang.org/
 * The Thor Team - https://github.com/wycats/thor
 * Hakon Wium Lie and Bert Bos for developing the book microformat http://www.alistapart.com/articles/boom
-* The WKHTMLTOPDF team http://code.google.com/p/wkhtmltopdf/
-* The EPUBCHECK team http://code.google.com/p/epubcheck/
+* The WKHTMLTOPDF team http://code.google.com/p/wkhtmltopdf/

data/bookshop.gemspec CHANGED Viewed

@@ -9,10 +9,10 @@ Gem::Specification.new do |s|
   s.authors     = ['D.a. Thompson']
   s.email       = ['da@blueheadpublishing.com']
   s.homepage    = "http://rubygems.org/gems/bookshop"
-  s.summary     = "A publishing framework for html-to-(e)book toolchain happiness and sustainable productivity."
-  s.description = "bookShop is a publishing framework for html-to-(e)book toolchain happiness and sustainable productivity.
+  s.summary     = "A publishing framework for html-to-pdf/(e)book toolchain happiness and sustainable productivity."
+  s.description = "bookShop is a publishing framework for html-to-pdf/(e)book toolchain happiness and sustainable productivity.
                     The framework is optimized to help developers quickly ramp-up, allowing them to more rapidly
-                    jump in and develop their html-to-(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over
+                    jump in and develop their html-to-pdf/(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over
                     configuration, setting them up with best practices, standards and tools from the start."
   s.license     = "MIT"
@@ -22,7 +22,6 @@ Gem::Specification.new do |s|
   s.add_dependency "thor", ">= 0.14.6"
-  s.add_dependency "nokogiri"
   s.add_development_dependency "bundler", ">= 1.0.0"
   s.add_development_dependency "rspec"

data/lib/bookshop/commands/build.rb CHANGED Viewed

@@ -17,7 +17,10 @@ module Bookshop
       build = ARGV.shift
       build = aliases[build] || build
-      erb = ERB.new(File.read('book/book.html.erb'))
+      # Renders <%= import(source.html.erb) %> files with ERB
+      def self.import(file)
+        ERB.new(File.read('book/'+file)).result(binding).gsub(/\n$/,'')
+      end
       # Define arguments and options
       argument :type
@@ -27,6 +30,8 @@ module Bookshop
         File.dirname(__FILE__)
       end
+      erb = import('book.html.erb')
       case build
       # 'build html' creates a html version of the book
@@ -37,7 +42,7 @@ module Bookshop
         puts "Generating new html from erb"
         File.open('builds/html/book.html', 'a') do |f|
-          f << erb.result
+          f << erb
         end
         FileUtils.cp_r('book/css/', 'builds/html/', :verbose => true)
@@ -53,7 +58,7 @@ module Bookshop
         # Generate the html from ERB
         puts "Generating new html from erb"
         File.open('builds/html/book.html', 'a') do |f|
-          f << erb.result
+          f << erb
         end
         # Copy over html assets

data/lib/bookshop/generators/bookshop/app/app_generator.rb CHANGED Viewed

@@ -23,15 +23,15 @@ module Bookshop
       end
       # Adds third-party tools
-      def add_tools
-        directory "tools/", "#{app_path}/tools/"
-      end
+      # def add_tools
+      #   directory "tools/", "#{app_path}/tools/"
+      # end
       # Change the permissions so tools are executable
-      def chmod_tools
-        chmod "#{app_path}/tools/epubcheck-1.2.jar", 0755
-        chmod "#{app_path}/tools/kindlegen", 0755
-      end
+      # def chmod_tools
+      #  chmod "#{app_path}/tools/epubcheck-1.2.jar", 0755
+      #  chmod "#{app_path}/tools/kindlegen", 0755
+      # end
     protected

data/lib/bookshop/generators/bookshop/app/templates/README.rdoc CHANGED Viewed

@@ -1,10 +1,10 @@
 == Welcome to bookshop
-bookShop is a publishing framework for html-to-(e)book toolchain happiness and sustainable productivity. The framework is optimized to help developers quickly ramp-up, allowing them to more rapidly jump in and develop their html-to-(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over configuration, setting them up with best practices, standards and tools from the start.
+bookShop is a publishing framework for html-to-pdf/(e)book toolchain happiness and sustainable productivity. The framework is optimized to help developers quickly ramp-up, allowing them to more rapidly jump in and develop their html-to-(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over configuration, setting them up with best practices, standards and tools from the start.
 bookshop hopes to simplify the process by:
 * using common developer tools like HTML, CSS, etc. to make the creation of your book comfortable and familiar, greatly reducing the learning curve for your developers, authors, agents, and other team members
-* providing a Ruby Gem to make building a book from HTML as easy as 'sudo gem install bookshop'
+* providing a Ruby Gem to make building a book from HTML as easy as 'gem install bookshop'
 * pulling all the html-to-(e)book tools together into one place (wkhtmltopdf, kindlegen, epubcheck)
 * sticking with open-source tools
 * giving the developer a set of scripts to automate the redundant stuff
@@ -17,7 +17,6 @@ bookshop hopes to simplify the process by:
 * Ruby v1.8.7 or v1.9.2 http://www.ruby-lang.org/en/downloads/
 * Rubygems v1.3.6 http://docs.rubygems.org/read/chapter/3
-* Java v1.6 http://www.java.com/
 == Installation
@@ -62,13 +61,18 @@ All of the source documents/code/assets (yay... HTML/CSS) for your book are stor
   or
+    items = [ "ball", "stick", "corgi" ]
     <ul>
-      <% for @item in @shopping_list %>
-        <li><%= @item %></li>
+      <% items.each do |item| %>
+        <li><%= item %></li>
       <% end %>
     </ul>
 * include other files or template structures
+    <%= import(your_source_file.erb.html) %>
 * explore other creative ways to structure and enhance your book (we'd love to see how you are doing it)
 When the book is built, your master +book/book.html.erb+ file will be compiled into the final HTML which will be used to build the book types.
@@ -164,5 +168,4 @@ We would like to thank:
 * The Ruby/Rubygems Team www.ruby-lang.org/
 * The Thor Team - https://github.com/wycats/thor
 * Hakon Wium Lie and Bert Bos for developing the book microformat http://www.alistapart.com/articles/boom
-* The WKHTMLTOPDF team http://code.google.com/p/wkhtmltopdf/
-* The EPUBCHECK team http://code.google.com/p/epubcheck/
+* The WKHTMLTOPDF team http://code.google.com/p/wkhtmltopdf/

data/lib/bookshop/generators/bookshop/app/templates/book/book.html.erb CHANGED Viewed

@@ -3,264 +3,18 @@
 <html><head>
 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
 <title>Cascading Style Sheets - Designing for the Web</title>
-<meta name="author" content="H�kon Wium Lie">
 <link rel="stylesheet" type="text/css" href="css/stylesheet.css">
 </head>
 <body>
-<div class="frontcover">
-<img src="images/canvas.jpg">
-<h1>Cascading Style Sheets</h1>
-<h2>Designing for the Web</h2>
-<h3>Third Edition</h3>
-<p>Sample document</p>
-</div>
+<%= import('cover.html.erb')%>
+<%= import('toc.html.erb')%>
+<%= import('preface.html.erb')%>
-<div class="halftitlepage">
-<h1 class="no-toc">Cascading Style Sheets</h1>
-<h2 class="no-toc">Designing for the Web</h2>
-<h3 class="no-toc">Third Edition</h3>
-</div>
+<!-- Chapter 01 has the imports included inside of it -->
+<%= import('ch01/ch01.html.erb')%>
-<div class="titlepage">
-<h1 class="no-toc">Cascading Style Sheets</h1>
-<h2 class="no-toc">Designing for the Web</h2>
-<h3 class="no-toc">Third Edition</h3>
-<p class="no-toc">H�kon Wium Lie<br>Bert Bos</p>
-<!-- also, the publisher's name would typically be printed here -->
-</div>
-<div class="imprint">
-<p>Copyright � 2005 H�kon Wium Lie and Bert Bos</p>
-</div>
-<div class="toc" id="toc-h-1">
-<h1>Table of Contents</h1>
-<ul class="toc">
-<li class="frontmatter"><a href="#toc-h-1">Table of Contents</a></li>
-<li class="frontmatter"><a href="#preface-h-1">Preface</a></li>
-<li class="chapter"><a href="#html-h-1">The Web and HTML</a>
-  <ul>
-  <li class="section"><a href="#the-web">The Web</a>
-    <ul>
-    <li class="section"><a href="#development">Development of the Web</a></li>
-    <li class="section"><a href="#images">Adding images</a></li>
-    </ul>
-  </li>
-  </ul>
-</li>
-<li class="chapter"><a href="#css-h-1">CSS</a>
-  <ul>
-  <li class="section"><a href="#rules">Rules and Style Sheets</a></li>
-  </ul>
-</li>
-<li class="endmatter"><a href="#index-h-1">Index</a></li>
-</ul>
-</div>
-<div class="preface" id="preface-h-1">
-<h1>Preface</h1>
-<p>This is a sample document whose purpose is to show how CSS can be
-used to print a book. To make the document more lively, excerpts from
-the third edition of &#8220;Cascading Style Sheets &#8212; designing
-for tbe Web&#8221; have been included.<span class="footnote"> That
-book <em>was</em> produced using the methods described in the
-document, and it was published by Addison-Wesley in 2005.</span> The
-excerpts have been selected for their example values and they appear,
-in this document, out of order.</p>
-<p>The PDF version of this document is produced directly from the HTML
-and CSS sources by the Prince formatter.</p>
-<p>We encourage you to reuse the structure, markup and style sheet of
-this sample document. In your own book, however, you need to provide
-the content yourself.</p>
-<p class="author">H�kon Wium Lie &amp; Bert Bos<br>
-Oslo/Antibes<br>November 2005</p>
-</div>
-<div class="chapter" id="html-h-1">
-<h1 style="counter-reset: page 1">The Web and HTML</h1>
-<p class="sidenote">The box <a class="pageref" href="#specs">&#8220;CSS Specifications&#8221;</a> lists the different CSS specifications.</p>
-<p>Cascading Style Sheets (CSS) represent a major breakthrough in
-how Web-page designers work by expanding their ability to
-control the appearance of Web pages, which are the documents
-that people publish on the Web.</p>
-<p>For the first few years after the World Wide Web (the Web) was
-created in 1990, people who wanted to put pages on the Web had
-little control over what those pages looked like. In the
-beginning, authors could only specify structural aspects of
-their pages (for example, that some piece of text would be a
-heading or some other piece would be straight text). Also,
-there were ways to make text bold or italic, among a few other
-effects, but that's where their control ended.</p>
-<div class="section" id="the-web">
-<h2>The Web</h2>
-<p>The Web is a vast collection of documents on the <dfn id="dfn-internet">Internet</dfn> that are linked together via
-hyperlinks. The Internet consists of millions of computers worldwide
-that communicate electronically. A <dfn id="dfn-hyperlink">hyperlink</dfn> is a predefined link between two
-documents. The hyperlinks allow a user to access documents on various
-Web servers without concern for where they are located. A <dfn id="dfn-web-server">Web server</dfn> is a computer on the Internet
-that serves out Web pages on request. From a document on a Web server
-in California, the user is just one mouse click away from a document
-that is stored, perhaps, on a Web server in France. Hyperlinks are
-integral to the Web. Without them, there would be no Web.</p>
-<div class="section" id="development">
-<h3>Development of the Web</h3>
-<p>The Web was invented around 1990 by Tim Berners-Lee with
-Robert Cailliau as a close ally. Both of them were then
-working at <dfn id="dfn-cern">CERN</dfn>, which is the European Laboratory for Particle
-Physics. Tim is a graduate of Oxford University and a
-long-time computer and software expert, and is now the director
-of the <dfn id="dfn-w3c">World Wide Web Consortium (W3C)</dfn>, an organization that
-coordinates the development of the Web. He also is a
-principal research scientist at Massachusetts Institute of
-Technology's Laboratory for Computer Science and Artificial
-Intelligence (MIT CSAIL). Robert is a 30-year veteran at
-CERN, where he still works. Robert organized the
-first Web conference in Geneva in 1993. Both Tim and Robert
-were awarded the ACM Software System Award in 1995 because
-of their work on the Web.</p>
-</div>
-</div>
-<div class="section" id="images">
-<h3>Adding images</h3>
-<p>Images proliferate on the Web. It wasn't until the Mosaic browser
-added support for images in 1993 that a critical mass of people
-realized the potential of the Web. You can add images to your
-documents with the <span class="element">img</span> element &#8211;
-<span class="element">img</span> is short for image.</p>
-<p>When the image is ready, the page looks like <a class="figref" href="#fig-loaded">this figure</a>.</p>
-<div class="figure" id="fig-loaded">
-  <p class="caption">The image has been loaded.</p>
-  <p class="art"><img alt="[image]" src="images/html-18.png" style="width: 100%;"></p>
-</div>
-</div>
-</div>
-<div class="chapter" id="css-h-1">
-<h1>CSS</h1>
-<p class="sidenote">HTML is the most popular document format on the
-Web, and it is used in most of the examples in this book.</p>
-<p>As we explained in <a class="chapref" href="http://people.opera.com/howcome/2005/ala/html-h-1"><q>The Web and HTML,</q></a>
- HTML elements enable Web-page designers to
-mark up a document's structure. The HTML specification lists
-guidelines on how browsers should display these elements. For example,
-you can be reasonably sure that the contents of a <span class="element">strong</span> element will be displayed as boldfaced.
-Also, you can pretty much trust that most browsers will display the
-content of an <span class="element">h1</span> element using a big font
-size &#8211; at least bigger than the <span class="element">p</span>
-element and bigger than the <span class="element">h2</span> element.
-But beyond trust and hope, you don't have any control over your text's
-appearance.</p>
-<div class="sidebar" id="specs">
-<h2 class="no-toc">CSS specifications</h2>
-<p>Cascading Style Sheets is formally described in three W3C
-specifications: CSS1, CSS2, and CSS 2.1. (As discussed in the
-previous chapter, W3C is the organization that coordinates the
-technical development of the Web.) The first specification, CSS1,
-was issued in December 1996 and describes a simple style sheet
-language mostly for screen-based presentations. CSS1 has around 50
-properties (for example, <span class="property">color</span> and
-<span class="property">font-size</span>). CSS2 was finalized in May
-1998 and builds on CSS1. CSS2 includes all CSS1 properties and adds
-around 70 of its own, such as properties to describe aural
-presentations and page breaks.</p>
-<p>CSS 2.1 is the most recent specification published by W3C. It
-adds some new features, but CSS 2.1 is mostly a scaled-down version
-of CSS2. CSS2 was an ambitious attempt to describe functionality,
-which Web authors had requested. However, not all the functionality
-is reliably supported by all browsers. CSS 2.1 is a specification
-that describes the parts that <em>are</em> supported by two or
-more browsers. Because CSS 2.1 is similar to CSS2, the
-specification was given a minor version number (that is, 2.1)
-rather than a major number (such as CSS3).</p>
-</div>
-<div class="section" id="rules">
-<h2>Rules and Style Sheets</h2>
-<p>You can create style sheets in two ways. You can either use a
-normal text editor and write the style sheets <q>by hand</q> or you
-can use a dedicated tool &#8211; for example, a Web authoring tool.
-The dedicated tools enable you to create style sheets without learning
-the syntax of the CSS language. However, in many cases, the designer
-wants to tweak the style sheet by hand afterwards, so we recommend
-that you learn to write and edit CSS by hand. Let's get started! Here
-is a simple example:</p>
-<pre class="CSS">h1 { color: green }
-</pre>
-<p>This code is a simple CSS rule that contains one rule. A <dfn id="dfn-rule">rule</dfn> is a statement about one stylistic aspect of
-one or more elements. A <dfn id="dfn-style-sheet">style sheet</dfn> is
-a set of one or more rules that apply to an HTML document. This rule
-sets the color of all first-level headings (<span class="element">h1</span>).</p>
-<div class="table">
-<p class="caption">HTML extension elements and their CSS equivalent.</p>
-<table class="lined">
-  <thead>
-     <tr><th>Element</th><th>CSS equivalent</th></tr>
-  </thead>
-  <tbody>
-     <tr><td><code>&lt;tt&gt;</code></td>
-       <td><span class="css">font-family: monospace</span></td></tr>
-     <tr><td><code>&lt;i&gt;</code></td>
-       <td><span class="css">font-style: italic</span></td></tr>
-     <tr><td><code>&lt;b&gt;</code></td>
-       <td><span class="css">font-weight: bold</span></td></tr>
-     <tr><td><code>&lt;u&gt;</code></td>
-       <td><span class="css">text-decoration: underline</span></td></tr>
-  </tbody>
-</table>
-</div>
-</div>
-</div>
-<div class="index" id="index-h-1">
-<h1>Index</h1>
-<ul class="index">
-<li><a href="#dfn-cern">CERN</a></li>
-<li><a href="#dfn-internet">Internet</a></li>
-<li><a href="#dfn-hyperlink">hyperlink</a></li>
-<li><a href="#dfn-rule">rule</a></li>
-<li><a href="#dfn-style-sheet">style sheet</a></li>
-<li><a href="#dfn-w3c">W3C</a></li>
-<li><a href="#dfn-web-server">Web server</a></li>
-<li><a href="#dfn-w3c">World Wide Web Consortium</a></li>
-</ul>
-</div>
+<!-- Chapter 01 has the imports included inside of it -->
+<%= import('ch02/ch02.html.erb')%>
 </body></html>

data/lib/bookshop/generators/bookshop/app/templates/book/ch01/adding_images.html.erb ADDED Viewed

@@ -0,0 +1,15 @@
+<div class="section" id="images">
+<h3>Adding images</h3>
+<p>Images proliferate on the Web. It wasn't until the Mosaic browser
+added support for images in 1993 that a critical mass of people
+realized the potential of the Web. You can add images to your
+documents with the <span class="element">img</span> element &#8211;
+<span class="element">img</span> is short for image.</p>
+<p>When the image is ready, the page looks like <a class="figref" href="#fig-loaded">this figure</a>.</p>
+<div class="figure" id="fig-loaded">
+  <p class="caption">The image has been loaded.</p>
+  <p class="art"><img alt="[image]" src="images/html-18.png" style="width: 100%;"></p>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/ch01/ch01.html.erb ADDED Viewed

@@ -0,0 +1,26 @@
+<div class="chapter" id="html-h-1">
+<h1 style="counter-reset: page 1">The Web and HTML</h1>
+<p class="sidenote">The box <a class="pageref" href="#specs">&#8220;CSS Specifications&#8221;</a> lists the different CSS specifications.</p>
+<p>Cascading Style Sheets (CSS) represent a major breakthrough in
+how Web-page designers work by expanding their ability to
+control the appearance of Web pages, which are the documents
+that people publish on the Web.</p>
+<p>For the first few years after the World Wide Web (the Web) was
+created in 1990, people who wanted to put pages on the Web had
+little control over what those pages looked like. In the
+beginning, authors could only specify structural aspects of
+their pages (for example, that some piece of text would be a
+heading or some other piece would be straight text). Also,
+there were ways to make text bold or italic, among a few other
+effects, but that's where their control ended.</p>
+<%= import('ch01/the_web.html.erb')%>
+<%= import('ch01/dev_of_the_web.html.erb')%>
+<%= import('ch01/adding_images.html.erb')%>
+</div>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/ch01/dev_of_the_web.html.erb ADDED Viewed

@@ -0,0 +1,19 @@
+<div class="section" id="development">
+<h3>Development of the Web</h3>
+<p>The Web was invented around 1990 by Tim Berners-Lee with
+Robert Cailliau as a close ally. Both of them were then
+working at <dfn id="dfn-cern">CERN</dfn>, which is the European Laboratory for Particle
+Physics. Tim is a graduate of Oxford University and a
+long-time computer and software expert, and is now the director
+of the <dfn id="dfn-w3c">World Wide Web Consortium (W3C)</dfn>, an organization that
+coordinates the development of the Web. He also is a
+principal research scientist at Massachusetts Institute of
+Technology's Laboratory for Computer Science and Artificial
+Intelligence (MIT CSAIL). Robert is a 30-year veteran at
+CERN, where he still works. Robert organized the
+first Web conference in Geneva in 1993. Both Tim and Robert
+were awarded the ACM Software System Award in 1995 because
+of their work on the Web.</p>
+</div>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/ch01/the_web.html.erb ADDED Viewed

@@ -0,0 +1,12 @@
+<div class="section" id="the-web">
+<h2>The Web</h2>
+<p>The Web is a vast collection of documents on the <dfn id="dfn-internet">Internet</dfn> that are linked together via
+hyperlinks. The Internet consists of millions of computers worldwide
+that communicate electronically. A <dfn id="dfn-hyperlink">hyperlink</dfn> is a predefined link between two
+documents. The hyperlinks allow a user to access documents on various
+Web servers without concern for where they are located. A <dfn id="dfn-web-server">Web server</dfn> is a computer on the Internet
+that serves out Web pages on request. From a document on a Web server
+in California, the user is just one mouse click away from a document
+that is stored, perhaps, on a Web server in France. Hyperlinks are
+integral to the Web. Without them, there would be no Web.</p>

data/lib/bookshop/generators/bookshop/app/templates/book/ch02/ch02.html.erb ADDED Viewed

@@ -0,0 +1,63 @@
+<div class="chapter" id="css-h-1">
+<h1>CSS</h1>
+<p class="sidenote">HTML is the most popular document format on the
+Web, and it is used in most of the examples in this book.</p>
+<p>As we explained in <a class="chapref" href="http://people.opera.com/howcome/2005/ala/html-h-1"><q>The Web and HTML,</q></a>
+ HTML elements enable Web-page designers to
+mark up a document's structure. The HTML specification lists
+guidelines on how browsers should display these elements. For example,
+you can be reasonably sure that the contents of a <span class="element">strong</span> element will be displayed as boldfaced.
+Also, you can pretty much trust that most browsers will display the
+content of an <span class="element">h1</span> element using a big font
+size &#8211; at least bigger than the <span class="element">p</span>
+element and bigger than the <span class="element">h2</span> element.
+But beyond trust and hope, you don't have any control over your text's
+appearance.</p>
+<div class="sidebar" id="specs">
+<h2 class="no-toc">CSS specifications</h2>
+<p>Cascading Style Sheets is formally described in three W3C
+specifications: CSS1, CSS2, and CSS 2.1. (As discussed in the
+previous chapter, W3C is the organization that coordinates the
+technical development of the Web.) The first specification, CSS1,
+was issued in December 1996 and describes a simple style sheet
+language mostly for screen-based presentations. CSS1 has around 50
+properties (for example, <span class="property">color</span> and
+<span class="property">font-size</span>). CSS2 was finalized in May
+1998 and builds on CSS1. CSS2 includes all CSS1 properties and adds
+around 70 of its own, such as properties to describe aural
+presentations and page breaks.</p>
+<p>CSS 2.1 is the most recent specification published by W3C. It
+adds some new features, but CSS 2.1 is mostly a scaled-down version
+of CSS2. CSS2 was an ambitious attempt to describe functionality,
+which Web authors had requested. However, not all the functionality
+is reliably supported by all browsers. CSS 2.1 is a specification
+that describes the parts that <em>are</em> supported by two or
+more browsers. Because CSS 2.1 is similar to CSS2, the
+specification was given a minor version number (that is, 2.1)
+rather than a major number (such as CSS3).</p>
+</div>
+<%= import('ch02/rules_and_css.html.erb')%>
+</div>
+<div class="index" id="index-h-1">
+<h1>Index</h1>
+<ul class="index">
+<li><a href="#dfn-cern">CERN</a></li>
+<li><a href="#dfn-internet">Internet</a></li>
+<li><a href="#dfn-hyperlink">hyperlink</a></li>
+<li><a href="#dfn-rule">rule</a></li>
+<li><a href="#dfn-style-sheet">style sheet</a></li>
+<li><a href="#dfn-w3c">W3C</a></li>
+<li><a href="#dfn-web-server">Web server</a></li>
+<li><a href="#dfn-w3c">World Wide Web Consortium</a></li>
+</ul>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/ch02/rules_and_css.html.erb ADDED Viewed

@@ -0,0 +1,41 @@
+<div class="section" id="rules">
+<h2>Rules and Style Sheets</h2>
+<p>You can create style sheets in two ways. You can either use a
+normal text editor and write the style sheets <q>by hand</q> or you
+can use a dedicated tool &#8211; for example, a Web authoring tool.
+The dedicated tools enable you to create style sheets without learning
+the syntax of the CSS language. However, in many cases, the designer
+wants to tweak the style sheet by hand afterwards, so we recommend
+that you learn to write and edit CSS by hand. Let's get started! Here
+is a simple example:</p>
+<pre class="CSS">h1 { color: green }
+</pre>
+<p>This code is a simple CSS rule that contains one rule. A <dfn id="dfn-rule">rule</dfn> is a statement about one stylistic aspect of
+one or more elements. A <dfn id="dfn-style-sheet">style sheet</dfn> is
+a set of one or more rules that apply to an HTML document. This rule
+sets the color of all first-level headings (<span class="element">h1</span>).</p>
+<div class="table">
+<p class="caption">HTML extension elements and their CSS equivalent.</p>
+<table class="lined">
+  <thead>
+     <tr><th>Element</th><th>CSS equivalent</th></tr>
+  </thead>
+  <tbody>
+     <tr><td><code>&lt;tt&gt;</code></td>
+       <td><span class="css">font-family: monospace</span></td></tr>
+     <tr><td><code>&lt;i&gt;</code></td>
+       <td><span class="css">font-style: italic</span></td></tr>
+     <tr><td><code>&lt;b&gt;</code></td>
+       <td><span class="css">font-weight: bold</span></td></tr>
+     <tr><td><code>&lt;u&gt;</code></td>
+       <td><span class="css">text-decoration: underline</span></td></tr>
+  </tbody>
+</table>
+</div>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/cover.html.erb ADDED Viewed

@@ -0,0 +1,27 @@
+<div class="frontcover">
+<img src="images/canvas.jpg">
+<h1>Cascading Style Sheets</h1>
+<h2>Designing for the Web</h2>
+<h3>Third Edition</h3>
+<p>Sample document</p>
+</div>
+<div class="halftitlepage">
+<h1 class="no-toc">Cascading Style Sheets</h1>
+<h2 class="no-toc">Designing for the Web</h2>
+<h3 class="no-toc">Third Edition</h3>
+</div>
+<div class="titlepage">
+<h1 class="no-toc">Cascading Style Sheets</h1>
+<h2 class="no-toc">Designing for the Web</h2>
+<h3 class="no-toc">Third Edition</h3>
+<p class="no-toc">H&#229;kon Wium Lie<br>Bert Bos</p>
+<!-- also, the publisher's name would typically be printed here -->
+</div>
+<div class="imprint">
+<p>Copyright &copy; 2005 H&#229;kon Wium Lie and Bert Bos</p>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/preface.html.erb ADDED Viewed

@@ -0,0 +1,23 @@
+<div class="preface" id="preface-h-1">
+<h1>Preface</h1>
+<p>This is a sample document whose purpose is to show how CSS can be
+used to print a book. To make the document more lively, excerpts from
+the third edition of &#8220;Cascading Style Sheets &#8212; designing
+for tbe Web&#8221; have been included.<span class="footnote"> That
+book <em>was</em> produced using the methods described in the
+document, and it was published by Addison-Wesley in 2005.</span> The
+excerpts have been selected for their example values and they appear,
+in this document, out of order.</p>
+<p>The PDF version of this document is produced directly from the HTML
+and CSS sources by the Prince formatter.</p>
+<p>We encourage you to reuse the structure, markup and style sheet of
+this sample document. In your own book, however, you need to provide
+the content yourself.</p>
+<p class="author">H&#229;kon Wium Lie &amp; Bert Bos<br>
+Oslo/Antibes<br>November 2005</p>
+</div>

data/lib/bookshop/generators/bookshop/app/templates/book/toc.html.erb ADDED Viewed

@@ -0,0 +1,25 @@
+<div class="toc" id="toc-h-1">
+<h1>Table of Contents</h1>
+<ul class="toc">
+<li class="frontmatter"><a href="#toc-h-1">Table of Contents</a></li>
+<li class="frontmatter"><a href="#preface-h-1">Preface</a></li>
+<li class="chapter"><a href="#html-h-1">The Web and HTML</a>
+  <ul>
+  <li class="section"><a href="#the-web">The Web</a>
+    <ul>
+    <li class="section"><a href="#development">Development of the Web</a></li>
+    <li class="section"><a href="#images">Adding images</a></li>
+    </ul>
+  </li>
+  </ul>
+</li>
+<li class="chapter"><a href="#css-h-1">CSS</a>
+  <ul>
+  <li class="section"><a href="#rules">Rules and Style Sheets</a></li>
+  </ul>
+</li>
+<li class="endmatter"><a href="#index-h-1">Index</a></li>
+</ul>
+</div>

data/lib/bookshop/version.rb CHANGED Viewed

@@ -1,3 +1,3 @@
 module Bookshop
-  VERSION = "0.0.15"
+  VERSION = "0.0.16"
 end

metadata CHANGED Viewed

@@ -2,7 +2,7 @@
 name: bookshop
 version: !ruby/object:Gem::Version
   prerelease:
-  version: 0.0.15
+  version: 0.0.16
 platform: ruby
 authors:
 - D.a. Thompson
@@ -10,7 +10,7 @@ autorequire:
 bindir: bin
 cert_chain: []
-date: 2011-12-02 00:00:00 Z
+date: 2011-12-11 00:00:00 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -23,43 +23,32 @@ dependencies:
         version: 0.14.6
   type: :runtime
   version_requirements: *id001
-- !ruby/object:Gem::Dependency
-  name: nokogiri
-  prerelease: false
-  requirement: &id002 !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: "0"
-  type: :runtime
-  version_requirements: *id002
 - !ruby/object:Gem::Dependency
   name: bundler
   prerelease: false
-  requirement: &id003 !ruby/object:Gem::Requirement
+  requirement: &id002 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
         version: 1.0.0
   type: :development
-  version_requirements: *id003
+  version_requirements: *id002
 - !ruby/object:Gem::Dependency
   name: rspec
   prerelease: false
-  requirement: &id004 !ruby/object:Gem::Requirement
+  requirement: &id003 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
         version: "0"
   type: :development
-  version_requirements: *id004
+  version_requirements: *id003
 description: |-
-  bookShop is a publishing framework for html-to-(e)book toolchain happiness and sustainable productivity.
+  bookShop is a publishing framework for html-to-pdf/(e)book toolchain happiness and sustainable productivity.
                       The framework is optimized to help developers quickly ramp-up, allowing them to more rapidly
-                      jump in and develop their html-to-(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over
+                      jump in and develop their html-to-pdf/(e)book (print-pdf, epub, mobi, etc.) flows, by favoring convention over
                       configuration, setting them up with best practices, standards and tools from the start.
 email:
 - da@blueheadpublishing.com
@@ -87,9 +76,18 @@ files:
 - lib/bookshop/generators/bookshop/app/templates/CHANGELOG
 - lib/bookshop/generators/bookshop/app/templates/README.rdoc
 - lib/bookshop/generators/bookshop/app/templates/book/book.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/ch01/adding_images.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/ch01/ch01.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/ch01/dev_of_the_web.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/ch01/the_web.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/ch02/ch02.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/ch02/rules_and_css.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/cover.html.erb
 - lib/bookshop/generators/bookshop/app/templates/book/css/stylesheet.css
 - lib/bookshop/generators/bookshop/app/templates/book/images/canvas.jpg
 - lib/bookshop/generators/bookshop/app/templates/book/images/html-18.png
+- lib/bookshop/generators/bookshop/app/templates/book/preface.html.erb
+- lib/bookshop/generators/bookshop/app/templates/book/toc.html.erb
 - lib/bookshop/generators/bookshop/app/templates/builds/epub/.empty_directory
 - lib/bookshop/generators/bookshop/app/templates/builds/html/.empty_directory
 - lib/bookshop/generators/bookshop/app/templates/builds/mobi/.empty_directory
@@ -97,14 +95,6 @@ files:
 - lib/bookshop/generators/bookshop/app/templates/config/application.rb
 - lib/bookshop/generators/bookshop/app/templates/config/boot.rb
 - lib/bookshop/generators/bookshop/app/templates/script/bookshop
-- lib/bookshop/generators/bookshop/app/tools/COPYING.txt
-- lib/bookshop/generators/bookshop/app/tools/README.txt
-- lib/bookshop/generators/bookshop/app/tools/epubcheck-1.2.jar
-- lib/bookshop/generators/bookshop/app/tools/jigsaw_license.txt
-- lib/bookshop/generators/bookshop/app/tools/jing_license.txt
-- lib/bookshop/generators/bookshop/app/tools/kindlegen
-- lib/bookshop/generators/bookshop/app/tools/lib/jing.jar
-- lib/bookshop/generators/bookshop/app/tools/lib/saxon.jar
 - lib/bookshop/generators/bookshop/generator/USAGE
 - lib/bookshop/generators/bookshop/generator/generator_generator.rb
 - lib/bookshop/generators/bookshop/generator/templates/%file_name%_generator.rb.tt
@@ -140,6 +130,6 @@ rubyforge_project: bookshop
 rubygems_version: 1.8.5
 signing_key:
 specification_version: 3
-summary: A publishing framework for html-to-(e)book toolchain happiness and sustainable productivity.
+summary: A publishing framework for html-to-pdf/(e)book toolchain happiness and sustainable productivity.
 test_files: []

data/lib/bookshop/generators/bookshop/app/tools/COPYING.txt DELETED Viewed

@@ -1,19 +0,0 @@
-Copyright (c) 2007 Adobe Systems Incorporated
-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/lib/bookshop/generators/bookshop/app/tools/README.txt DELETED Viewed

@@ -1,61 +0,0 @@
-This folder contains the distribution of epubcheck project.
-EpubCheck is a tool to validate IDPF Epub files. It can detect many
-types of errors in Epub. OCF container structure, OPF and OPS mark-up,
-and internal reference consistency are checked. EpubCheck can be run
-as a standalone command-line tool, installed as a web application or
-used as a library.
-Epubcheck project home: http://code.google.com/p/epubcheck/
-BUILDING
-To build epubcheck from the sources you need Java Development Kit (JDK) 1.5 or above
-and Apache ant (http://ant.apache.org/) 1.6 or above installed
-Run
-ant -f build.xml
-RUNNING
-To run the tool you need Java Runtime (1.5 or above). Any OS should do. Run
-it from the command line:
-java -jar epubcheck-x.x.x.jar file.epub
-All detected errors are simply printed to stderr.
-USING AS A LIBRARY
-You can also use EpubCheck as a library in your Java application. EpubCheck
-public interfaces can be found in com.adobe.epubcheck.api package. EpubCheck
-class can be used to instantiate a validation engine. Use one of its
-constructors and then call validate() method. Report is an interface that
-you can implement to get a list of the errors and warnings reported by the
-validation engine (instead of the error list being printed out).
-LICENSING
-See COPYING.txt
-AUTHORS
-Peter Sorotokin
-Garth Conboy
-Markus Gylling
-Piotr Kula
-Most of the EpubCheck functionality comes from the schema validation tool Jing
-and schemas that were developed by IDPF and DAISY. EpubCheck development was
-largely done at Adobe Systems.

data/lib/bookshop/generators/bookshop/app/tools/epubcheck-1.2.jar DELETED Viewed

Binary file

data/lib/bookshop/generators/bookshop/app/tools/jigsaw_license.txt DELETED Viewed

@@ -1,66 +0,0 @@
-Jigsaw Copying Conditions
-W3C IPR SOFTWARE NOTICE
-Copyright � 1995-1998 World Wide Web Consortium, (Massachusetts Institute of
-Technology, Institut National de Recherche en Informatique et en
-Automatique, Keio University). All Rights Reserved.
-http://www.w3.org/Consortium/Legal/
-This W3C work (including software, documents, or other related items) is
-being provided by the copyright holders under the following license. By
-obtaining, using and/or copying this work, you (the licensee) agree that you
-have read, understood, and will comply with the following terms and
-conditions:
-Permission to use, copy, and modify this software and its documentation,
-with or without modification,  for any purpose and without fee or royalty is
-hereby granted, provided that you include the following on ALL copies of the
-software and documentation or portions thereof, including modifications,
-that you make:
-  1. The full text of this NOTICE in a location viewable to users of the
-     redistributed or derivative work.
-  2. Any pre-existing intellectual property disclaimers, notices, or terms
-     and conditions. If none exist, a short notice of the following form
-     (hypertext is preferred, text is permitted) should be used within the
-     body of any redistributed or derivative code: "Copyright � World Wide
-     Web Consortium, (Massachusetts Institute of Technology, Institut
-     National de Recherche en Informatique et en Automatique, Keio
-     University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"
-  3. Notice of any changes or modifications to the W3C files, including the
-     date changes were made. (We recommend you provide URIs to the location
-     from which the code is derived).
-In addition, creators of derivitive works must include the full text of this
-NOTICE in a location viewable to users of the derivitive work.
-THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS
-MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
-LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR
-PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE
-ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
-COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
-DOCUMENTATION.
-The name and trademarks of copyright holders may NOT be used in advertising
-or publicity pertaining to the software without specific, written prior
-permission. Title to copyright in this software and any associated
-documentation will at all times remain with copyright holders.
-____________________________________
-This formulation of W3C's notice and license became active on August 14
-1998. See the older formulation for the policy prior to this date. Please
-see our Copyright FAQ for common questions about using materials from our
-site, including specific terms and conditions for packages like libwww,
-Amaya, and Jigsaw. Other questions about this notice can be directed to
-site-policy@w3.org .
-webmaster
-(last updated 14-Aug-1998)

data/lib/bookshop/generators/bookshop/app/tools/jing_license.txt DELETED Viewed

@@ -1,12 +0,0 @@
-Jing Copying Conditions
-Copyright (c) 2001-2003 Thai Open Source Software Center Ltd
-All rights reserved.
-Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
-    * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-    * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
-    * Neither the name of the Thai Open Source Software Center Ltd nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/lib/bookshop/generators/bookshop/app/tools/kindlegen DELETED Viewed

Binary file

data/lib/bookshop/generators/bookshop/app/tools/lib/jing.jar DELETED Viewed

Binary file

data/lib/bookshop/generators/bookshop/app/tools/lib/saxon.jar DELETED Viewed

Binary file