rails textile_toolbar_demo && cd textile_toolbar_demo
　
ruby script/plugin install git://github.com/pelargir/textile_toolbar.git
rake textile_toolbar:install 
　
ruby script/generate scaffold post title:string body:text published:boolean
　
vi app/views/posts/edit.html.erb
    <%#= f.text_area :body %>
    <%= f.textile_area :body, :rows => 5, :cols => 20 %>
　
vi app/views/layouts/posts.html.erb 
  <%= stylesheet_link_tag 'scaffold' %>
  <%= javascript_include_tag :defaults %>
  <%= javascript_include_tag "textile_toolbar.js" %>
　
rake db:migrate && rake db:fixtures:load
　
ruby script/server
　
# http://localhost:3000/posts/<post.id>/edit

• 参考资料
  
  • 插件textile_toolbar首页
  • Announcing the textile_toolbar Plugin

(1..5).each do |i|
  puts i
end

5.downto(1) do |i|
  puts i
end

• 说明
  
  • 在下面资料的逆向循环语句中，do前面多了一个点。

• 参考资料
  
  • http://www.railsrocket.com/articles/looping-backwards-in-ruby

• 说明
  
  • Cucumber是跨计算机语言的代码测试工具
  • Cucumber是使用本地化语言的代码测试工具
  • Cucumber是集成多种测试工具于一体的工具
  • Cucumber彻底分离测试描述（文字工作者）与描述实现（软件工作者）
  • Cucumber更加人性化，更加语言化，更加简单化

• 参考资料
  
  • 代码测试工具Cucumber首页
  • Cucumber: Next Generation Ruby BDD tool
  • Cucumber: 黄瓜将成为下一代的Ruby BDD工具
  • Ruby on Rails（Cucumber Wiki）
  • Cucumber（黄瓜）

• Cucumber（中文语言描述）基础讲座系列（即将推出）
  
  • Cucumber on Rails基本使用过程
  • Cucumber基本概念
  • Cucumber on Rails最简单实例
  • Cucumber on Rails深化实例

• 国际化功能问与答（一）：国际化文件
  
  • 默认国际化文件在哪里？
    $RAILS_ROOT/config/locales
  • 使用什么样语言写国际化文件？
    YAML语言
    或者
    Ruby语言
  • 通常中国大陆中文使用什么国际化文件名称？
    zh-CN.yml
    或者
    zh-CN.rb
  • 默认国际化文件是定义了什么文字语言？
    English
  • 国际化文件最大特点是什么？
    以命名空间为基础结构
  • 一个国际化文件是否可以存在几种语言或者方言（zh-CN,zh-HK,zh-TW）呢？
    可以
  • 一种语言或者一种方言的国际化内容是否可以存放到几个国际化文件呢？
    可以
  • 一个国际化文件名称是否与文件内容相关呢？
    无关

MountainWest RubyConf, among the most super cool awesome Ruby gatherings around, is looking for sponsors for the 2009 event in Salt Lake City, UT.

You can read the prospectus here. (PDF)

If you or your company is looking to support the Ruby community, and get some solid advertising in front of some of the best geeks in the world, this is for you.

If you know someone or some company who would be interested in sponsoring the conference, please pass this information on.

• 重要参考资料
  
  • Rails 2.2: i18n, HTTP validators, thread safety, JRuby/1.9 compatibility, docs
  • Ruby on Rails 2.2 Release Notes
  • Rails 2.2已经正式发布！
  • What’s New in Edge Rails: Rails 2.2 Released – Summary of Features 4
  • Demo application to show Rails’ new i18n features
  • Rails 2.2 For Me And For You
  • Rails 2.2 Released – 27 Links and Resources To Get You Going

• Rails 2.2版本不再推荐使用的功能
  
  • List of Countries
  • Deprecation
  • Rails 2.2 Deprecations

• 专题资料
  
  • Memo-what? – A Guide to Memoization
  • Rails Roundup: Rails 2.2 Will Be Threadsafe, ETags Support in Rails Edge
  • Demo of Rails 2.2 internationalization
  • Things Caches Do
  • http://rails-i18n.org/
  • The Ruby on Rails I18n core api

• 参考资料
  
  • Rails 2.2 Released: A Glance at New Features

• 安装说明
  
  • 下载: http://fit.coollittlethings.com/down.php?v=1.9.3_intel
  • 解压文件即双击该文件: FunInputToy_v1.9.3_intel.zip
  • 双击文件: FunInputToy_v1.9.3_intel.pkg
  • 自动重新启动计算机
  • 系统偏好设置 >> 多语言环境 >> 输入法菜单 >> 如上图所示

• 参考资料
  
  • FIT发布实验版 http://fit.coollittlethings.com/?p=112
  • 下载首页 http://fit.coollittlethings.com/?p=3

• 致谢
  
  • 非常感谢 kyle 所提供的信息.

Fifty People, One Question: New York

“ Autumn, the year’s last, loveliest smile. ”

William Cullen Bryant

Tree on Fire by Axel

I Still Care For You

Ray LaMontagne

• 什么是消息队列（Messaging Queue）
  
  • http://en.wikipedia.org/wiki/Message_Queue
  • http://www.cnblogs.com/rickie/archive/2004/11/16/64345.aspx

• 有哪些队列服务器（Queue Server）软件
  
  • Beanstalkd
  • Starling
  • Peafowl

• 同步与异步概念
  
  • HTTP是同步的，Queue是异步的，但是目的是一样的
  • http://en.wikipedia.org/wiki/Message_Queue

• 服务器与客户端概念
  
  • 在HTTP概念中，存在浏览器（Client）与网络服务器（Server）；
  • 在Queue概念中，也存在客户端软件与服务器软件概念；

• 如何在Ruby和Rails中使用基于Beanstalk的消息队列（Messaging Queue）
  
  • Beanstalk Messaging Queue http://tinyurl.com/24zfv7
  • Ruby Beanstalkd distributed worker basics http://tinyurl.com/5nehld
  • Ruby Beanstalkd distributed worker intermediate lessons http://tinyurl.com/6hz6p3
  • http://async-observer.rubyforge.org/

• 参考资料
  
  • https://computing.llnl.gov/tutorials/parallel_comp/

• Joe Mocker's Weblog

There’s a nice write-up about recent events at Ruby Manor that describes a talk involving Monkeybars.

I want add a few comments. First, while it is true that using JRuby means some gems do not work, the upside is that you have at your disposal the hojillion¹ Java libraries. While it is a goal that all Ruby code, gem or not, work with JRuby (with some caveats about native code), the ability to call into Java libs is a major win. The post mentions that a particualr gem for using Twitter could not be used; I’m fairly sure this is the exact situation Logan Barnett encountered when he started on Twit-and-Twitter for the Java One Script Bowl.

Logan was able to use a Java lib for Twitter, one that (as I recall) offered a more robust API. Big win. So, not to diminish the problem JRuby may have with certain gems, but there are two ways of looking at this: Some gems don’t run (glass 99/100 empty), vs. full use of Java libs (glass overflowing onto the floor and out the door).

Second, Monkeybars was compared (so to speak) with Shoes. No mention was made of Shoes having stability issues (something I’ve seen for myself), but even were it rock-solid there is no way one would want to build a serious app of any complexity. (To fair, I don’t think Shoes was created for that purpose, though some enthusiasts mistake the ease of use as demonstrated in demo apps as something that scales to commercial-grade desktop applications. If and when there is a WYSIWYG editor for Shoes that might change.) I’m deeply skeptical that, for example, JotBot could have been made in Shoes, if only because of the lack of sophisticated components.

However, for those who really REALLY want to build GUI apps that way, good news: Work is afoot to add this to Monkeybars. We hope before too long to allow Monkeybars to offer the best of both worlds.

¹ This is a really big number. Really. Big.

• 安装说明
  
  • 点击链接： http://tinyurl.com/6g8nd9
  • 把下载的文件NetNewsWire.app移到应用软件目录下
  • 点击该文件NetNewsWire.app，就可以启动该软件
  • 注册一下用户
  • 在所有的Mac OS X机器上，只要有该软件并且有相同的用户，相互间就可以同步本地RSS信息。

Rails 2.2 is finally done after we cleared the last issues from the release candidate program. This release contains an long list of fixes, improvements, and additions that’ll make everything Rails smoother and better, but we also have a number of star player features to parade this time.

Internationalization by default
The most important is that Rails now includes a full-on internationalization framework and that it’s pre-wired from start. The work of the i18n group has been very impressive and it’s great to see that Rails finally ships with a solution in the box that’s both simple and extensible. Great job, guys!

Stronger etag and last-modified support
We’ve also added much better support for HTTP validators in the form of etag and last-modified. Making it so much easier to skip expensive procesesing if the client already has the latest stuff. This also makes it even easier to use Rails with gateway proxies.

Thread safety and a connection pool
Josh Peek has added thread safety to Rails and Nick Sieger from JRuby worked on getting Active Record a proper connection pool. So now all elements of Rails are thread safe, which is a big boon for the JRuby guys in particular. For C Ruby, we still need a bunch of dependent libraries to go non-blocking before it’ll make much of a difference, but work on that is forth coming.

Ruby 1.9 and JRuby compatibility
Jeremy Kemper has been rocking on both Ruby 1.9 and JRuby compatibility. Rails 2.2 is fully compatible with both, but again, there might be supporting libraries and gems that are not. Again, lots of work is going into making everything else fully compatible as well.

Better API docs, great guides
Finally, the last big push has been with the documentation of Rails. Pratik’s docrails project has made immense progress. Not only are the API docs much improved, but we also have a whole new guides section generated from documentation that now lives with the source. A true community project with lots of contributors. I’m sure both those new and old to Rails will greatly appreciate the strong focus on documentation.

To read about all these features and more in details, checkout the Rails 2.2 release notes—another one of those guides from the docrails project.

How to install
As always, you can install Rails 2.2 through RubyGems. We now require RubyGems 1.3.1, so be sure to update that first: gem update --system

Then you can install Rails: gem install rails

If you’re updating an existing application, you can run rake rails:update to get the latest JavaScript files and scripts.

From all of us to all of you, we hope you enjoy this release. It’s a true pleasure to see Rails make such big steps forward once again. Dig in, have fun, and we’ll be back with Rails 2.3 with even more before you know it.

• 相关链接
  
  • Ruby和Rails应用软件有多少？ http://www.railsforall.org/apps
  • Ruby和Rails资料有多少？ http://www.railsforall.org/resources

First up this week, a warning for those who don’t closely follow the state of the Rails repository – “edge” really means edge now. The bits for 2.2 are getting locked down for release, and the repository has been forked; for the moment, edge Rails is being identified as 2.3 , though that projected version number might change later. If you’re trying to install almost-released 2.2 bits on your machine, make sure you’re using the 2-2-stable branch, and not edge, which is currently seeing some major changes.

The 2-2-stable code is still seeing changes, but they’re either bug fixes or very small things. This week, that includes fixing a bug in assignment to has_one :through associations , some further tuning of CSRF protection , a fix to handling of checkboxes for Boolean attributes , updating the bundled copies of TZInfo, Prototype, and script.aculo.us, and some Ruby 1.9 compatibility work (though currently full Ruby 1.9 compatibility is targeted for Rails 2.3).

The biggest feature change in the 2.2 branch is the addition of explicit I18n support to newly-generated Rails projects, including a sample locale file, auto-loading all locales in config/locales, and sample settings in config/environment.rb. commit

Also worth noting in 2.2 is a chunk of code removal: a whole mess of special case tests for the SQL Server adapter have been chopped out of the Active Record test cases. That’s because Ken Collins has done tremendous work in making the SQL Server adapter work the way that Rails expects data adapters to work, giving us a big step in the area of backend portability. commit

On the actual edge code (the master branch in the repository), there’s a lot more action. With that branch just opened, some pent-up code has been checked in, and some big changes are being made. It’s an exciting time, and edge is definitely worth checking out. Here are some of the most notable changes in the past week.

One big set of changes has come from Jeremy Kemper, who has been overhauling the internal Rails testing to switch from Test::Unit::TestCase to ActiveSupport::TestCase. This work also includes requiring Mocha to test Rails (in the 2.2 code, some tests are skipped if you don’t have Mocha installed) and generally making the Rails testing strategy (both within core and for generated applications) more consistent moving forward.

If you’re one of the people who has always been bothered by the special-case naming of application.rb, rejoice! It’s been reworked to be application_controller.rb in the edge code. More info here and here . commit

Rails 2.3 will introduce the notion of default scopes : similar to named scopes, but applying to all named scopes or find methods within the class. For example, you can write default_scope :order => 'name ASC' and any time you retrieve records from that class they’ll come out sorted by name (unless you override the option, of course). commit

A lot of folks have adopted the notion of using try() to attempt operations on objects – Here’s Chris Wanstrath’s blog post introducing it. It’s especially helpful in views where you can avoid nil-checking by writing code like <%= @person.try(:name) %>. Well, now it’s baked right into Rails. commit

Also new on the syntactic sugar front is Enumerable#none? to check that none of the elements match the supplied block. commit

The render method has been getting smarter over the years, and it’s going to be even smarter in 2.3. If you have an object or a collection and the naming matches up, you can now just do <% render @article %> or <% render @articles %> and things will just work. Ryan Daigle has some more examples on this. commit

On a somewhat similar note, render_component goes from “deprecated” to “nonexistent” in 2.3. If you still need it, you can install the plugin . commit

The autolink helper has been refactored to make it a bit less messy and more intuitive. commit commit

There’s a fix to a memory leak connected to thread safety and asset tags, that could bite sites that were referencing a lot of external images. Aaron Batalion contributed the fix, as well as a blog post explaining the issue. commit and commit

Finally, it’s worth mentioning that some controversy has erupted over a change made to the 2.2 code five months ago – the addition of Array#second through Array#tenth as aliases for Array#[1] through Array#[9]. Without taking a stand on the controversy (I’ve done that elsewhere), I’ll just note that the most recent edge checkin as I write this trims this down to only support Array#second through Array#fifth – and uses the savings in overhead to implement Array#forty-two. commit

With king of the hill Rails chugging along, and up-and-comer Merb picking up steam, why bother with Ramaze?

The number one thing that makes Ramaze stand out from the crowd is that you write very little code and you write it all yourself. No generators.

...

Before Rails, people wrote lots and lots of code when making a web app, and they did it over and over as they did web app after web app. With each new app, they would spend time “ramping up” with just the base application before they got into the real meat of the matter, the core functionality which varied from client to client, application to application. Rails and Merb and their ilk try to make your life easier by generating this “lots and lots of code” for you, so you don’t have to spend time repeating the motions of getting the skeleton of your application coded.

Ramaze takes a different approach. It asks: How about we dump the “lots and lots of code” part altogether? This way, you get the benefit of nearly nil ramp up time, without the gaping jaw effect that hits you after you run a code generator script and sit staring at the big filetree that just sprouted out of the ground (think Jack and the Beanstalk).

Ramaze by Example