Great to hear! As an add-on for informational purposes only, I'll throw this out there:
Lets assume you want to include the following javascript function on a few different forms:
function sayHello(name) {
// Fantastic aint it
console.log('Hello, ' + name);
}
Using the Macro/Formatter method I mentioned above, you could put this function in a Macro in two ways. The first is directly using <script> blocks:
Macro:
<?xml version="1.0" encoding="utf-8" ?>
<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">
<script>
function sayHello(name) {
console.log('Hello, ' + name);
}
</script>
</j:jelly>
The other method, as you have discovered, is using a NON-GLOBAL UI Script. Global UI scripts are included on every page and usually adds unnecessary overhead. Using the macro in conjunction with a non-global UI Script and a formatter, you can achieve the same exact thing. So the following set of scripts would be functionally identical to the above:
UI Script
name: SayHello
global: false
function sayHello(name) {
console.log('Hello, ' + name);
}
Macro:
<?xml version="1.0" encoding="utf-8" ?>
<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">
<script>
</j:jelly>
The primary difference between the two is that the first loads a single resource - the page with content generated by the Macro. The second loads two resources - the page with content generated by the Macro and the UI Script file loaded separately.
