INTRODUCTION - OPTIMIZE - jor_aniMateLIMITER
LIMITER PROPERTY:
JMP MODULE TARGET:
RECOMMENDED:
module | cycle
default: false
recommended state: false
- if module | cycle is not used
recommended state: false
- if module | cycle is not used
module | parallax
default: false
recommended state: false
- if module | parallax is not used
recommended state: false
- if module | parallax is not used
module | tubeplayer
default: false
recommended state: false
- if module | tubeplayer is not used
recommended state: false
- if module | tubeplayer is not used
OTHER MODULES AND TOOLS ?
JMPv3.0 has many other modules and tools that mostly use the standard jQuery and jQuery CoreUI library components
These standard components are also used and deployed by WB itself if required
This LIST B displays which module + tool uses which component, these JMPv3.0 modules + tools can not be disabled
JMPv3.0 has many other modules and tools that mostly use the standard jQuery and jQuery CoreUI library components
These standard components are also used and deployed by WB itself if required
This LIST B displays which module + tool uses which component, these JMPv3.0 modules + tools can not be disabled
module | OnLoad
JMP MODULES + TOOLS:
SCRIPT USED:
standard jQuery library
module | OnEvent
standard jQuery library
module | CoreUI draggable
standard jQuery UI component
module | CoreUI droppable
standard jQuery UI component
standard jQuery UI component
module | CoreUI resizable
module | disable
standard jQuery library
module | appendTo
standard jQuery library
standard jQuery library
module | iframe
module | unordered list
standard jQuery library
standard jQuery library
easy tools | preblock
module | reposition
jQuery reposition
module | reposition can not be disabled
other JMPv3.0 components depend on it for a correct functioning
module | reposition can not be disabled
other JMPv3.0 components depend on it for a correct functioning
MUST I INCLUDE MULTIPLE INSTANCES OF jor_aniMateLIMITER ?
No, a single instance of jor_aniMateLIMITER per page should be used, no more
" jor_aniMateTEMPLATE can be used as many times per page as required " ...
But, jor_aniMateLIMITER should only be added to a page once , it affects all instances of jor_aniMateTEMPLATE on the page
Even more, JMPv3.0 will not allow jor_aniMateLIMITER to be included to a page more then once ...
If it detects more then a single LIMITER output, a window alert will display and prompt to remove excessive instances
The alert will read as ...
No, a single instance of jor_aniMateLIMITER per page should be used, no more
" jor_aniMateTEMPLATE can be used as many times per page as required " ...
But, jor_aniMateLIMITER should only be added to a page once , it affects all instances of jor_aniMateTEMPLATE on the page
Even more, JMPv3.0 will not allow jor_aniMateLIMITER to be included to a page more then once ...
If it detects more then a single LIMITER output, a window alert will display and prompt to remove excessive instances
The alert will read as ...
easy tools | page load
standard jQuery library
JMPv3.0 OPTIMIZE - NEW EXTENSION jor_aniMateLIMITER - ?
jor_aniMAteMASTERPACKv3.0 is a powerful tool with many many functions
If a website is build around JMPv3.0 it is an optimized power pack with virtually limitless animation options in a single extension
But if we want to use JMPv3.0 as a single function extension it will load scripts that we don't plan or want to use
With JMPv3.0 build 5.2 it is now possible to disable individual modules and optimize JMPv3.0 to our requirement
JMPv3.0 now consists of 2 extensions - 01. jor_aniMateTEMPLATE and the new 02. jor_aniMateLIMITER
jor_aniMateLIMITER allows to modify individual JMPv3.0 modules by excluding - including script references to our page
Simply add a single instance of jor_aniMateLIMITER and enable or disable JMPv3.0 modules as required
jor_aniMAteMASTERPACKv3.0 is a powerful tool with many many functions
If a website is build around JMPv3.0 it is an optimized power pack with virtually limitless animation options in a single extension
But if we want to use JMPv3.0 as a single function extension it will load scripts that we don't plan or want to use
With JMPv3.0 build 5.2 it is now possible to disable individual modules and optimize JMPv3.0 to our requirement
JMPv3.0 now consists of 2 extensions - 01. jor_aniMateTEMPLATE and the new 02. jor_aniMateLIMITER
jor_aniMateLIMITER allows to modify individual JMPv3.0 modules by excluding - including script references to our page
Simply add a single instance of jor_aniMateLIMITER and enable or disable JMPv3.0 modules as required
The following LIST A displays the modules that can be disabled and shows recommendations as to when to disable
LIST A
LIST B
module | onscroll
jQuery onscroll + jQuery keyframes mod
module | onscroll can not be disabled
other JMPv3.0 components depend on it for a correct functioning
module | onscroll can not be disabled
other JMPv3.0 components depend on it for a correct functioning
module | scroll
jQuery scrollto + jQuery local scroll + additional
module | scroll can not be disabled
other JMPv3.0 components depend on it for a correct functioning
module | scroll can not be disabled
other JMPv3.0 components depend on it for a correct functioning
DO I NOW HAVE TO MAKE CHANGES TO jor_aniMateTEMPLATE ?
No, jor_aniMateTEMPLATE will function exactly the same as before JMPv3.0 build 5.2
The only change we have to make is the following ...
If any of the modules from the above LIST A is used in our project we simply need to add
a single instance of jor_aniMateLIMITER to our page
If we use jor_aniMateTEMPLATE in a project that does not use any of the modules from LIST A
then we do not have to include jor_aniMateLIMITER to the project at all , JMPv3.0 is instant optimized, instant JMPv3.0-Lite
All other modules and tools (=LIST B) will still function normal even without jor_aniMateLIMITER present
Only include jor_aniMateLIMITER to a page if any of the modules of LIST A is actually used
No, jor_aniMateTEMPLATE will function exactly the same as before JMPv3.0 build 5.2
The only change we have to make is the following ...
If any of the modules from the above LIST A is used in our project we simply need to add
a single instance of jor_aniMateLIMITER to our page
If we use jor_aniMateTEMPLATE in a project that does not use any of the modules from LIST A
then we do not have to include jor_aniMateLIMITER to the project at all , JMPv3.0 is instant optimized, instant JMPv3.0-Lite
All other modules and tools (=LIST B) will still function normal even without jor_aniMateLIMITER present
Only include jor_aniMateLIMITER to a page if any of the modules of LIST A is actually used
SCRIPT USED:
jQuery cycle
jQuery cycle tiles
jQuery cycle tiles
jQuery parallax
jQuery plaxify
jQuery plaxify
jQuery tubeplayer
FireFox 30.x
REMARK
Note that JMPv3.0 will not detect the amount of instances used in a project, but the amount of outputs to a page
What's the difference ?
Webbuilder automatically generates a single output if the code of multiple extensions is exactly the same
Let's look at this in a "practical" example by using jor_aniMateLIMITER ...
Say we add 2 instances of jor_aniMateLIMITER to a page and we don't change any of the properties, we just run the page
If we would now look at the code that is generated by Webbuilder we would see a single output of jor_aniMateLIMITER
Webbuilder treats both extensions as a single unit because the code of both instances is exactly the same
JMPv3.0 at this point will not display a window alert, it detects a single output, this scenario is not a problem!
Note that JMPv3.0 will not detect the amount of instances used in a project, but the amount of outputs to a page
What's the difference ?
Webbuilder automatically generates a single output if the code of multiple extensions is exactly the same
Let's look at this in a "practical" example by using jor_aniMateLIMITER ...
Say we add 2 instances of jor_aniMateLIMITER to a page and we don't change any of the properties, we just run the page
If we would now look at the code that is generated by Webbuilder we would see a single output of jor_aniMateLIMITER
Webbuilder treats both extensions as a single unit because the code of both instances is exactly the same
JMPv3.0 at this point will not display a window alert, it detects a single output, this scenario is not a problem!
If we now go back to our project and open one of the jor_aniMateLIMITER instances
We now change ie. the property module | nivo we set it to true, default is false we change it to true
We run the page again and again we look at the code that is generated by Webbuilder
We will now see 2 instances of jor_aniMateLIMITER written to our page because the code of both instances is now different
This is a problem cause we could easily create duplicate script references resulting in multiple request of the same script
This of course is not what we want, we want to optimize, not create additional needless http requests
JMPv3.0 at this point will display a window alert warning to comply and remove excessive instances!
We now change ie. the property module | nivo we set it to true, default is false we change it to true
We run the page again and again we look at the code that is generated by Webbuilder
We will now see 2 instances of jor_aniMateLIMITER written to our page because the code of both instances is now different
This is a problem cause we could easily create duplicate script references resulting in multiple request of the same script
This of course is not what we want, we want to optimize, not create additional needless http requests
JMPv3.0 at this point will display a window alert warning to comply and remove excessive instances!
This of course is all theoretical cause the rule of use is simple - ONLY One instance of jor_aniMateLIMITER per page
Still good to know JMPv3.0 is keeping track for us, a mistake is easy to make ...
Still good to know JMPv3.0 is keeping track for us, a mistake is easy to make ...
SUMMARY
Only Include a single instance of jor_aniMateLIMITER if any of the modules of LIST A is used by jor_aniMateTEMPLATE
Only Include a single instance of jor_aniMateLIMITER if any of the modules of LIST A is used by jor_aniMateTEMPLATE
INSTALL NOTES
Always install both extensions by the same build ... For example ...
Do not install jor_aniMateTEMPLATE from JMPv3.0 build 5.1 together with jor_aniMateLIMITER from JMPv3.0 build 5.2
JMPv3.0 will also in this matter display a window alert warning to comply if different builds are detected!
Always install both extensions by the same build ... For example ...
Do not install jor_aniMateTEMPLATE from JMPv3.0 build 5.1 together with jor_aniMateLIMITER from JMPv3.0 build 5.2
JMPv3.0 will also in this matter display a window alert warning to comply if different builds are detected!
A window alert will also display and prompt a warning if jor_aniMateLIMITER is required
The alert will read as ...
FireFox 30.x
b5.3
No Quick Link
No Quick Link
No Quick Link
No Quick Link
No Quick Link
NEW IN BUILD 5.6
01. REMOVED
the following modules were removed from JMPv3.0 being less suitable for RWD/modern web design
• module | nivo
• module | roundabout
• module | swf
02. CHANGED
the previous included animate.css library has been removed
the animates.css library however is still available in a new method - more info see here
GOTO FULL UPDATE HISTORY
01. REMOVED
the following modules were removed from JMPv3.0 being less suitable for RWD/modern web design
• module | nivo
• module | roundabout
• module | swf
02. CHANGED
the previous included animate.css library has been removed
the animates.css library however is still available in a new method - more info see here
GOTO FULL UPDATE HISTORY
5
b5.2