whowish_word 0.1.0 → 0.1.1

Sign up to get free protection for your applications and to get access to all the features.
data/README.md CHANGED
@@ -1,4 +1,4 @@
1
- WhowishWord
1
+ WhowishWord (This is a draft)
2
2
  ====================
3
3
 
4
4
  Have you ever been bored when a project manager (or marketing department) keeps changing wording on a website?
@@ -9,10 +9,11 @@ WhowishWord facilitates the process of changing wording on a website.
9
9
  How you should work
10
10
  -------------------
11
11
 
12
- 1. Activate edit mode through http://your_domain/whowish_word
12
+ 1. Activate edit mode by calling activate_whowish_word_edit_mode() in any controller
13
13
  2. Go back to the website, you'll see an edit icon on each word
14
14
  3. Click on an edit icon to edit the corresponding word
15
15
  4. Fill in a new word, and click save
16
+ 4.1 If it is the first time, you will need to fill master password at this point. (The instruction how to set password is below)
16
17
 
17
18
  And when you have finished, deactivate edit mode.
18
19
 
@@ -23,9 +24,9 @@ This take the burden off programmers because it is extremely boring to change wo
23
24
  Prerequisite
24
25
  -------------------
25
26
 
26
- Rails 3.0.*
27
+ Rails 3.1.*
27
28
 
28
- (Haven't tested with Rails 3.1.*)
29
+ (It does not work with Rails 3.0.*, yet. Please send me an issue and I will fix it.)
29
30
 
30
31
 
31
32
  How to use it
@@ -46,11 +47,13 @@ Second, create RAILS_ROOT/config/initializers/whowish_word.rb that contains:
46
47
  ```ruby
47
48
  require 'whowish_word'
48
49
 
49
- WhowishWord.ini
50
+ WhowishWord.init(:active_record)
51
+
52
+ WhowishWord.username = "root"
53
+ WhowishWord.password = "pass"
50
54
  ```
51
55
 
52
- You can use either use :mysql or :mongodb
53
- (I have planned to add :redis and :postgresql)
56
+ You can use either use :active_record or :mongoid
54
57
 
55
58
  Performance
56
59
  -------------------
@@ -61,12 +64,13 @@ It is fast because words are kept in memory. They are not kept in database while
61
64
  How to extend WhowishWord to suit your need
62
65
  -------------------------------------------------
63
66
 
64
- WhowishWord is nicely structure. You can extend it by writing a new handler and creator (on client-side) and a new generator (on server-side).
67
+ WhowishWord is nicely structure. You can extend it by writing a new handler and creator (on client-side).
65
68
 
66
69
  Please learn the code structure. If you have any question, feel free to ask me.
67
70
 
68
71
 
69
- Author
72
+ Authors
70
73
  -------------------
71
74
 
72
75
  Tanin Na Nakorn
76
+ Tanun Niyomjit (The design of a dialog box)
@@ -45,8 +45,6 @@ whowishWordHelper.editHandler = function() {
45
45
  content: this.whowishWord.contentHandler.getContent(),
46
46
  success: function(html){
47
47
 
48
- console.log(self.whowishWord.id);
49
-
50
48
  $w.whowishWordDialog.start_loading();
51
49
 
52
50
  $w.ajax({
@@ -3,7 +3,7 @@ $:.push File.expand_path("../lib", __FILE__)
3
3
 
4
4
  Gem::Specification.new do |s|
5
5
  s.name = "whowish_word"
6
- s.version = "0.1.0"
6
+ s.version = "0.1.1"
7
7
  s.platform = Gem::Platform::RUBY
8
8
  s.authors = ["Tanin Na Nakorn"]
9
9
  s.email = ["tanin47@yahoo.com"]
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: whowish_word
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors: