newjs 1.0.2 → 1.0.3

data/History.txt

@@ -1,3 +1,10 @@
+== 1.0.3 2008-02-15
+
+* install_website:
+  * changed generated screen.css to be same as newjs's screen.css
+* website:
+  * Tutorial on releasing JavaScript library
+
 == 1.0.2 2008-02-15
 
 * newjs:

data/lib/newjs/version.rb

@@ -2,7 +2,7 @@ module Newjs #:nodoc:
   module VERSION #:nodoc:
     MAJOR = 1
     MINOR = 0
-    TINY  = 2
+    TINY  = 3
 
     STRING = [MAJOR, MINOR, TINY].join('.')
   end

data/newjs_theme_generators/plain_theme/templates/website/stylesheets/screen.css

@@ -1,5 +1,5 @@
 body {
-  background-color: #E1D1F1;
+  background-color: #8DBD82;
   font-family: "Georgia", sans-serif;
   font-size: 16px;
   line-height: 1.6em;
@@ -24,7 +24,7 @@ li {
 }
 a {
   color: #5E5AFF;
-	background-color: #DAC;
+	background-color: #A1DDB1;
   font-weight: normal;
   text-decoration: underline;
 }
@@ -39,7 +39,7 @@ blockquote {
 }
 
 #main {
-  width: 45em;
+  width: 50em;
   padding: 0;
   margin: 0 auto;
 }
@@ -101,12 +101,12 @@ pre, code {
   text-align: right;
   font-family: sans-serif;
   font-weight: normal;
-  background-color: #B3ABFF;
+  background-color: #9A5535;
   color: #141331;
   padding: 15px 20px 10px 20px;
   margin: 0 auto;
 	margin-top: 15px;
-  border: 3px solid #141331;
+  border: 3px solid #7E393E;
 }
 
 #version .numbers {
@@ -119,16 +119,16 @@ pre, code {
 
 #version p {
   text-decoration: none;
-	color: #141331;
-	background-color: #B3ABFF;
+	color: #F1F4FF;
+	background-color: #9A5535;
 	margin: 0;
 	padding: 0;
 }
 
 #version a {
   text-decoration: none;
-	color: #141331;
-	background-color: #B3ABFF;
+	color: #F1F4FF;
+	background-color: #9A5535;
 }
 
 .clickable {

data/website/index.html

@@ -33,7 +33,7 @@
     <h1>JavaScript Project Generator</h1>
     <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/newjs"; return false'>
       <p>Get Version</p>
-      <a href="http://rubyforge.org/projects/newjs" class="numbers">1.0.2</a>
+      <a href="http://rubyforge.org/projects/newjs" class="numbers">1.0.3</a>
     </div>
     <h1>&#x2192; &#8216;newjs&#8217;</h1>
 
@@ -197,6 +197,68 @@ in your required order.</p>
 
 <pre>rake dist</pre>
 
+	<p>Two files are added into the <code>dist/</code> folder:</p>
+
+
+<pre>$ ls dist/
+drnic_js_test_helpers-0.5.0.js  drnic_js_test_helpers.js</pre>
+
+	<p>One with a version number, and one without.</p>
+
+
+	<h3>Upload library to rubyforge</h3>
+
+
+	<p>Assuming you don&#8217;t really care where your package/library is uploaded
+and made available for downloading, <code>newjs</code> projects comes
+pre-built ready to upload them to <code>rubyforge</code>.</p>
+
+
+	<p>First, you&#8217;ll need a rubyforge account.</p>
+
+
+	<p>Second, create a rubyforge project. It can take 12-48hrs for confirmation
+to come back.</p>
+
+
+	<p>Third, use the <code>rubyforge</code> command-line app to 
+store your rubyforge project information locally.</p>
+
+
+<pre>$ rubyforge setup  # first time only
+$ rubyforge login
+$ rubyforge config
+$ rubyforge create_package project_name project_name
+</pre>
+
+	<p>Note, if you are placing your JavaScript project within an existing
+rubyforge project, then the two <code>project_name</code> values
+are different:</p>
+
+
+	<ol>
+	<li>The rubyforge project name (e.g. drnicutilities) </li>
+		<li>The JavaScript project/library name (e.g. drnic_js_test_helpers)</li>
+	</ol>
+
+
+	<p>Finally, each time you want to release a new version of your library you do 
+two things:</p>
+
+
+	<ol>
+	<li>Update Rakefile&#8217;s <code>APP_VERSION</code> value to the new version number</li>
+		<li>Run <code>rake release VERSION=X.Y.Z</code></li>
+	</ol>
+
+
+	<p>Your files are now available for download via rubyforge.org.</p>
+
+
+	<p>If you use the generated website (below), it comes with a link to these
+files when you click the large version number (e.g. &#8220;Get Version X.Y.Z&#8221;).</p>
+
+
 	<h2>Create a website for your project</h2>
 
 

data/website/index.txt

@@ -132,6 +132,51 @@ Finally, run the command:
 
 <pre>rake dist</pre>
 
+Two files are added into the <code>dist/</code> folder:
+
+<pre>$ ls dist/
+drnic_js_test_helpers-0.5.0.js  drnic_js_test_helpers.js</pre>
+
+One with a version number, and one without.
+
+h3. Upload library to rubyforge
+
+Assuming you don't really care where your package/library is uploaded
+and made available for downloading, <code>newjs</code> projects comes
+pre-built ready to upload them to <code>rubyforge</code>.
+
+First, you'll need a rubyforge account.
+
+Second, create a rubyforge project. It can take 12-48hrs for confirmation
+to come back.
+
+Third, use the <code>rubyforge</code> command-line app to 
+store your rubyforge project information locally.
+
+<pre>$ rubyforge setup  # first time only
+$ rubyforge login
+$ rubyforge config
+$ rubyforge create_package project_name project_name
+</pre>
+
+Note, if you are placing your JavaScript project within an existing
+rubyforge project, then the two <code>project_name</code> values
+are different:
+
+# The rubyforge project name (e.g. drnicutilities) 
+# The JavaScript project/library name (e.g. drnic_js_test_helpers)
+
+Finally, each time you want to release a new version of your library you do 
+two things:
+
+# Update Rakefile's <code>APP_VERSION</code> value to the new version number
+# Run <code>rake release VERSION=X.Y.Z</code>
+
+Your files are now available for download via rubyforge.org. 
+
+If you use the generated website (below), it comes with a link to these
+files when you click the large version number (e.g. "Get Version X.Y.Z").
+
 h2. Create a website for your project
 
 You can quickly create a clean, readable website for your project

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: newjs
 version: !ruby/object:Gem::Version 
-  version: 1.0.2
+  version: 1.0.3
 platform: ruby
 authors: 
 - Dr Nic Williams