http://w3schools.com/ has js tutorials. Js is a language, and it always runs in a browser the way it is supposed to - nothing special about SL. You just add it to SL when you need more programming power than SL's triggers provide.
I'm also wrapping examples into a book I'm writing after meeting so many people who don't necessarily want to be programmers but want to maximize their Storyline capabilities.
I'm still of the opinion that course developers should still probably learn something about JavaScript if they are going to use it. The person who says "oh, I can swim. I've watched other people do it and I should be able to just copy and paste their movements..." is the one who is destined to drown.
I'm of the BARE school of thought. Borrow and reuse everything.
Although to Owen's point, you can't reuse it if you don't have at least some understanding. But borrowing and working through is a method of increasing understanding, too.
I agree. There are three "swim lanes" for me that stand out: thinking like a programmer (this has nothing to do with coding in a language but more like moving from page-content to systems thinking), coding (or at least copy-pasting, which is the implementation of thinking like a programmer), and finally troubleshooting (which itself is one of the most universal skill you can apply to anywhere else). You can start simple and expand both in depth and surface how much you need but you can't just take one of these and jump into the deep ocean...
7 Replies
I don't know about Books but here is some Getting Started info and examples.
http://w3schools.com/ has js tutorials. Js is a language, and it always runs in a browser the way it is supposed to - nothing special about SL. You just add it to SL when you need more programming power than SL's triggers provide.
Hi Anna!
You'll find various examples on my blog on using JavaScript and Storyline. https://www.rabbitoreg.com/?s=javascript
I'm also wrapping examples into a book I'm writing after meeting so many people who don't necessarily want to be programmers but want to maximize their Storyline capabilities.
I'm still of the opinion that course developers should still probably learn something about JavaScript if they are going to use it. The person who says "oh, I can swim. I've watched other people do it and I should be able to just copy and paste their movements..." is the one who is destined to drown.
I'm of the BARE school of thought. Borrow and reuse everything.
Although to Owen's point, you can't reuse it if you don't have at least some understanding. But borrowing and working through is a method of increasing understanding, too.
That is actually how I learned. :-)
I agree. There are three "swim lanes" for me that stand out: thinking like a programmer (this has nothing to do with coding in a language but more like moving from page-content to systems thinking), coding (or at least copy-pasting, which is the implementation of thinking like a programmer), and finally troubleshooting (which itself is one of the most universal skill you can apply to anywhere else). You can start simple and expand both in depth and surface how much you need but you can't just take one of these and jump into the deep ocean...
This discussion is closed. You can start a new discussion or contact Articulate Support.