rsence 2.1.8 → 2.1.9

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. data/INSTALL.rdoc +1 -1
  2. data/README.rdoc +4 -4
  3. data/VERSION +1 -1
  4. data/lib/conf/argv.rb +1 -0
  5. metadata +5 -5
@@ -132,7 +132,7 @@ This not only enables SessionStorage (persistent sessions between RSence restart
132
132
  * *randgen*:: C-optimized random string generator developed for RSence specifically
133
133
  * *jsmin_c*:: C-optimized Javascript whitespace removal library; Ruby wrapper developed for RSence specifically; based on the original JSMin[http://www.crockford.com/javascript/jsmin.html]
134
134
  * *jscompress*:: C-optimized Javascript compression and obfuscation library developed for RSence specifically
135
- * *html_min*:: C-optimized HTML whitespace removal library developed for RSence specfically
135
+ * *html_min*:: C-optimized HTML whitespace removal library developed for RSence specifically
136
136
  * *cssmin*:: CSS whitespace removal library
137
137
  * *sequel*[http://sequel.rubyforge.org/]
138
138
  * Generic SQL database ORM
@@ -5,7 +5,7 @@
5
5
 
6
6
  RSence is a RIA framework designed for responsive GUI applications on the web; it's implemented as a hybrid Ruby - Javascript system. The server is written in Ruby and C. Applications are installed as plugin bundles. The GUI framework is written in Javascript; it doesn't strictly require the server, but has extensive transport support with automatic data synchronization with the server. User interfaces are usually described in structured view trees represented by YAML data structures, which are automatically converted for rendering in the client.
7
7
 
8
- Javascript knowledge is required only when creating custom client-driven functionality; basic understanding of the YAML GUITree structures is enough in most cases. Likewise, no prior Ruby knowledge is needed if you want to create stand-alone Javascript applitations. Javascript component themes are easily created with just basic web designer skills. Data API's are easy to link no matter what language is used to create them. Skills in your organization are easily combined for various parts of larger applications.
8
+ Javascript knowledge is required only when creating custom client-driven functionality; basic understanding of the YAML GUITree structures is enough in most cases. Likewise, no prior Ruby knowledge is needed if you want to create stand-alone Javascript applications. Javascript component themes are easily created with just basic web designer skills. Data API's are easy to link no matter what language is used to create them. Skills in your organization are easily combined for various parts of larger applications.
9
9
 
10
10
  RSence is not primarily targeted as an engine for plain old html web sites, there are plenty of other tools for that purpose and RSence is easily integrated with them in various ways.
11
11
 
@@ -17,7 +17,7 @@ Just run this command in the shell, if you have ruby installed. Otherwise, read
17
17
 
18
18
  == Initializing a new project
19
19
 
20
- The +init+ command will cretate a directory called `env_dir` in this example. It asks a few questions about the environment. Use a path and project name that matches your purposes.
20
+ The +init+ command will create a directory called `env_dir` in this example. It asks a few questions about the environment. Use a path and project name that matches your purposes.
21
21
  rsence init /home/me/rsence_projects/env_dir
22
22
 
23
23
 
@@ -89,8 +89,8 @@ For more detailed installation and usage instructions, read the {file:INSTALL In
89
89
 
90
90
  === The bleeding edge (for developers)
91
91
  RSence comes in two varieties:
92
- 1. rsence : The stable (no major new featuers, just bugfixes) release.
93
- 2. rsence-pre : The active development snaphot released periodically.
92
+ 1. rsence : The stable (no major new features, just bug fixes) release.
93
+ 2. rsence-pre : The active development snapshot released periodically.
94
94
 
95
95
  Both varieties can be installed simultaneously and it's suggested to use
96
96
  the stable "rsence" package for production installations and to use the
data/VERSION CHANGED
@@ -1 +1 @@
1
- 2.1.8
1
+ 2.1.9
@@ -139,6 +139,7 @@ module RSence
139
139
  @args[:conf_files].push( arg )
140
140
  end
141
141
  else
142
+ arg = arg.to_i if option_name == :latency
142
143
  @args[option_name] = arg
143
144
  end
144
145
  expect_option = false
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: rsence
3
3
  version: !ruby/object:Gem::Version
4
- hash: 27
4
+ hash: 25
5
5
  prerelease:
6
6
  segments:
7
7
  - 2
8
8
  - 1
9
- - 8
10
- version: 2.1.8
9
+ - 9
10
+ version: 2.1.9
11
11
  platform: ruby
12
12
  authors:
13
13
  - Riassence Inc.
@@ -15,7 +15,7 @@ autorequire:
15
15
  bindir: bin
16
16
  cert_chain: []
17
17
 
18
- date: 2011-01-28 00:00:00 +02:00
18
+ date: 2011-02-19 00:00:00 +02:00
19
19
  default_executable: rsence
20
20
  dependencies:
21
21
  - !ruby/object:Gem::Dependency
@@ -403,7 +403,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
403
403
  requirements: []
404
404
 
405
405
  rubyforge_project: rsence-
406
- rubygems_version: 1.4.2
406
+ rubygems_version: 1.5.0
407
407
  signing_key:
408
408
  specification_version: 3
409
409
  summary: Release 2.1 version of the RSence framework.