[Jifty-commit] jifty branch, master, updated. 837788395ad25574ab070a50e51bd2dee82594c6

[Jifty commits]

The branch, master has been updated
       via  837788395ad25574ab070a50e51bd2dee82594c6 (commit)
      from  685bd60952a19614b19ee02bc23c7783ff67594a (commit)

Summary of changes:
 lib/Jifty/Manual/jQueryMigrationGuide.pod |   62 ++++++++++++++--------------
 1 files changed, 31 insertions(+), 31 deletions(-)

- Log -----------------------------------------------------------------
commit 837788395ad25574ab070a50e51bd2dee82594c6
Author: Shawn M Moore <sartak at bestpractical.com>
Date:   Fri Apr 30 22:09:55 2010 +0800

    English fixes for jQueryMigrationGuide

diff --git a/lib/Jifty/Manual/jQueryMigrationGuide.pod b/lib/Jifty/Manual/jQueryMigrationGuide.pod
index 5bd9941..19ec12f 100644
--- a/lib/Jifty/Manual/jQueryMigrationGuide.pod
+++ b/lib/Jifty/Manual/jQueryMigrationGuide.pod
@@ -5,32 +5,32 @@ jQueryMigrationGuide - How to migrate your code to use jQuery.
 =head1 Migrate your jifty app to jquery
 
 Application developers may start the migration by modifying
-F<config.yml>, set the C<ConfigFileVersion> to 4. If you did not write
-any custom javascript code for your app, then its done. Everything
+F<config.yml>, setting the C<ConfigFileVersion> to 4. If you did not write
+any custom javascript code for your app, then you're done. Everything
 should just work.
 
-If you did wrote some javascript code before, but you did not use any
-of those funcitons defined in F<jifty*.js>, F<prototype.js> or
+If you did write some javascript code, but you did not use any
+of the functions defined in F<jifty*.js>, F<prototype.js> or
 F<scriptaculous.js>, then you're still good to go.
 
 Otherwise, your code might need to be modified a little bit. Since
 both F<prototype.js> and F<scriptaculous.js> are removed by default,
 one trivial choice is to simply bring them back. That is as easy as
-adding a B<Prototypism> plugin to your Jifty application.
+adding the B<Prototypism> plugin to your Jifty application.
 
-If you dislike the whole Prototypism like us, you can choose to
+If you dislike Prototypism like we do, you can choose to
 re-write your code with jQuery. In the section L</"From Prototype
-to jQuery"> below, we provide some known pattern that can be applied to
-rewrite prototypism code with jQuery, or with just normal javascript.
+to jQuery"> below, we provide some common patterns that can be applied to
+rewrite Prototypism code with jQuery, or with just normal javascript.
 
-If you hack Jifty internal, please make sure you've read the following
+If you hack on Jifty's internals, please make sure you've read the following
 L</"Jifty API"> section and L<Jifty::Manual::JavaScript> to catch the
-Javascript API update since the removal of C<prototype.js>.
+Javascript API updates since the removal of C<prototype.js>.
 
 Although we've removed C<prototype.js>, we still prefer to use
-non-conflict mode of jQuery at this moment. That is, C<$> function is
-now undefined, but not an alias of jQuery. This is to ensure that it's
-not conflicting with Prototypism at all conditions. If you'd like
+the non-conflict mode of jQuery. That is, C<$> function is
+now undefined instead of an alias to jQuery. This is to ensure that it's
+not conflicting with Prototypism anywhere. If you'd like
 to use C<$> function, create that alias in your C<app.js> like this:
 
     $ = jQuery;
@@ -46,25 +46,25 @@ localize this alias within a closure:
 
 =head1 Jifty API
 
-Jifty javascript libraries embraced a major re-architect after jQuery
-landed. Especially those internal functions to process form elements.
+We re-architechted Jifty's javascript libraries to use jQuery. Especially
+the internal functions to process form elements.
 
-The Prototype-based old way is to extend Form object and the
-Form.Element object. Since the removal of Prototype library, it is
-dangerous to name those functions under Form. Because loading
-Prototype library can destroy those Jifty functions.
+The old, Prototype-based way is to extend Form object and the
+Form.Element object. Since the removal of the Prototype library, it is
+dangerous to name those functions under Form because loading
+the Prototype library can destroy those Jifty functions.
 
-The new jQuery-fashioned way is to always extend internal functions
-under Jifty object. C<Form> becomes C<Jifty.Form>, C<Form.Element> becomes
-C<Jifty.Form.Element> and so on. The detail list of these defined
+The new jQuery-based way is to always extend internal functions
+under the Jifty object. C<Form> becomes C<Jifty.Form>, C<Form.Element> becomes
+C<Jifty.Form.Element>, and so on. The detailed list of these
 functions are given in L<Jifty::Manual::Javascript>. Most of
 those functions are internal functions that you probably should not
-use them directly.
+use directly.
 
 =head1 From Prototype to jQuery
 
-If you've ever written javascript code on your Jifty applications, and
-you'd like to remove PrototypeJS library, here are some dummy rules to
+If you've ever written javascript code for your Jifty applications, and
+you'd like to remove the PrototypeJS library, here are some mechanical rules to
 re-write prototypejs-based javascript code with jQuery.
 
 =head3 Array iteration
@@ -113,9 +113,9 @@ To:
 
 =head2 JSON
 
-jQuery does not build-in with JSON stringify function, but since it
+jQuery does not ship with the JSON stringify function, but since it
 neither altered the native Array, nor defined its own Hash, it's
-prefered and fine to just use C<JSON.stringify> from C<json.js>.
+acceptable and preferred to just use C<JSON.stringify> from C<json.js>.
 
 From:
 
@@ -128,9 +128,9 @@ To:
 
 =head2 Effects
 
-jQuery has a small set of default effects built-in to its core. They
-have different naming then those defined in C<scriptaculous.js>. The
-internal way to do effect is via the C<Jifty.Effect> method. Please
-see the detail usage in L<Jifty::Manual::JavaScript>.
+jQuery has a small set of default effects built into its core. They
+have different names then those defined in C<scriptaculous.js>. The
+internal way to specify effects is using the C<Jifty.Effect> method. Please
+see the detailed usage documentation in L<Jifty::Manual::JavaScript>.
 
 =cut

-----------------------------------------------------------------------