• 英文说明
  
  • CCleaner is a freeware system optimization, privacy and cleaning tool.

• 中文说明
  
  • 一款免费的系统优化工具；
  • 清除系统的不使用和临时文件；
  • 使得系统运行更快；

cd ~
　
mkdir bin
　
ln -s /Applications/TextMate.app/Contents/Resources/mate ~/bin/mate
　
vim .bash_profile
export PATH="$HOME/bin:$PATH" 
　
source .bash_profile
　
mate .

• 参考资料
  
  • TextMate shell utility

• The Grid System
• Design By Grid | Home
• WordPress › Lightweight « WordPress Themes
• 960 Grid System
• Fast Workouts That Really Work! on Yahoo! Health

I forked the Monkeybars repo so I could safely experiment with some things. My repo is monkeybars-with-inline-ruby-swing and that’s pretty much it in a nutshell.

Often, when people talk about Monkeybars, they compare it to some other similar tool that uses inline code (often using a “builder”-style syntax) to define the UI. The typical Monkeybars demo, in contrast, shows the use of WYSIWYG UI editor to create a binary Java Swing class; this file is then used in the Monkeybars app.

Not surprisingly, showing how this is done can take some time, even for a basic Hello, World! demo app. The sad truth of conference talks and demos is that you can get screwed from both ends in trying to properly explain anything non-trivial. You want to point out the details (because your tool is powerful), but that eats up the limited time available. You also want to actually show something, ideally something complete, so you end up with something simplistic.

If done well, then everyone gets the point: robust, sophisticated tool presented in overly-simplistic app for demonstration purposes. However, you can often end up with people seeing it the other way: lots of detailed steps needed to get to skimpy results. What’s then not grasped (or not well explained) is that the details are there to convey the breadth of possibilities; the skimpy app is there to simply demonstrate that this is something real. You still have to apply some imagination to understand the implications for larger, far more complex applications by extrapolation.

Demos using hand-written code to define a GUI have a real edge here because the speaker never has to leave the code editor, never has to switch views or tools, never has to explain much more than “here’s some more Ruby.” What’s often not mentioned, though, is that the inline-style of GUI definition does not scale well beyond the typical demo program. What you see really is what your get. (Trust me; I would not want to have to work on JotBot hand-coding the UI.)

Of course, maybe you don’t want much more than a handful of buttons and some text fields. Maybe all you want is the desktop equivalent of HTML 3.2.

Sometimes that’s all I need for given screen in some larger app, and having Monkeybars provide this would make it that much sweeter. Best would be that it would not alter how one uses the full power of the library.

So here’s what my fork of Monkeybars adds:

• Some code to the base View class to aid in detecting when the Swing UI class is in fact created via Ruby, so that the appropriate reflection/meta-programming can be done
• An additional app generator that gives you an MVC tuple, with a basic view UI class, written in Ruby, in place.

Because I’m interested in getting people to play with this, I renamed the key files from monkeybars to jimpanzee. Now if you install the code as a gem you won’t stomp on any existing Monkeybars installation. (The code should be completely compatible with the current actual Monkeybars API, but the renaming is cleaner.)

With jimpanzee, you can do this:

james@james06:~/tmp$ jimpanzee MyCoolApp :demo
Creating directory MyCoolApp
Copying jimpanzee project structure
Creating  default code for MyCoolApp ...

Final steps:

  1. Place a copy of jruby-complete.jar in the MyCoolApp/lib/java directory
  2. cd into the MyCoolApp/src directory
  3. Run the code using jruby:

       jruby main.rb

Happy hacking!

and if you follow those final instructions you’ll have a simple cross-platform GUI app running. Toss in rawr and you’re three steps away from having redistributable executables ready.

You can see it here (except for the Rawr part):

There’s more to be done, not the least of which is ensuring that my approach is robust. The generator needs improvement; it’s pretty brain-dead. (For example, :demo is a hard-coded flag for the generator code, and you can’t tell it what to name the generated tuple. But these are not difficult things to change. The real issue is what to change them to.)

There’s a certain “gee whiz” factor in this, because there’s a low limit on what such generators can buy you, and how much inline UI code you’ll want, but the flip side is that it does lower the barrier to entry, and it is of practical value when coupled with Monkeybars’ other killer features. The best part is that it is in addition to, not in place of, all the power the best GUI toolkit offers for creating robust GUI apps of all shapes and sizes.

Please keep in mind when you see any demo that looks a bit too good or too easy that maybe the cool comes with a cost. The most common is that what makes some things easy ends up making other things hard. Always try to ask the presenter what the limits are, if a tool will grow with you if the size your application expands, or if will you find yourself stuck once the gee whiz has worn off.

Whatever tools you pick, consider the long view.

I Changed My Mind

Lyrics Born

Automatic Mahjong Table

“ There is no win and no fail. There is only make. ”

Sister Corita Kent

Erst mal paar Nachträge zur Adventskalenderliste letzte Woche:

• Ruby Advent 2008 hat “Ruby Cool-aid for Holiday Season”.

• Advent Beer Calendar 2008, ein Blog über alkoholhaltige Biermischgetränke.

Wer noch Geschenke sucht:

• Krippe für Puristen

• Legend of Zelda — Mosaic Artwork

• Bad Gift Emporium, “We have lots of BAD gifts. Really BAD gifts.”

I remember Leslie Harpold.

NP: Brazilian Girls—Internacional

• :: PLUS ::

• GCDrawKit - A complete framework for vector drawing
• split-s: Replacing methods
• The Omni Mouth » Helpify, the Omni Help Emitter
• Peachpit: Building a WordPress Blog People Want to Read - $29.99

Phusion is on a roll today. Not only did we just get a new Passenger, they’ve also just dropped a new REE (the Ruby patches for copy-on-write) that includes 64-bit support as well as compatibility with OS X and Solaris. They’ve also fitted the excellent RailsBench patches from Stefan Kaes that allows you to tweak the GC settings in Ruby if you need to.

This edition was sponsored by 37signals, Curve21, Dr Dispatch Transportation Software, InfoEther, Martian Interactive, New York Times, Shopify, Trevor Turk, and Utah Imaging.

November 29-December 5, 2008 Edition

Rails 2.3 development is still continuing at a healthy clip. Here’s an overview of what’s happened this week.

Application Templates

Rails now incorporates Jeremy McAnally’s rg application generator. What this means is that we now have template-based application generation built right into Rails; if you have a set of plugins you include in every application (among many other use cases), you can just set up a template once and use it over and over again when you run the rails command. Pratik Naik provided a thorough writeup of this feature over on his blog. commit

Find Improvements

Even the venerable code used by Active Record to talk to databases can be improved, and we had a couple of improvements checked in this week. First, the SQL generated for preloading records in has_and_belongs_to_many associations has had an extra “AS” excised, which makes it work better with some databases. Also, we now have a :having option on find (as well as on has_many and has_and_belongs_to_many associations) for filtering records in grouped finds. As those with heavy SQL backgrounds know, this allows filtering based on grouped results:

developers =  Developer.find(:all, :group => "salary", 
  :having => "sum(salary) >  10000", :select => "salary")

commit commit

Rack Integration

The tighter integration of Rails with Rack continues. This week saw the death of the venerable CGI processor within Rails, as well as the use of Rack to handle FCGI. There was also some refactoring down in the Rails tests to make them play nicer with Rack. commit commit

Configuration File Cleanup

Over the years, the default environment.rb file had gotten a bit cluttered with comments, random documentation, and settings that mot people don’t need. DHH took a few minutes to clean up the mess, and the current state of this file is much leaner. As part of the cleanup, session store configuration has been moved out to its own file. commit

No More Process Scripts

If you’re one of the (fairly rare) Rails developers who deploys in a fashion that depends on the inspector, reaper, and spawner scripts, you’ll need to know that those scripts are no longer included in core Rails. For Rails applications that are reployed with current alternatives like Passenger, these are just unnecessary baggage. But if you need them, you’ll be able to pick up copies via the irs_process_scripts plugin. commit

Odds and Ends

The fact that Rails checks for IP spoofing can be a nuisance for sites that do heavy traffic with cell phones, because their proxies don’t generally set things up right. If that’s you, you can now set ActionController::Base.ip_spoofing_check = false to disable the check entirely. commit

Rails.root now returns a Pathname object, which means you can use it directly with the join method to clean up existing code that uses File.join. commit

ActionController::Dispatcher now implements its own middleware stack, which you can see by running rake middleware. commit

Gem loading is smarter about missing dependencies. commit

auto_link now properly applies options (such as :target and :class) to generated e-mail links. commit

The Phusion team keeps blazing ahead with Passenger and improving it rapidly. They’ve just released version 2.0.5, which includes a few fixes and introduces compatibility with the Rack-based Edge Rails.

At 37signals, we’ve already switched over Ta-da List and are busy working on getting the rest of our suite running on Passenger. It’s just so much easier to deal with and the memory savings you get through REE are a nice cherry on top.

I keep getting a steady stream of success reports from all over the world as well. I’ve even read of a few people getting back into Rails development because Passenger finally took out the inconvenience of deploying.

It’s hard to argue with the usability. I’ve personally been setting up a new server running Ubuntu 8.10 and using Apache 2 with Passenger. The time it took me to go from a fresh install to a complete production setup was ridiculously low. There’s just so much less to worry about.

If you haven’t given Passenger a chance yet, now is definitely the time.

警告：在复制本博客代码时，空行存在中文空格，需要删除！！！

rails 04_demo_cucumber && cd 04_demo_cucumber
　
ruby script/generate cucumber
　
vi features/support/env.rb
require 'cucumber/rails/rspec'
require 'webrat' if !defined?(Webrat)
　
vi lib/tasks/cucumber.rake
# 在format和language之前是两个“-”，其它地方也是如此。
Cucumber::Rake::Task.new(:features) do |t|
  t.cucumber_opts = "—format pretty —language zh-CN" 
　
rake db:migrate
　
rake features
　
ruby script/generate rspec_scaffold post title:string body:text
　
ruby script/generate feature post title:string body:text
　
vi features/step_definitions/webrat_steps.rb
#require 'webrat' if !defined?(Webrat) # Because ...
　
rake db:migrate
　
vi features/manage_posts.feature
功能:管理帖子
  为了能够控制“帖子MVC”
  作为软件普通用户
  我要完成“帖子MCV”创建和删除帖子的功能
　
  场景: 创建一个新的帖子
    假如 我已经在创建新帖子页面
    当 我在输入框<post_title>中输入内容<lycom.de是什么网站>
    而且 我在输入框<post_body>中输入内容<lycom.de是一个Ruby/Rails技术新闻博客>
    而且 我点击按钮<Create>
    那么 我应该看到<lycom.de是什么网站>
    而且 我应该看到<lycom.de是一个Ruby/Rails技术新闻博客>
　
  场景: 删除第一个帖子
    假如 存在<4>个帖子
    当 我删除第一个帖子
    那么 还应该有<3>个帖子
　
vi features/step_definitions/post_steps.rb
require 'spec'
$:.unshift(File.dirname(__FILE__) + '/../../lib')
　
Given /我已经在创建新帖子页面/ do
  visits "/posts/new" 
end
　
When /我点击按钮<(.*)>/ do |btn_name|
  clicks_button btn_name
end
　
Given /存在<(\d+)>个帖子/ do |n|
  Post.transaction do
    Post.destroy_all
    n.to_i.times do |n|
      Post.create! :title => "Post #{n}" 
    end
  end
end
　
When /我在输入框<(.*)>中输入内容<(.*)>/ do |id,text|
  fills_in(id, :with => text)
end
　
When /我删除第一个帖子/ do
#  @post = Post.find(:first)
#  visits "/posts/#{@post.id}" 
  visits posts_url
  clicks_link "Destroy" 
end
　
Then /^我应该看到<(.*)>/ do |text|
  #response.body.should =~ /#{text}/
  response.body.should =~ Regexp.new(text)
end
　
Then /还应该有<(\d+)>个帖子/ do |n|
  Post.count.should == n.to_i
  response.should have_tag("table tr", n.to_i + 1) # There is a header row too
end
　
# 这个命令输出结果就是上面图
rake features　
或者
ruby script/cucumber -a zh-CN features/manage_posts.feature

• 说明
  
  • 通用即时通讯工具Adiumx解决了MSN账号在Apple上的即时通讯问题。
  • 另一款通用即时通讯工具Pidgin

• 说明
  
  • RJS教程是使用早期的Rails版本为基础的
  • RJS中文教程不是完整的翻译版本
  • 谁来着手以Rails 2.2版本重新写该教程的命令？

• 相关链接
  
  • RJS教程中文版本
  • RJS教程英文版本