Luca Guidi

Click to Globalize is ready for Rails 2.1!

I spent a lot of time to make this release the best of ever! I know that a lot of time has passed since the latest Rails major release, and I apologize for this.
The official Globalize it seems dead, but the great work of Nate Clark (aka heythisisnate) has made it compatible with Rails 2.1. Thanks Nate!
The Rails Edge now includes a basic support for i18n!

What's Changed?

The first big change is about the configuration, past versions has cluttered a bit your ApplicationController, I know, but now Click uses a YAML file configuration file for locales.

As you can see, it's more readable than put an Hash inside your main controller, and it also take the advantage to separate configuration from logic.

The second change regards the default language, you can use the above file to declare it, or use the Globalize syntax (Globalize::Locale.set_base_language('en-US')), but you have to choose a locale before the app starts.
This because Click needs a secure fallback mechanism, if no active Locale was set, it's always guarantees your application to work.

The third feature is about formatting: you can always choose between textile and markdown without editing ApplicationController, but using the same configuration file.

I removed the deprecated class method ApplicationController#globalize? in favor of the instance one. This means you can use it to turn on/off Click to Globalize, just returning a boolean value:

This version also includes tiny fixes, refactoring and cleanup.

You may wish to learn a bit about Click to Globalize, so I encourage you to visit the official page.
I hope you enjoy your i18n on Rails!

Click to Globalize has been rewritten, in order to use all instance methods of the JavaScript class, instead of class methods.

I also fixed some tiny issues:

• The form_authentication_token method is called only if the application is protected against the CSRF attacks (protect_against_forgery? returns true)
• It uses as parameter key what request_forgery_protection_token returns, instead of the hard-coded authenticity_token
• The JavaScript class uses Prototype's dom:loaded custom event.

I also migrated the plugin GitHub. The new repo is http://github.com/jodosha/click-to-globalize/tree/master, so the oldest one is deprecated.
Have a nice globalization!

If you enjoyed this post, feel free to recommend me on Working With Rails.

Click to Globalize

Click to Globalize is an extension for Globalize plugin, it allows to edit in place globalized labels. With this plugin you don't have to create a globalization back-end, but just edit your interface in place!!

If you have a previous globalization experience, you probably noticed that the main problem of dedicated back-ends is the lack of the context where the string will be placed in. It isn't a trivial issue: you'll never know if the meaning of your string is harmonious with other labels and how your string will be rendered, until the page load.

Now you can forget this issues, you can directly globalize in place!!

Getting Started

1. Install Globalize 1, if you don't already done.
2. Install Click to Globalize:
   
3. Run the setup task:
   
4. Edit config/click.yml
5. Add at the end of your layout the following code:
   
6. Put in your view:
   
7. Start the server and click to globalize.

Prerequisites

• Globalize 1 plugin: www.globalize-rails.org.
• Prototype >= 1.5.1.1, this version was bundled in the outdated versions.
• RedCloth gem (optional) for textile formatting.
• BlueCloth gem (optional) for markdown formatting.

Install

NOTE the following instructions are for Click to Globalize v0.4.0 (Rails 2.1.x), for older version, please check your README.

1. Install Globalize 1, if you don't already done.
2. Install Click to Globalize:
   Rails 2.1.x Rails 2.0.x Rails 1.2.x
3. Run the setup task:
   
4. Run the tests (optional):
   
5. Edit config/click.yml, adding your locales (including the default one), and, optionally, the formatting style:

NOTE: Make sure to choose a default locale before the app starts.
6. Personalize the access to the globalization features, overriding #globalize:
   
   NOTE: #globalize? is method to turn on/off all the Click to Globalize features.
7. Add at the end of your layout the following code:
   

Uninstall

Features

• In-place editing for each globalized string.
• Easy and painless plug-in/plug-out process.
• Unobtrusive Javascript.
• Auto transformation from input text to textarea for long strings.

Common Issues

• The install process (for Rails 1.2.x) upgrades your Prototype version to 1.5.1.1 only if needed, but it's advisable to backup your scripts.
• Due to unobtrusive nature of the plugin, each page is parsed by javascript to find the right element and bind to it an Ajax.InPlaceEditor.
  Be sure your (X)HTML is wellformed.
  NOTICE: If you use the Rails 1.2.x scaffold system, Click to Globalize doesn't works. Cleanup the code before to use.
• If you use a wiki-formatting style it could be advisable to use #h to avoid security problems (i.e. XSS).
  
• The official Globalize repository is still not compatible with Rails 2.1, use the heythisisnate's fork instead.

Contribute

• Check out the code and test it:
  
• Create tickets at the Sushistar Lighthouse Page.
• Create a patches and add as attachement to the tickets.

Repository

http://github.com/jodosha/click-to-globalize/tree/master

Credits

Javascript tests are based on Prototype test libs.

Vote

If you find it useful feel free to add to your favs on agilewebdevelopment.com.

Copyright

Copyright © 2007 - 2008 http://lucaguidi.com, released under the MIT license.

Tutorials

• Getting Started --high resolution
  
• Getting Started
  
• Restrict The Access
  
• Text Area Transformation
  
• Formatting
  
• How to Prevent XSS