public
Description: Generic support for extracting GMail-style search keywords/values from strings
Homepage: http://codefluency.rubyforge.org/keyword_search
Clone URL: git://github.com/bruce/keyword_search.git
Updating Rakefile

git-svn-id: 
svn+ssh://rubyforge.org/var/svn/codefluency/keyword_search/trunk@9 
a36c4c08-a44a-49c9-8a5d-6074d9d18ea7
wbruce (author)
Mon Jan 08 13:31:18 -0800 2007
commit  d566a77c5493a467198c7ad4f30b6fc2e7db05ee
tree    935d359596f3bfb90c1bf500f83e1347a7fceb3c
parent  14b8c73dcca1a8e054dd9a265cc1be376329552f
...
23
24
25
26
27
 
28
29
30
...
32
33
34
 
35
36
37
...
23
24
25
 
 
26
27
28
29
...
31
32
33
34
35
36
37
0
@@ -23,8 +23,7 @@ Development Roadmap:
0
 
0
 == SYNOPSIS:
0
 
0
-Here's an example of usage from Rails.
0
-* Note that the library is generic, and could presumably be used for any Ruby project.
0
+Here's an example of usage from Rails (though the library is generic, and could presumably be used for any Ruby project)
0
 
0
   # Some variables to build up
0
   clauses = []
0
@@ -32,6 +31,7 @@ Here's an example of usage from Rails.
0
 
0
   # Search a string, defining the supported keywords and building up
0
   # the variables in the associated closures
0
+
0
   KeywordSearch.search('account has:attachment since:2006-12-03') do |with|
0
 
0
     with.default_keyword :title
...
5
6
7
8
 
9
10
11
...
5
6
7
 
8
9
10
11
0
@@ -5,7 +5,7 @@ require 'hoe'
0
 require './lib/keyword_search.rb'
0
 
0
 Hoe.new('keyword_search', KeywordSearch::VERSION) do |p|
0
- p.rubyforge_name = 'keyword_search'
0
+ p.rubyforge_name = 'codefluency'
0
   p.summary = 'Generic support for extracting GMail-style search keywords/values from strings'
0
   p.description = p.paragraphs_of('README.txt', 2..5).join("\n\n")
0
   p.url = p.paragraphs_of('README.txt', 0).first.split(/\n/)[1..-1]
...
7
8
9
10
 
11
12
13
...
7
8
9
 
10
11
12
13
0
@@ -7,7 +7,7 @@ end
0
 
0
 module KeywordSearch
0
   
0
- VERSION = '1.0.0'
0
+ VERSION = '1.0.1'
0
   
0
   class << self
0
     def search(input_string, definition=nil, &block)

Comments

    No one has commented yet.