3. RE: Javascript $.getScript inconsistencies

Hi Dan, thanks for all the great work in unlocking js for the community, if it wasn't for that I'd have to say "no can do" far too often, and now each time its maybe and then yes.

How do you mean don't place the js in a code page, that's the ultimate location to place it in though isn't it? My workflow now is to download a page locally, insert the js inline and then work on it until its good and then place it in a code page. Still the ability to use the developer tools on live code would be helpful. Do you know why QB isn't opening this up more, I can understand that they don't want to support it which makes sense but js vastly enhances QB's capabilities. Still, pretty happy with your solution!

4. RE: Javascript $.getScript inconsistencies

>How do you mean don't place the js in a code page, that's the ultimate location to place it in though isn't it?

Ultimately you would place your code into a code page. However, it is faster to just paste code into the console during development while refining and debugging your code. There are many benefits to working in the console because you can use all the development tools to debug, inspect, override..

>Do you know why QB isn't opening this up more, I can understand that they don't want to support it which makes sense but js vastly enhances QB's capabilities.

I can't speak for QB's motivations. With regard to extra support, using JavaScript with QuickBase should actually lessen the support because the JavaScript ecosystem provides an enormous tools, utilities and libraries that is supported by the browser manufactures, framework and library authors.