You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Effect** is a super class to define custom effects.
1665
+
1666
+
#### Example:
1667
+
1668
+
```javascript
1669
+
Class('CustomFade',Effect,{
1670
+
duration:500, // milliseconds of duration
1671
+
apply:function (){
1672
+
// You need the following line to apply a Fade effect in runtime
1673
+
_super_('Fade','apply').apply(this,arguments);
1674
+
}
1675
+
})
1676
+
```
1677
+
1678
+
1663
1679
### Timer
1664
1680
1681
+
**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.
1682
+
1683
+
NOTE: As it is currently depending in requestAnimationFrame availability it only works on modern browsers.
1684
+
1685
+
#### Example:
1686
+
1687
+
```javascript
1688
+
Timer.thread({
1689
+
duration:300, // duration in milliseconds
1690
+
timing(timeFraction,elapsed){
1691
+
return timeFraction; // you can change this line to return a custom math function for timing
1692
+
},
1693
+
intervalInterceptor(progress){
1694
+
if (progress>=100){
1695
+
// do whatever you want here
1696
+
}
1697
+
}
1698
+
});
1699
+
```
1700
+
1665
1701
## List and Math Functions
1666
1702
1667
1703
### ArrayList
@@ -1990,7 +2026,7 @@ Inside of the body of your component, when it is a **FormField** component, ever
1990
2026
1991
2027
#### org.quickcorp.components.ButtonField
1992
2028
1993
-
**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.
2029
+
**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.
1994
2030
1995
2031
##### Usage:
1996
2032
@@ -2011,7 +2047,7 @@ Inside of the body of your component, when it is a **FormField** component, ever
2011
2047
2012
2048
#### org.quickcorp.components.TextField
2013
2049
2014
-
**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.
2050
+
**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.
2015
2051
2016
2052
##### Usage:
2017
2053
@@ -2022,7 +2058,7 @@ Inside of the body of your component, when it is a **FormField** component, ever
2022
2058
2023
2059
#### org.quickcorp.components.EmailField
2024
2060
2025
-
**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.
2061
+
**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.
2026
2062
2027
2063
##### Usage:
2028
2064
@@ -2746,7 +2782,7 @@ QCObjects was designed to work into a professional environment. There are many w
2746
2782
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):
Copy file name to clipboardexpand all lines: package.json
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
{
2
2
"name": "qcobjects",
3
-
"version": "2.2.449",
3
+
"version": "2.2.455",
4
4
"description": "QCObjects is an Open-source framework that empowers full-stack developers to make micro-services and micro-frontends into an N-Tier architecture.",
0 commit comments