Merge pull request #1 from QuickCorp/language-es

Language es

QCObjects.js

@@ -1687,12 +1687,12 @@
                 a.oldclick = a.onclick;
                 a.onclick = function(e) {
                   var _ret_ = true;
-                  if (!global.get("routingPaths")) {
-                    global.set("routingPaths", []);
+                  if (!_top.global.get("routingPaths")) {
+                    _top.global.set("routingPaths", []);
                   }
                   var routingWay = ClassFactory("CONFIG").get("routingWay");
                   var routingPath = e.target[routingWay];
-                  if (global.get("routingPaths").includes(routingPath) &&
+                  if (_top.global.get("routingPaths").includes(routingPath) &&
                     e.target[routingWay] !== document.location[routingWay] &&
                     e.target.href !== document.location.href
                   ) {
@@ -1801,11 +1801,11 @@
                 routing[attributeNames[a]] = routingNode.getAttribute(attributeNames[a]);
               }
               this.routings.push(routing);
-              if (!global.get("routingPaths")) {
-                global.set("routingPaths", []);
+              if (!_top.global.get("routingPaths")) {
+                _top.global.set("routingPaths", []);
               }
-              if (!global.get("routingPaths").includes(routing.path)) {
-                global.get("routingPaths").push(routing.path);
+              if (!_top.global.get("routingPaths").includes(routing.path)) {
+                _top.global.get("routingPaths").push(routing.path);
               }
             }
           }
@@ -1973,7 +1973,7 @@
           var component = this;
           var lang1=ClassFactory("CONFIG").get("lang","en");
           var lang2 = navigator.language.slice(0, 2);
-          var i18n = global.get("i18n");
+          var i18n = _top.global.get("i18n");
           if ((lang1 !== lang2) && (typeof i18n === "object" && i18n.hasOwnProperty.call(i18n,"messages"))){
             var callback_i18n = function (){
               var component = this;

README.md

@@ -28,7 +28,7 @@ You can contribute to [QCObjects](https://qcobjects.dev) following the set of gu
 
 For those who have no time to read all of this today, here is a small video that explains what QCObjects is and what can be done with it.
 
-[![QCObjects Explainer Video](http://img.youtube.com/vi/D0rftABPGvQ/0.jpg)](http://www.youtube.com/watch?v=D0rftABPGvQ "QCObjects Explainer Video")
+[![QCObjects Explainer Video](https://img.youtube.com/vi/D0rftABPGvQ/0.jpg)](https://www.youtube.com/watch?v=D0rftABPGvQ "QCObjects Explainer Video")
 
 _________________________
 # Table of Contents
@@ -91,7 +91,6 @@ _________________________
 		- [GLOBAL](#global)
 		- [CONFIG](#config)
 		- [Processor](#processor)
-- [for Unix/Linux systems](#for-unixlinux-systems)
 		- [waitUntil](#waituntil)
 		- [Package](#package)
 		- [Import](#import)
@@ -1010,8 +1009,9 @@ Processor.setProcessor(SERVICE_PORT);
 
 Then you only need to set your environment variable SERVICE_URL in your shell
 
+This is only for Unix/Linux systems
+
 ```shell
-# for Unix/Linux systems
 export SERVICE_URL="https://example.com:443/path-to-a-resource/"
 ```
 
@@ -1660,8 +1660,44 @@ Class("MyNewController",Controller,{
 ```
 
 ### Effect
+
+**Effect** is a super class to define custom effects.
+
+#### Example:
+
+```javascript
+Class('CustomFade',Effect,{
+	duration:500, // milliseconds of duration
+	apply: function (){
+		// You need the following line to apply a Fade effect in runtime
+		_super_('Fade','apply').apply(this,arguments);
+	}
+})
+```
+
+
 ### Timer
 
+**Timer** is a special implementation of **requestAnimationFrame** to emulate the creation of thread instances, so you can handle runtime paralell processing in a little bit more efficient way.
+
+NOTE: As it is currently depending in requestAnimationFrame availability it only works on modern browsers.
+
+#### Example:
+
+```javascript
+Timer.thread({
+		duration:300, // duration in milliseconds
+		timing(timeFraction,elapsed){
+			return timeFraction; // you can change this line to return a custom math function for timing
+		},
+		intervalInterceptor(progress){
+			if (progress>=100){
+				// do whatever you want here
+			}
+		}
+});
+```
+
 ## List and Math Functions
 
 ### ArrayList
@@ -1990,7 +2026,7 @@ Inside of the body of your component, when it is a **FormField** component, ever
 
 #### org.quickcorp.components.ButtonField
 
-**ButtonField** is a sub-definition of **FormField**, that is commonly used for almost the same purpose of FormField. The main difference between ButtonField and FormField is that ButtonField has a **<button>** DOM element as the body of the component by default. And FormField hasn't a pre-defined body.
+**ButtonField** is a sub-definition of **FormField**, that is commonly used for almost the same purpose of FormField. The main difference between ButtonField and FormField is that ButtonField has a **```<button>```** DOM element as the body of the component by default. And FormField hasn't a pre-defined body.
 
 ##### Usage:
 
@@ -2011,7 +2047,7 @@ Inside of the body of your component, when it is a **FormField** component, ever
 
 #### org.quickcorp.components.TextField
 
-**ButtonField** is a sub-definition of **FormField**, that is commonly used for almost the same purpose of FormField. The main difference between InputField and FormField is that ButtonField has a **<textarea>** DOM element as the body of the component by default. And FormField hasn't a pre-defined body.
+**ButtonField** is a sub-definition of **FormField**, that is commonly used for almost the same purpose of FormField. The main difference between InputField and FormField is that ButtonField has a **```<textarea>```** DOM element as the body of the component by default. And FormField hasn't a pre-defined body.
 
 ##### Usage:
 
@@ -2022,7 +2058,7 @@ Inside of the body of your component, when it is a **FormField** component, ever
 
 #### org.quickcorp.components.EmailField
 
-**EmailField** is a sub-definition of **FormField**, that is commonly used for almost the same purpose of FormField. The main difference between ButtonField and FormField is that ButtonField has a **<input>** DOM element as the body of the component by default. And FormField hasn't a pre-defined body.
+**EmailField** is a sub-definition of **FormField**, that is commonly used for almost the same purpose of FormField. The main difference between ButtonField and FormField is that ButtonField has a **```<input>```** DOM element as the body of the component by default. And FormField hasn't a pre-defined body.
 
 ##### Usage:
 
@@ -2746,7 +2782,7 @@ QCObjects was designed to work into a professional environment. There are many w
 The benefits of a Multitier or N-Tier architecture are scalability and reliability of the systems that are demanding higger impact and performance. To go deep into this concepts would unnecessary enlarge this reference document but you can read more about this concepts in the following external links (only for reference and study):
 
 - [Miltitier Architecture](https://en.m.wikipedia.org/wiki/Multitier_architecture)
-- [3 Tier Architecture](http://www.tonymarston.net/php-mysql/3-tier-architecture.html)
+- [3 Tier Architecture](https://www.tonymarston.net/php-mysql/3-tier-architecture.html)
 - [Milti Tier Application](https://www.techopedia.com/definition/23599/multi-tier-application)
 - [N Tier Architecture System Concepts and Tips](https://www.guru99.com/n-tier-architecture-system-concepts-tips.html)
 
@@ -3070,19 +3106,19 @@ Import('cl.quickcorp'); # this will import your main file: cl.quickcorp.js into
 
 ## Options
 
- *  -V, --version                output the version number
- *  -h, --help                   output usage information
+   -V, --version                output the version number
+   -h, --help                   output usage information
 
 ## Commands
 
- *  **create** [options] <appname>   Creates an app with <appname>
- *  **publish** [options] <appname>  Publishes an app with <appname>
- *  **generate-sw** <appname>        Generates the service worker  <appname>
- *  **launch** <appname>             Launches the application
+   **create** [options] ```<appname>```   Creates an app with ```<appname>```
+   **publish** [options] ```<appname>```  Publishes an app with ```<appname>```
+   **generate-sw** ```<appname>```        Generates the service worker  ```<appname>```
+   **launch** ```<appname>```             Launches the application
 
 ## Use:
- *  $ qcobjects-cli [command] --help
- *  For detailed information of a command
+   $ qcobjects-cli [command] --help
+   For detailed information of a command
 
 # ALPHA RISE Startup
 --------------------------

VERSION

@@ -1 +1 @@
-2.2.449
+2.2.455

manifest.json

@@ -36,7 +36,8 @@
     {
       "src": "img/icons/icon-192x192.png",
       "sizes": "192x192",
-      "type": "image/png"
+      "type": "image/png",
+      "purpose": "any maskable"
     },
     {
       "src": "img/icons/icon-384x384.png",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "qcobjects",
-  "version": "2.2.449",
+  "version": "2.2.455",
   "description": "QCObjects is an Open-source framework that empowers full-stack developers to make micro-services and micro-frontends into an N-Tier architecture.",
   "main": "QCObjects.js",
   "license": "LGPL-3.0",