rsence-pre 2.1.0.21 → 2.1.8.0

data/INSTALL.rdoc

@@ -4,21 +4,33 @@ If you already have a working ruby environment and know what to do, the easiest
 
  gem install rsence
 
-Otherwise, follow these instructions:
+If you have an older version of rsence installed, it's be automatically
+updated along other gems when you run:
 
+ gem update
 
-== 1. System Dependencies
+For system-wide installs, run the gem command as a superuser. A common way
+for doing so is prefixing the command with sudo.
+
+RSence 2.1 is verified to be compatible with Rubinius. To use RSence with
+Rubinius, just use "rbx gem" instead of just "gem" for installation.
+
+The following instructions contain detailed steps for installing Ruby, RSence
+and its dependencies on each supported platform:
+
+
+== System Dependencies
 
 This is a list of system level dependencies. You only need to do this step once; follow the steps of for your target operating system.
 
-=== 1.1. Mac OS X
+=== Mac OS X
 
-==== 1.1.1 Mac OS X 10.6
+==== Mac OS X 10.6
 
 * Install *XCode*[http://developer.apple.com/mac/] to get the essential development tools, like compilers.
 * Proceed to section 3.0
 
-==== 1.1.2. Mac OS X 10.4 and 10.5
+==== Mac OS X 10.4 and 10.5
 
 This step applies only to Mac OS X 10.4 "Tiger" and 10.5 "Leopard". The default ruby build of these versions of Mac OS X is somewhat broken.
 
@@ -29,7 +41,7 @@ This step applies only to Mac OS X 10.4 "Tiger" and 10.5 "Leopard". The default
     sudo port install rb-rubygems
 * Proceed to section 3.0
 
-=== 1.2. Debian and Ubuntu Linux
+=== Debian and Ubuntu Linux
 
 This step applies only to Debian, Ubuntu and similar Linux distributions.
 
@@ -37,28 +49,27 @@ This step applies only to Debian, Ubuntu and similar Linux distributions.
     sudo apt-get install build-essential ruby-full rubygems rake
 * Proceed to section 3.0
 
-=== 1.3. Microsoft Windows
+=== Microsoft Windows
 
 RSence works just fine on Windows too, with a few limitations.
 Windows compatibility has been officially tested on Windows XP SP3 and Windows 7 (64 bit).
 
-==== 1.3.1. Install ruby 1.8.7:
-* Download Ruby 1.8.7-p249 (RC2) from http://rubyinstaller.org/downloads
+==== Install ruby 1.8.7:
+* Download Ruby 1.8.7-p302 from http://rubyinstaller.org/downloads
 * Run the downloaded exe to install ruby
   * In the installation and destination prompt, check these options:
     * Add Ruby executables to your PATH
     * Associate .rb and .rbw files with this Ruby installation
-* Download and Install the Development Kit from http://rubyinstaller.org/downloads
-  * Extract the included directories into the directory where you installed ruby.
-    * It's +C:\ruby+ by default.
+* Download and Install the Development Kit (DevKit-tdm-...-sfx.exe) from http://rubyinstaller.org/downloads
+  * Extract the included directories into the directory where you installed ruby, which is +C:\ruby+ by default.
 
-==== 1.3.2. Install RSence
+==== Install RSence
 * In the command prompt, run:
     gem update --system
     gem install rsence
     rsence help
 
-==== 1.3.3. Create RSence environment
+==== Create RSence environment
 
 Replace the +\my_projects+ path with the path to the directory where you want to run or develop your projects. Likewise, replace +my_project+ with something descriptive for your project.
 
@@ -72,7 +83,7 @@ Replace the +\my_projects+ path with the path to the directory where you want to
   * If the address is +0.0.0.0+, enter +127.0.0.1+ instead.
   * Using just defaults, the following URL should work: http://127.0.0.1:8001
 
-==== 1.3.4. Windows limitations
+==== Windows limitations
 If you install the sqlite dll and the sqlite3-ruby gem, you'll gain persistent sessions and this warning message will disappear:
 `Warning: Session database is not available. Can't use persistent sessions`
 
@@ -83,7 +94,7 @@ Backgrounding on Windows is not yet implemented, because POSIX signals are not f
 However, if you run RSence under Cygwin, everything should work like on a UNIX machines.
 
 
-=== 1.4. Other UNIX / Linux systems:
+=== Other UNIX / Linux systems:
 
 This step applies to systems not listed above.
 
@@ -98,13 +109,13 @@ You'll have to figure out how to install the dependencies on your own, but gener
   * gcc, make etc.
 
 
-== 2. Ruby Library Dependencies
+== Ruby Library Dependencies
 
 The `rsence` gem depends on the dummy `rsence-deps` gem, which depends on all essential dependencies of RSence.
 Optionally, you probably want at a database and a database adapter supported by Sequel[http://sequel.rubyforge.org]
 This not only enables SessionStorage (persistent sessions between RSence restarts), but some plugins written for RSence depend on at least Sqlite.
 
-=== 2.1 Detailed list of ruby libraries used
+=== Detailed list of ruby libraries used
 
 * *rake*[http://rake.rubyforge.org]
   * Ruby build tool
@@ -134,23 +145,27 @@ This not only enables SessionStorage (persistent sessions between RSence restart
   * Some plugins depend on it directly.
 
 
-== 3. Setting up RSence
+== Setting up RSence
 
 The primary installation method of RSence is via RubyGems.
 
 To ensure your RubyGems is up-to-date, run:
   sudo gem update --system
+* gem update --system is disabled in Debian based systems, such as Ubuntu. It's okay to skip on these systems.
 
 Even if RubyGems is up-to-date, ensure your installed gems are up-to-date, some of these are updated frequently. This will also update RSence release versions to the most recent version, if installed.
   sudo gem update
 
-=== 3.1. Install RSence
+=== Install RSence
 
 This will install RSence via RubyGems, the preferred method. All dependencies are installed too, except for the ones you already might have installed.
   gem install rsence
 
+Debian/Ubuntu users need to include /var/lib/gems/1.8/bin into PATH either by adding it directly there or by making a symbolic link:
+  sudo ln -s /var/lib/gems/1.8/bin/rsence /usr/local/bin/rsence
+
 Optionally, you might want to contribute to RSence development, just clone or fork the GIT repository on Github:
-  * http://github.com/rsence/rsence
+  http://github.com/rsence/rsence
 
 When installed, ensure it works by exploring the help of the 'rsence' command, like:
   rsence
@@ -160,9 +175,9 @@ When installed, ensure it works by exploring the help of the 'rsence' command, l
   rsence help init
 etc..
 
-=== 3.2. Setting up
+=== Setting up
 
-==== 3.2.1. Creating a RSence project environment
+==== Creating a RSence project environment
 
 To set up an environment for your RSence project, use the init command. In this example '/home/me/projects' is assumed as your project directory. Replace that with a path that matches your own environment. The RSence project directory must either be empty or will be created automatically.
   rsence init /home/me/projects/my_first_rsence_project
@@ -200,29 +215,29 @@ You may edit the conf/config.yaml at a later time to change these settings. The
 
 Any differences in your local configuration replace the default. If the configuration option type is an Array, the defaults are not replaced, the defaults are appended to. If your configuration only has partial items of a Hash defined, only those are applied to the default.
 
-==== 3.2.2. Start RSence in the development mode with logs printed to the standard output:
+==== Start RSence in the development mode with logs printed to the standard output:
 
 The debug/development mode has the most verbose output and is the intended mode of RSence for development. Changes in your code are automatically (re)loaded and the javascript is not obfuscated or minimized in any way. Values also have human-readable id's.
   cd /home/me/projects/my_first_rsence_project
   rsence run -df
 
-==== 3.3.3. Open a web browser
+==== Open a web browser
 * By default, the RSence listens on port 8001
 * To test it, open the address http://127.0.0.1:8001/
 * If everything works:
   * A welcome message is displayed
   * Check the "Don't show again" checkbox and click the "Close" button to make the 'welcome' plugin uninstall itself.
 
-==== 3.3.4. Stop RSence
+==== Stop RSence
 Just press CTRL-C in the terminal, if RSence was started using the 'run' command.
 
 
-== 4. Modes of operation
+== Modes of operation
 
 RSence supports two main modes of operation: in the foreground and in the background. Each have various options. Use the 'rsence help run' and 'rsence help start' commands to read more about them.
 
 
-=== 4.1. Starting RSence as a foreground process.
+=== Starting RSence as a foreground process.
 
 The 'run' mode is well suited for development. Especially when combined with the -d and -f options.
 
@@ -238,26 +253,26 @@ Starting in foreground mode with debug and logging in foreground:
 Stopping in foreground mode: Press CTRL-C
 
 
-=== 4.2. Starting RSence as a daemon (background mode).
+=== Starting RSence as a daemon (background mode).
 
 In the background mode, standard output and standard errors are logged in the 'log' directory of your project and the PID file is written in the 'run' directory. This mode of operation is best suited for production deployment and it's not available on Microsoft Windows, because full POSIX compliance is not available on Windows.
   rsence start
 
-=== 4.2.1 Stopping RSence in background mode
+=== Stopping RSence in background mode
   rsence stop
 
-=== 4.2.2 Checking RSence status in background mode
+=== Checking RSence status in background mode
   rsence status
 
-=== 4.2.3 To store the RSence sessions into the session database while in background mode
+=== To store the RSence sessions into the session database while in background mode
   rsence save
 
 The sessions are also stored when stopping and restarting RSence. Use the 'save' command regularly from a cron script or equivalent in a production environment.
 
-=== 4.3. Restarting RSence in background mode
+=== Restarting RSence in background mode
   rsence restart
 
-=== 4.2.5. Re-setting the sessions
+=== Re-setting the sessions
 This is needed only, if the session storage becomes corrupt in a development environment (changing value definitions and such). This invalidates all ongoing sessions.
 Just apply the --reset-sessions option after the run, start or restart command in the command prompt.
   rsence restart --reset-sessions
@@ -267,11 +282,11 @@ The '-r' switch is equivalent to '--reset-sessions'
 *NOTE: All the sessions currently connected clients are invalidated and need to reload the page*
 
 
-=== 4.4. Running in development mode
+=== Running in development mode
 Just apply the -d option after the *run*, *start* or *restart* command in the command prompt.
   rsence restart -d
 
-==== 4.4.1. What does development mode do?
+==== What does development mode do?
 * Plugins are (re)loaded automatically in the background, if they are changed, disabled, added or removed.
   * This is also enabled with the -a switch (--auto-update)
 * Javascript packages are automatically re-built, if they are changed.
@@ -279,22 +294,22 @@ Just apply the -d option after the *run*, *start* or *restart* command in the co
 * Much more verbose logging
 * Code obfuscation / minimizing options are turned off.
 
-=== 4.5. Other command-line options
+=== Other command-line options
 Just run this command to see the available options:
   rsence help <command>
 example:
   rsence help run
 
-=== 4.6. Running RSence using rackup
+=== Running RSence using rackup
   rackup conf/config.ru
 
-=== 4.7. Running RSence using unicorn
+=== Running RSence using unicorn
   unicorn conf/config.ru -c conf/unicorn.conf
 
 
-== 5. Plugin Deployment
+== Plugin installation
 
-If you followed the previous steps, you are ready to deploy some software.
+If you followed the previous steps, you are ready to install some plugins.
 * In development mode (see 4.4.), plugins are (re/un)loaded when:
   * Adding a new plugin into the plugins directory
   * Removing a plugin from the plugins directory
@@ -302,25 +317,25 @@ If you followed the previous steps, you are ready to deploy some software.
   * Enabling a plugin by removing a file or folder named "disabled" in the plugin's bundle directory
   * The plugin's ruby or yaml files are changed.
 
-* In production mode, a RSence restart is required (see 4.4.), unless running with the '-a' ('--auto-update') option enabled. Enabling it is a good idea for production environments where the code is updated frequently. It enables nearly zero downtime, if code updates are thoroughly tested before being deployed.
+* In production mode, a RSence restart is required (see 4.4.), unless running with the '-a' ('--auto-update') option enabled. Enabling it is a good idea for production environments where the code is updated frequently. It enables nearly zero downtime, if code updates are thoroughly tested before being upgraded.
 
 * By default, the "plugins" directory in the "rsence" directory is the only plugin directory.
   * Edit the configuration file to enable other directories.
 * Sample plugins are available at http://rsence.org/
 
 
-=== 5.1. Deploying plugins
+=== Installing plugins
 Copy or move a plugin bundle directory into the "plugins" directory.
 
-=== 5.2. Un-deploying plugins
+=== Un-Installing plugins
 Move a plugin bundle out of the the "plugins" directory.
 
-=== 5.3. Temporarily disabling a plugin
+=== Temporarily disabling a plugin
 Create an empty file named "disabled" in the plugin bundle to disable it.
   touch plugins/legacy/disabled
 
 
-== 6. Getting more information
+== Getting more information
 
 * Explore http://rsence.org/
 * Join our chat room on IRC (IRCNet and FreeNode):

data/README.rdoc

@@ -5,7 +5,7 @@
 
 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. 
 
-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 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.
+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.
 
 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.
 
@@ -87,6 +87,22 @@ Each command-line tool command takes a number of options, the +env_dir+ argument
 
 For more detailed installation and usage instructions, read the {file:INSTALL Install Guide} document.
 
+=== The bleeding edge (for developers)
+RSence comes in two varieties:
+1. rsence : The stable (no major new featuers, just bugfixes) release.
+2. rsence-pre : The active development snaphot released periodically.
+
+Both varieties can be installed simultaneously and it's suggested to use
+the stable "rsence" package for production installations and to use the
+"rsence-pre" package for development purposes, because the RSence crew
+can't possibly test each and every application available. It's your 
+responsibility as a developer to report any RSence issues effecting your
+software. The sooner reported, the better; it ensures better release 
+versions.
+
+To use "rsence-pre", install the "rsence-pre" gem and use the "rsence-pre" 
+command instead of the "rsence" command.
+
 === Licensing and commercial support options
 * {file:LICENSE.txt *GPL*} version 3 by default.
 * Riassence[http://riassence.com/] Inc. provides commercial support, custom licensing arrangements and various other services.

data/VERSION

@@ -1 +1 @@
-2.1.0.21.pre
+2.1.8.0.pre

data/conf/rsence_command_strings.yaml

@@ -421,35 +421,35 @@
   
   :version: |+
     usage: 'rsence version'
-  
+    
     The 'version' command simply outputs the version number of RSence.
-  
-    RSence follows the standard four-numbered sequence-based version identification
-    scheme. The scheme is defined like: major.minor[.maintenance[.package]][.pre]
-  
+    
+    RSence follows the common three-numbered sequence-based version identification
+    scheme. The scheme is defined like: major.minor[.maintenance]
+    
     The major number designates major changes in functionality, sometimes limiting
     backwards compatibility with software written for previous versions.
-  
+    
     The minor number designates minor changes in functionality, like minor or
     moderate changes in functionality that usually don't impact backwards
     compatibilty of software written for a previous release with the same major
     version.
-  
+    
     The maintenance number designates bug fixes and other minimal changes to
     the release. In a maintenance number change, no new features are introduced.
-  
+    
     The package number is a sequence used for the package release. Rubygems
     requires an unique version for each gem released, so pre-releases usually
     occupy the first package numbers of any release.
-  
-    The '.pre' suffix signifies a pre-release, like "Alpha" or "Beta". To
-    install a prerelease version, gem requires the '--pre' command line argument.
-    Release versions never have the '.pre' suffix. There are usually several
-    package number increments of a new release.
-  
+    
+    RSence also comes in a '-pre' variety. Consider RSence prereleases as
+    anything between 'Alpha', 'Beta' and 'Release Candidate'. The prereleases
+    are have a fourth number in their version number string. That number
+    is the 'package' or 'build' number.
+    
     Version number conventions in written text should include both major and
     minor version numbers prefixed with 'RSence'. The maintennance number
     is usally not mentioned unless an issue is fix or such is discussed.
-  
-    For instance: "RSence 2.0 has undergone some major refactoring since 1.2.1"
+    
+    Example: "RSence 2.0 has undergone some major refactoring since 1.2.1"
   

data/js/comm/sessionwatcher/sessionwatcher.js

@@ -25,14 +25,15 @@
 COMM.SessionWatcher = HApplication.extend({
   constructor: function( _timeoutSecs, _sesTimeoutValueId ){
     
-    // onIdle is called when HSystem's ticker count % 100 == 0
-    // this means it's 5 seconds with HSystemTickerInterval 50
-    this.base(10, 'SesWatcher'); 
-    
     // gets the HValue represented by
     // sesTimeoutValueId (:client_time in server)
     this.sesTimeoutValue = COMM.Values.values[_sesTimeoutValueId];
     this.timeoutSecs = _timeoutSecs;
+    
+    // onIdle is called when HSystem's ticker count % 100 == 0
+    // this means it's 5 seconds with HSystemTickerInterval 50
+    this.base(10, 'SesWatcher'); 
+    
   },
   
   // Tells the server the client's current time

data/js/comm/transporter/transporter.js

@@ -27,7 +27,8 @@ COMM.Transporter = HApplication.extend({
   **/
   constructor: function(){
     var _this = this;
-    this.serverLostMessage = 'Server Connection Lost: Reconnecting...';
+    _this._detectNativeJSONSupport();
+    _this.serverLostMessage = 'Server Connection Lost: Reconnecting...';
     _this.label = 'Transporter';
     _this.url = false;
     _this.busy = false;
@@ -37,6 +38,17 @@ COMM.Transporter = HApplication.extend({
     _this._busyFlushTimeout = false;
     _this.base(1);
   },
+
+  _detectNativeJSONSupport: function(){
+    if(window['JSON']){
+      var
+      _JSON = window.JSON,
+      _fun = 'function';
+      if((typeof _JSON['parse'] === _fun) && (typeof _JSON['stringify'] === _fun)){
+        this.parseResponseArray = this._nativeParseResponseArray;
+      }
+    }
+  },
   
 /** Tries to (re)connect to the server as often as possible,
   * mandated essentially by the priority of its
@@ -64,6 +76,49 @@ COMM.Transporter = HApplication.extend({
            COMM.Values._encodeString(_this._clientEvalError):'';
   },
   
+  parseResponseArray: function( _responseText ){
+    var _arr = eval( _responseText );
+    return _arr;
+  },
+  
+  _nativeParseResponseArray: function( _responseText ){
+    var _arr = JSON.parse( _responseText );
+    return _arr;
+  },
+  
+  setValues: function( _values ){
+    if(!_values instanceof Object){
+      console.log("Invalid values block: ", _values );
+      return;
+    }
+    var
+    i = 0,
+    _valueManager = COMM.Values,
+    _itemtype,
+    _valueId,
+    _valueData;
+    if(_values['new'] instanceof Array){
+      for(i=0;i<_values['new'].length;i++){
+        _valueId = _values['new'][i][0];
+        _valueData = _values['new'][i][1];
+        _valueManager.create( _valueId, _valueData );
+      }
+    }
+    if(_values['set'] instanceof Array){
+      for(i=0;i<_values['set'].length;i++){
+        _valueId = _values['set'][i][0];
+        _valueData = _values['set'][i][1];
+        _valueManager.s( _valueId, _valueData );
+      }
+    }
+    if(_values['del'] instanceof Array){
+      for(i=0;i<_values['del'].length;i++){
+        _valueId = _values['del'][i];
+        _valueManager.del( _valueId );
+      }
+    }    
+  },
+  
 /** = Description
   * Handles synchronization responses.
   *
@@ -83,10 +138,11 @@ COMM.Transporter = HApplication.extend({
       _this.failure(resp);
       return;
     }
-    var _responseArray = eval(resp.X.responseText),
-        i = 1,
+    var _responseArray = _this.parseResponseArray(resp.X.responseText),
+        i = 2,
         _responseArrayLen = _responseArray.length,
         _sesKey = _responseArray[0],
+        _values = _responseArray[1],
         _session = COMM.Session,
         _queue = COMM.Queue;
     if(_sesKey === ''){
@@ -95,6 +151,7 @@ COMM.Transporter = HApplication.extend({
     else {
       _session.newKey(_sesKey);
     }
+    _this.setValues( _values );
     for(;i<_responseArrayLen;i++){
       try {
         _queue.pushEval( _responseArray[i] );
@@ -123,7 +180,7 @@ COMM.Transporter = HApplication.extend({
   failMessage: function(_title,_message){
     var _this = COMM.Transporter,
         _queue = COMM.Queue;
-    console.log('failMessage?');
+    console.log('failMessage title:',_title,', message:',_message);
     _this.stop = true;
     _queue.push(function(){jsLoader.load('default_theme');});
     _queue.push(function(){jsLoader.load('controls');});
@@ -240,6 +297,7 @@ COMM.Transporter = HApplication.extend({
     // console.log('sync.');
     this.busy = true;
     if(window['sesWatcher'] && window.sesWatcher['sesTimeoutValue']){
+      // Sets the value of the session watcher to the current time. It could cause an unnecessary re-sync poll immediately after this sync otherwise.
       sesWatcher.sesTimeoutValue.set( new Date().getTime() );
     }
     var _this = this,

data/js/comm/values/values.js

@@ -322,6 +322,11 @@ COMM.Values = HClass.extend({
     return _str;
   },
   
+  _nativeEncode: function(_obj){
+    return JSON.stringify( _obj );
+  },
+  
+  
 /** = Description
   * Decodes a JSON object. Decodes url-encoded strings contained.
   *
@@ -355,6 +360,29 @@ COMM.Values = HClass.extend({
     return _obj;
   },
   
+  _nativeDecode: function(_ibj){
+    var _obj, _type, _this = this;
+    if(_ibj !== null && _ibj !== undefined){
+      _type = _this.type(_ibj);
+      if(!_type){
+        return null;
+      }
+      switch(_type){
+        case 'b': _obj = _ibj; break;
+        case 'n': _obj = _ibj; break;
+        case 's': _obj = _this._decodeString(_ibj); break;
+        case 'd': _obj = _ibj; break;
+        case 'a': _obj = JSON.parse(_ibj); break;
+        case 'h': _obj = JSON.parse(_ibj); break;
+        default: _obj = null; break;
+      }
+    }
+    else {
+      return null;
+    }
+    return _obj;
+  },
+  
 /** = Description
   * Makes a deep copy of the object.
   *
@@ -408,6 +436,24 @@ COMM.Values = HClass.extend({
     }
   },
   
+  _nativeClone: function( _obj ){
+    if(_obj === null){
+      return null;
+    }
+    else if (_obj === undefined){
+      console.log('Undefined object, supplementing with null.');
+      return null;
+    }
+    if( (_obj instanceof Array) || (_obj instanceof Object) ){
+      // conversion via encoding/decoding via JSON string.
+      return JSON.parse( JSON.stringify( _obj ) );
+    }
+    else {
+      // no conversion needed (numbers, strings, booleans etc..)
+      return _obj;
+    }
+  },
+  
 /** = Description
   * Returns an URI-encoded string representation of all the changed values to
   * synchronize to the server.
@@ -431,9 +477,25 @@ COMM.Values = HClass.extend({
       _syncValues[_id] = _value;
     }
     return encodeURIComponent(_this.encode(_syncValues));
+  },
+  
+  _detectNativeJSONSupport: function(){
+    if(window['JSON']){
+      var
+      _JSON = window.JSON,
+      _fun = 'function';
+      if((typeof _JSON['parse'] === _fun) && (typeof _JSON['stringify'] === _fun)){
+        // console.log('Has native JSON support. Re-routing encode, decode and clone methods of COMM.Values...');
+        this.clone = this._nativeClone;
+        this.encode = this._nativeEncode;
+        // this.decode = this._nativeDecode;
+      }
+    }
   }
 });
 
+COMM.Values._detectNativeJSONSupport();
+
 // Backwards compatibility assignment for code that still
 // uses HVM as a reference of the Value Manager:
 HVM = COMM.Values;

data/js/controls/button/themes/default/button.css

@@ -25,7 +25,7 @@
 }
 
 .button_edge_left {
-  left: 0px; width: 24px;
+  left: 0px; width: 6px;
   background-position: 0px 0px;
 }
 .disabled > .button_control > .button_edge_left {
@@ -39,21 +39,21 @@
 }
 
 .button_edge_right {
-  right: 0px; width: 24px;
-  background-position: -24px 0px;
+  right: 0px; width: 6px;
+  background-position: -42px 0px;
 }
 .disabled > .button_control > .button_edge_right {
-  background-position: -24px -144px;
+  background-position: -42px -144px;
 }
 .enabled > .button_control:hover > .button_edge_right {
-  background-position: -24px -48px;
+  background-position: -42px -48px;
 }
 .enabled > .button_control:active > .button_edge_right {
-  background-position: -24px -96px;
+  background-position: -42px -96px;
 }
 
 .button_center {
-  left: 24px; right: 24px;
+  left: 6px; right: 6px;
   background-position: 0px -24px;
 }
 .disabled > .button_control > .button_center {