Skip to content
Browse files

Merge pull request #363 from kytrinyx/more-js-references

Fix references to EventManager and Blogger
  • Loading branch information...
2 parents d41a25c + abdfd97 commit d218699f72f392a4c9b9a73020f81346cd5a0ce9 @steveklabnik steveklabnik committed
View
0 source/assets/jsblogger/screen.css → source/assets/blogger/screen.css
File renamed without changes.
View
4 source/paths/codemash_2012.markdown
@@ -5,9 +5,9 @@ title: CodeMash 2012 Resources
Here's all the content Jeff presented at CodeMash 2012:
-* (Precompiler: Fundamental Ruby on Rails)[/paths/codemash_rails.html] - Based on our JSBlogger Tutorial, a gentle introduction to Rails (4 Hours)
+* (Precompiler: Fundamental Ruby on Rails)[/paths/codemash_rails.html] - Based on our Blogger Tutorial, a gentle introduction to Rails (4 Hours)
* (Precompiler: Advanced Rails Patterns)[/paths/codemash_patterns.html] - Four patterns for use in Rails applications: decorators, facades, modules, and slim controllers (4 Hours)
* (Conference Session: Metrics-Powered Rails Performance)[/paths/codemash_performance_metrics.html] - An introduction to performance metrics for CPU, Memory, and Databases (1 Hour)
* (Lightning Talk: The World is Full of Real People)[http://jumpstartlab.com/news/archives/2012/01/13/the-world-is-full-of-real-people/] - Thoughts on our responsibility to the world (5 Minutes)
-All the tutorials are open source and on Github. Your thoughts and contributions are greatly appreciated!
+All the tutorials are open source and on Github. Your thoughts and contributions are greatly appreciated!
View
4 source/paths/codemash_rails.markdown
@@ -37,10 +37,10 @@ You need:
We're going to follow the first parts of a long tutorial available here:
-http://tutorials.jumpstartlab.com/projects/jsblogger.html
+http://tutorials.jumpstartlab.com/projects/blogger.html
## Contributing
You're strongly invited to help improve these tutorials, even while we're running the session. All the text is available on Github, so you can edit it right in the browser. Hit the "Feedback" tab on the left side of any page.
-Enjoy!
+Enjoy!
View
4 source/paths/performance_metrics.markdown
@@ -9,7 +9,7 @@ http://speakerdeck.com/u/j3/p/metrics-driven-rails-performance
The sample project is available here:
-https://github.com/jumpstartlab/jsblogger_advanced
+https://github.com/jumpstartlab/blogger_advanced
To get it ready after cloning:
@@ -26,4 +26,4 @@ Aman Gupta has an interesting presentation about Debugging Ruby up here:
http://speakerdeck.com/u/tmm1/p/debugging-ruby-performance
-It's a great jumping-off point if you want to dive into the depths of deep debugging/performance.
+It's a great jumping-off point if you want to dive into the depths of deep debugging/performance.
View
4 source/paths/ruby_one_day.markdown
@@ -37,11 +37,11 @@ We'll start with the fundamentals of Ruby and Object Oriented Programming:
http://tutorials.jumpstartlab.com/projects/ruby_in_100_minutes.html
-### JSAttend
+### EventManager
Then, to put those techniques into practice, let's begin [the EventMangager project]({% page_url /projects/eventmanager %}).
-We anticipate only working through a few iterations of JSAttend in the session, but please continue working on your own!
+We anticipate only working through a few iterations of EventManager in the session, but please continue working on your own!
## Contributing
View
4 source/paths/ruby_rails_quickstart.markdown
@@ -7,7 +7,7 @@ title: Ruby/Rails QuickStart - 5 Day
* Ruby Syntax Review
* Understanding Ruby Style
-* Writing Pure Ruby with JSAttend
+* Writing Pure Ruby with EventManager
* Common Ruby Patterns
### Day 2
@@ -21,7 +21,7 @@ title: Ruby/Rails QuickStart - 5 Day
* Rails MVC Implementation
* Understanding Rails Components
-* "Error-Driven Development" with JSBlogger
+* "Error-Driven Development" with Blogger
* Basic Relationship Patterns
### Day 4
View
2 source/projects/blogger.markdown
@@ -465,7 +465,7 @@ Refresh your browser and your article should show up along with a link back to t
This is not a CSS project, so to make it a bit more fun we've prepared a CSS file you can drop in. It should match up with all the example HTML in the tutorial.
-Download the file from http://tutorials.jumpstartlab.com/assets/jsblogger/screen.css and place it in your `app/assets/stylesheets/` folder. It will be automatically picked up by your project.
+Download the file from http://tutorials.jumpstartlab.com/assets/blogger/screen.css and place it in your `app/assets/stylesheets/` folder. It will be automatically picked up by your project.
## I1: Form-based Workflow
View
2 source/projects/jstwitter.markdown
@@ -435,7 +435,7 @@ wonderwillow said...
Getting each friend's last message was cool, but they're in some random order. Sort them by the `screen_name` in alphabetical order! I want you to hack out the code, but the way I did it would read like this:
-"take the friends list and use the `sort_by` method, then call each one `friend` and find the `friend.screen_name`". You might look at how you used `sort_by` in JSAttend for syntax clues. (NOTE: Ruby considers all capital letters to come earlier in alphabetical order than lowercase letters. To keep all your letters together regardless of capitalization, change `friend.screen_name` to `friend.screen_name.downcase` when sorting)
+"take the friends list and use the `sort_by` method, then call each one `friend` and find the `friend.screen_name`". You might look at how you used `sort_by` in EventManager for syntax clues. (NOTE: Ruby considers all capital letters to come earlier in alphabetical order than lowercase letters. To keep all your letters together regardless of capitalization, change `friend.screen_name` to `friend.screen_name.downcase` when sorting)
Second, these messages are lacking any time context. The `status` hash has a key named `created_at` which holds a string like this one: `Thu Jul 23 23:31:16 +0000 2009`. That's the information we need, but it's in an ugly format. Use these steps to make the data more useable:
View
2 source/topics/better_views/view_partials.markdown
@@ -11,7 +11,7 @@ When writing Ruby we break up complex methods into multiple, smaller methods. Wh
{% include custom/sample_project_advanced.html %}
<pre class="note">
- <p>Apologies that the text below refers to a HAML version of JSBlogger. If you haven't completed the "ERB and HAML" tutorial/exercises, your project will still have ERB.</p>
+ <p>Apologies that the text below refers to a HAML version of Blogger. If you haven't completed the "ERB and HAML" tutorial/exercises, your project will still have ERB.</p>
<p>The concepts below will still apply, but you'll need to "port" the examples from HAML to ERB.</p>
</pre>
View
4 source/topics/controllers/flash.markdown
@@ -159,10 +159,10 @@ The condition is no longer necessary because if there aren't keys in the flash,
{% include custom/sample_project.html %}
-The JSBlogger project already uses flash messages, but we can try a few experiments with `ArticlesController`:
+The Blogger project already uses flash messages, but we can try a few experiments with `ArticlesController`:
1. Refactor `update`, `destroy`, and `create` to set the `:notice` message in the `redirect_to`
2. Add a message under the `:validation` key when an article fails to validate, then display this key in a dedicated paragraph within the form partial.
3. Refactor the flash display in the application layout to iterate through all keys.
* CHALLENGE: make it so the `:validation` key is skipped in the top display, allowing it to only show up in the form.
-4. Move the body of your flash messages into the `en.yml` locale file and load them using the `t` helper
+4. Move the body of your flash messages into the `en.yml` locale file and load them using the `t` helper
View
2 source/topics/controllers/parameters.markdown
@@ -199,7 +199,7 @@ This isn't about writing less code, it's about writing code in the right place.
{% include custom/sample_project.html %}
-1. Open the `ArticlesController` in JSBlogger and find the `create` action. As an experiment, rewrite it setting each form value individually rather than using mass-assignment.
+1. Open the `ArticlesController` in Blogger and find the `create` action. As an experiment, rewrite it setting each form value individually rather than using mass-assignment.
2. In the `index` action, implement handling for an `order_by` parameter as modeled in the text. Add an option to sort by `"word_count"`
3. Add links to the index page which, when clicked, change the sorting to `"title"`, `"word count"`, or `"published"`. *CHALLENGE*: Add links and handling so each of these can be _inverted_.
4. In the `index` action of `ArticlesController`, handle a parameter named `"limit"` which will limit how many articles are displayed. If there is no `"limit"`, display all the articles.
View
6 source/topics/debugging/outputting_text.markdown
@@ -233,11 +233,11 @@ For more extensive discussion, check out the Heroku resource center here: http:/
## Exercises
-Grab the JSBlogger sample project, create a branch, and try out each of the following techniques:
+Grab the Blogger sample project, create a branch, and try out each of the following techniques:
```
-git clone https://github.com/JumpstartLab/jsblogger
-cd jsblogger
+git clone https://github.com/JumpstartLab/blogger
+cd blogger
git checkout -b my_debugging
bundle
```
View
4 source/topics/internal_testing/factories.markdown
@@ -9,7 +9,7 @@ In the beginning there were fixtures. We'd write huge YAML files containing samp
They worked great, until the object structure changed. When you decide that your article now needs a `"published_on"` timestamp, you'd go through all your fixtures and manually add the given YAML attribute to each entry in the fixtures file. Boring!
<div class='note'>
-<p>During this tutorial section, have a copy of the JSBlogger sample project open. You'll be able to install the library, create factories, and experiment with them.</p>
+<p>During this tutorial section, have a copy of the Blogger sample project open. You'll be able to install the library, create factories, and experiment with them.</p>
</div>
## Factories
@@ -210,4 +210,4 @@ That's everything you need to know to create flexible, easy sample data with Fab
2. Write a fabricator for `Comment` that just generates the `Comment` object. Use appropriate generators from `Faker`
3. Use inheritance to extend that pattern to create a `Comment` with a parent `Article`
4. From your console, use the override style to create a comment with the body `"Hello, World!"`
-5. Flip the `Article` patterns so `Fabricate(:article)` gives you an article with comments, and `Fabricate(:article_without_comments)` gives an `Article` with no comments
+5. Flip the `Article` patterns so `Fabricate(:article)` gives you an article with comments, and `Fabricate(:article_without_comments)` gives an `Article` with no comments
View
2 source/topics/javascript/jquery.markdown
@@ -120,7 +120,7 @@ What's `.coffee`? Next we will take a look at CoffeeScript.
{% include custom/sample_project.html %}
-1. Add the `jquery-rails` gem to JSBlogger and use the generator to setup the library.
+1. Add the `jquery-rails` gem to Blogger and use the generator to setup the library.
2. Create a file named `interface.js` in the `javascripts` directory.
3. Load that file by adding it to the include in the application layout. Verify it is in the head by looking at the page source.
4. Remove it from the application layout, and instead add it to the `:defaults` in the configuration. Note that you'll need to restart the server for it to take effect. Verify the script appears in the head of a page's source.
View
2 source/topics/models/polymorphism.markdown
@@ -115,7 +115,7 @@ Now the `.phone_numbers` method returns an array. You can just think of it as a
{% include custom/sample_project.html %}
-In the JSBlogger sample application, you already have `Article` and `Comment` classes. As it stands, a `Comment` belongs to an `Article`.
+In the Blogger sample application, you already have `Article` and `Comment` classes. As it stands, a `Comment` belongs to an `Article`.
Now we decide that we want to implement comment threads, so that a `Comment` can belong to *either* an `Article` or another `Comment`.
View
10 source/topics/sample_project.markdown
@@ -1,17 +1,17 @@
---
layout: page
-title: Sample Project - JSBlogger
+title: Sample Project - Blogger
---
-For these tutorials we've built a very simple three-model sample project named JSBlogger. You can use it to complete all the exercises and experiments described.
+For these tutorials we've built a very simple three-model sample project named Blogger. You can use it to complete all the exercises and experiments described.
## Check Out the Code
From your terminal, change to a directory where you want to store your project. Then, checkout the code from GitHub:
```
-git clone http://github.com/JumpstartLab/jsblogger.git
-cd jsblogger
+git clone http://github.com/JumpstartLab/blogger.git
+cd blogger
```
<div class="note">
@@ -36,7 +36,7 @@ git update-index --assume-unchanged db/development.sqlite3
## Use Pattern
-Unless otherwise specified, the exercises for a single section are designed to be completed independently of the other sections. You should always start with this original copy of JSBlogger.
+Unless otherwise specified, the exercises for a single section are designed to be completed independently of the other sections. You should always start with this original copy of Blogger.
### Starting a Branch

0 comments on commit d218699

Please sign in to comment.
Something went wrong with that request. Please try again.