THE IMPORT
Q: How do I get the jorAMP_PROJECTS into my project ?
A:
Inside the jor_aniMateMASTERPACKv3.0 .rar is a jorAMP_PROJECTS folder
Inside this jorAMP_PROJECTS folder all jorAMP_PROJECTS are presented as regular Webbuilder projects (.wbs)
01. select the project of your interest, open the project
02. copy-paste the TEMPLATE from the first page into your project
03. close the jorAMP_PROJECT Webbuilder project
04. done! - start editing the TEMPLATE settings
Q: How do I get the jorAMP_PROJECTS into my project ?
A:
Inside the jor_aniMateMASTERPACKv3.0 .rar is a jorAMP_PROJECTS folder
Inside this jorAMP_PROJECTS folder all jorAMP_PROJECTS are presented as regular Webbuilder projects (.wbs)
01. select the project of your interest, open the project
02. copy-paste the TEMPLATE from the first page into your project
03. close the jorAMP_PROJECT Webbuilder project
04. done! - start editing the TEMPLATE settings
jorAMP_PROJECTS are my own custom coded templates for jor_aniMateMASTERPACKv3.0
The only part of jor_aniMateTEMPLATE that is used in the jorAMP_PROJECTS is the upper part , the TEMPLATE SET settings
The only part of jor_aniMateTEMPLATE that is used in the jorAMP_PROJECTS is the upper part , the TEMPLATE SET settings
NOT USED
only the upper part
TEMPLATE SET
is used
TEMPLATE SET
is used
THE PROBLEM
jor_aniMateMASTERPACKv3.0 consists of 15+ modules, which are in essence well over 25+ extensions packed into one extension
All of these modules can interact with each other, and by custom coding, they can become a whole new extension in itself ...
But an extension needs an interface for the user to interact with that extension ... hence - The Problem !
Each extension requires it's own unique interface, it's own unique set of input properties
But here only one extension ... jor_aniMateTEMPLATE , is used to create numerous extensions
It is impossible to anticipate which inputs will be required ...
THE TEMPLATE SET SOLUTION
The TEMPLATE SET solution, - In the TEMPLATE SET input , each entry has 8 predefined inputs instead ...
jor_aniMateMASTERPACKv3.0 consists of 15+ modules, which are in essence well over 25+ extensions packed into one extension
All of these modules can interact with each other, and by custom coding, they can become a whole new extension in itself ...
But an extension needs an interface for the user to interact with that extension ... hence - The Problem !
Each extension requires it's own unique interface, it's own unique set of input properties
But here only one extension ... jor_aniMateTEMPLATE , is used to create numerous extensions
It is impossible to anticipate which inputs will be required ...
THE TEMPLATE SET SOLUTION
The TEMPLATE SET solution, - In the TEMPLATE SET input , each entry has 8 predefined inputs instead ...
So ... instead of having 1entry = 1 input as a normal extension would have, here there are always 8 inputs 1 entry = 8 inputs
Q: But, when is which input used ?
A: That depends on what the script demands
When and What do I input ?
The TEMPLATE SET provides 4 information entries on When to input What ...
Q: But, when is which input used ?
A: That depends on what the script demands
When and What do I input ?
The TEMPLATE SET provides 4 information entries on When to input What ...
1 entry is 8 predefined inputs
NOT USED
NOT USED
used input in this example
__________________________________________________________________________
more info on template settings see here Overview Template Set User
more info on template settings see here Overview Template Set User
NOT USED
The FUNCTION entry is the purpose of the function, the entry for example could be font color
The 2nd entry provides a quick visual reminder of which of the 8 inputs actually is used
The FUNCTION INFO (READ HERE) property provides detailed information on when to input what
The 4th entry again provides a quick visual reminder of which of the 8 inputs actually is used
THE LOGIC
All in all it isn't that much different from a regular extension input
if the FUNCTION is font family - the input is INPUT | font
if the FUNCTION is an easing effect - the input is INPUT | easing
etc etc
AN EXAMPLE:
All in all it isn't that much different from a regular extension input
if the FUNCTION is font family - the input is INPUT | font
if the FUNCTION is an easing effect - the input is INPUT | easing
etc etc
AN EXAMPLE:
below this line should not
be changed by user input
be changed by user input
INTRODUCTION - jorAMP_PROJECTS
EXPLAIN ?
b5.6