rsence-pre 2.2.0.37 → 2.2.0.38

Sign up to get free protection for your applications and to get access to all the features.
data/VERSION CHANGED
@@ -1 +1 @@
1
- 2.2.0.37.pre
1
+ 2.2.0.38.pre
metadata CHANGED
@@ -1,75 +1,61 @@
1
- --- !ruby/object:Gem::Specification
1
+ --- !ruby/object:Gem::Specification
2
2
  name: rsence-pre
3
- version: !ruby/object:Gem::Version
4
- version: 2.2.0.37
3
+ version: !ruby/object:Gem::Version
4
+ hash: 51
5
5
  prerelease:
6
+ segments:
7
+ - 2
8
+ - 2
9
+ - 0
10
+ - 38
11
+ version: 2.2.0.38
6
12
  platform: ruby
7
- authors:
13
+ authors:
8
14
  - Riassence Inc.
9
15
  - Juha-Jarmo Heinonen
10
16
  autorequire:
11
17
  bindir: bin
12
18
  cert_chain: []
13
- date: 2012-01-27 00:00:00.000000000 Z
14
- dependencies:
15
- - !ruby/object:Gem::Dependency
19
+
20
+ date: 2012-02-21 00:00:00 Z
21
+ dependencies:
22
+ - !ruby/object:Gem::Dependency
16
23
  name: rsence-deps
17
- requirement: &70324729769980 !ruby/object:Gem::Requirement
24
+ prerelease: false
25
+ requirement: &id001 !ruby/object:Gem::Requirement
18
26
  none: false
19
- requirements:
20
- - - =
21
- - !ruby/object:Gem::Version
22
- version: '966'
27
+ requirements:
28
+ - - "="
29
+ - !ruby/object:Gem::Version
30
+ hash: 1935
31
+ segments:
32
+ - 966
33
+ version: "966"
23
34
  type: :runtime
24
- prerelease: false
25
- version_requirements: *70324729769980
26
- description: ! 'RSence is a different and unique development model and software frameworks
27
- designed first-hand for real-time web applications. RSence consists of separate,
28
- but tigtly integrated data- and user interface frameworks.
29
-
30
-
35
+ version_requirements: *id001
36
+ description: |-
37
+ RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks.
38
+
31
39
  RSence could be classified as a thin server - thick client system.
32
-
33
-
34
- Applications and submobules are installed as indepenent plugin bundles into the
35
- plugins folder of a RSence environment, which in itself is a self-contained bundle.
36
- A big part of RSence itself is implemented as shared plugin bundles.
37
-
38
-
39
- The user interface framework of RSence is implemented in high-level user interface
40
- widget classes. The widget classes share a common foundation API and access the
41
- browser''s native API''s using an abstracted event- and element layer, which provides
42
- exceptional cross-browser compatibility.
43
-
44
-
45
- The data framework of RSence is a event-driven system, which synchronized shared
46
- values between the client and server. It''s like a realtime bidirectional form-submission
47
- engine that handles data changes intelligently. On the client, changed values trigger
48
- events on user interface widgets. On the server, changed values trigger events on
49
- value responder methods of server plugin modules. It doesn''t matter if the change
50
- originates on client or server, it''s all synchronized and propagated automatically.
51
-
52
-
53
- The server framework is implemented as a high-level, modular data-event-driven system,
54
- which handles delegation of tasks impossible to implement using a client-only approach.
55
-
56
- Client sessions are selectively connected to other client sessions and legacy back-ends
57
- via the server by using the data framework.
58
-
59
-
60
- The client is written in Javascript and the server is written in Ruby. The client
61
- also supports CoffeeScript for custom logic. In many cases, no custom client logic
62
- is needed; the user interfaces can be defined in tree-like data models. By default,
63
- the models are parsed from YAML files, and other structured data formats are possible,
64
- including XML, JSON, databases or any custom logic capable of producing similar
65
- objects. The server can connect to custom environments and legacy backends accessible
66
- on the server, including software written in other languages.'
40
+
41
+ Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles.
42
+
43
+ The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility.
44
+
45
+ The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically.
46
+
47
+ The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach.
48
+ Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework.
49
+
50
+ The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
67
51
  email: info@rsence.org
68
- executables:
52
+ executables:
69
53
  - rsence-pre
70
54
  extensions: []
55
+
71
56
  extra_rdoc_files: []
72
- files:
57
+
58
+ files:
73
59
  - lib/rsence/argv/argv_util.rb
74
60
  - lib/rsence/argv/env_check.rb
75
61
  - lib/rsence/argv/help_argv.rb
@@ -264,7 +250,6 @@ files:
264
250
  - js/controls/window/window.js
265
251
  - js/core/class/class.js
266
252
  - js/core/elem/elem.coffee
267
- - js/core/elem/elem.js
268
253
  - js/core/event/event.js
269
254
  - js/core/iefix/ie_css_element.htc
270
255
  - js/core/iefix/ie_css_style.htc
@@ -356,28 +341,42 @@ files:
356
341
  - .yardopts
357
342
  - bin/rsence-pre
358
343
  homepage: http://www.rsence.org/
359
- licenses:
344
+ licenses:
360
345
  - GPL-3
361
346
  post_install_message:
362
347
  rdoc_options: []
363
- require_paths:
348
+
349
+ require_paths:
364
350
  - lib
365
- required_ruby_version: !ruby/object:Gem::Requirement
351
+ required_ruby_version: !ruby/object:Gem::Requirement
366
352
  none: false
367
- requirements:
368
- - - ! '>='
369
- - !ruby/object:Gem::Version
353
+ requirements:
354
+ - - ">="
355
+ - !ruby/object:Gem::Version
356
+ hash: 57
357
+ segments:
358
+ - 1
359
+ - 8
360
+ - 7
370
361
  version: 1.8.7
371
- required_rubygems_version: !ruby/object:Gem::Requirement
362
+ required_rubygems_version: !ruby/object:Gem::Requirement
372
363
  none: false
373
- requirements:
374
- - - ! '>'
375
- - !ruby/object:Gem::Version
364
+ requirements:
365
+ - - ">"
366
+ - !ruby/object:Gem::Version
367
+ hash: 25
368
+ segments:
369
+ - 1
370
+ - 3
371
+ - 1
376
372
  version: 1.3.1
377
373
  requirements: []
374
+
378
375
  rubyforge_project: rsence-
379
- rubygems_version: 1.8.15
376
+ rubygems_version: 1.8.17
380
377
  signing_key:
381
378
  specification_version: 3
382
379
  summary: Pre-Release 2.2 version of RSence.
383
380
  test_files: []
381
+
382
+ has_rdoc: