whowish_word 0.3.1 → 0.3.2

data/.gitignore

@@ -1,6 +1,6 @@
-
-/Gemfile.lock
-spec/rails/tmp/*
-*.gem
-rails/db/*.sqlite3
+
+/Gemfile.lock
+spec/rails/tmp/*
+*.gem
+rails/db/*.sqlite3
 rails/tmp/*

data/.loadpath

@@ -1,5 +1,5 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<loadpath>
-	<pathentry path="" type="src"/>
-	<pathentry path="org.rubypeople.rdt.launching.RUBY_CONTAINER" type="con"/>
-</loadpath>
+<?xml version="1.0" encoding="UTF-8"?>
+<loadpath>
+	<pathentry path="" type="src"/>
+	<pathentry path="org.rubypeople.rdt.launching.RUBY_CONTAINER" type="con"/>
+</loadpath>

data/.project

@@ -1,17 +1,18 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>whowish_word</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.rubypeople.rdt.core.rubybuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.rubypeople.rdt.core.rubynature</nature>
-	</natures>
-</projectDescription>
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>whowish_word</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.rubypeople.rdt.core.rubybuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>com.aptana.ruby.core.rubynature</nature>
+		<nature>org.rubypeople.rdt.core.rubynature</nature>
+	</natures>
+</projectDescription>

data/Gemfile

@@ -1,3 +1,3 @@
-source 'http://rubygems.org'
-
+source 'http://rubygems.org'
+
 gem 'rspec'

data/HOW_TO_BUILD_WHOWISH_HOOK.md

@@ -1,10 +1,10 @@
-Process to discover where to put the hook
---------------------------------------------
-
-In a view, please a try-catch block and print all traces.
-
-Do this in:
-1. layout
-2. normal view
-3. partial
+Process to discover where to put the hook
+--------------------------------------------
+
+In a view, please a try-catch block and print all traces.
+
+Do this in:
+1. layout
+2. normal view
+3. partial
 4. nested layout

data/ISSUE.md

@@ -1,93 +1,93 @@
-Current issues
-==================
-
-
-
-Support different database engine 
--------------------------------------------------
-
-It is painful to use WhowishWord on different database (MySQL, PostgreSQL, MongoDB, Redis, ...).
-
-Here is a cycle for a database
-
-- Initialize structure
-- Save migration version
-- Rails uses it
-- Do another migration
-- Save the new version 
-
-There must be a better way that:
-- lets user configure easily
-- does not depend on 3rd library (No ORM. Really? Should we do that?)
-	- ActiveRecord is ok
-	- Mongoid is not, because it is not a standard
-- 
-
-### Solution
-
-Just Support them directly...
-
-
-### (Not good) Solution
-
-Use SQLite instead.
-However, this poses another problem. SQLite cannot be run on Cloud service, e.g. Heroku.
-
-
-
-
-
-A way to activate edit mode (Solved!)
--------------------------------------------------
-
-It should be activate-able inside Rails application, e.g. a call to WhowishWord.activate_edit_mode.
-We let user manage its own session.
-
-The thing to look out is that we have to be careful about using a global variable within WhowishWord gem
-because it is shared among users....
-
-### Solution
-
-Create a single point of activating an edit mode, WhowishWord.activate_edit_mode()
-
-
-
-Javascript text issue (Solved!)
-----------------------
-
-Javascript text being enclosed with single-quotes causes an error 
-(Even if we'd change to double-quotes enclosing, there would still be a problem)
-
-
-### Solution 1
-
-User is responsible to make sure that all quotes are escaped.
-
-Input text attributes (Solved!)
-----------------------
-
-In edit mode, we cannot add edit icon next to the element, which owns the attribute.
-
-### Solution
-
-Use javascript to add the edit icon.
-
-1. Generate a unique text in the attribute
-2. Get the element by searching for the unique text
-3. Replace text with a whowish word
-4. Add edit icon to the element
-
-When getting an element, we have to store the element and the attribute's name in a hash for future use.
-This is because the element might not have its own ID.
-
-
-Select box options (Solved!)
----------------------
-
-In edit mode, we cannot edit whowish word in option's value and option's text
-
-### Solution
-
-Use javascript to generate edit icon
-
-
+Current issues
+==================
+
+
+
+Support different database engine 
+-------------------------------------------------
+
+It is painful to use WhowishWord on different database (MySQL, PostgreSQL, MongoDB, Redis, ...).
+
+Here is a cycle for a database
+
+- Initialize structure
+- Save migration version
+- Rails uses it
+- Do another migration
+- Save the new version 
+
+There must be a better way that:
+- lets user configure easily
+- does not depend on 3rd library (No ORM. Really? Should we do that?)
+	- ActiveRecord is ok
+	- Mongoid is not, because it is not a standard
+- 
+
+### Solution
+
+Just Support them directly...
+
+
+### (Not good) Solution
+
+Use SQLite instead.
+However, this poses another problem. SQLite cannot be run on Cloud service, e.g. Heroku.
+
+
+
+
+
+A way to activate edit mode (Solved!)
+-------------------------------------------------
+
+It should be activate-able inside Rails application, e.g. a call to WhowishWord.activate_edit_mode.
+We let user manage its own session.
+
+The thing to look out is that we have to be careful about using a global variable within WhowishWord gem
+because it is shared among users....
+
+### Solution
+
+Create a single point of activating an edit mode, WhowishWord.activate_edit_mode()
+
+
+
+Javascript text issue (Solved!)
+----------------------
+
+Javascript text being enclosed with single-quotes causes an error 
+(Even if we'd change to double-quotes enclosing, there would still be a problem)
+
+
+### Solution 1
+
+User is responsible to make sure that all quotes are escaped.
+
+Input text attributes (Solved!)
+----------------------
+
+In edit mode, we cannot add edit icon next to the element, which owns the attribute.
+
+### Solution
+
+Use javascript to add the edit icon.
+
+1. Generate a unique text in the attribute
+2. Get the element by searching for the unique text
+3. Replace text with a whowish word
+4. Add edit icon to the element
+
+When getting an element, we have to store the element and the attribute's name in a hash for future use.
+This is because the element might not have its own ID.
+
+
+Select box options (Solved!)
+---------------------
+
+In edit mode, we cannot edit whowish word in option's value and option's text
+
+### Solution
+
+Use javascript to generate edit icon
+
+