Live Coding Sessions
The four sessions work up to a mini-project in the last 40 minutes of session 4.
The links for session 4 are now included below. There are session links for TwitchTV and YouTube. In session 3 I examine how to rasterize arbitrary WL expressions that are neither Images nor Graphics. We also go over how to control ImageSize and AspectRatio to accommodate HTML requirements (or vis-a-versa).
Along with Andreas Lauschke and Alan Calvitti I've undertaken the following 'live coding' sessions along the line of APIs where WL is the computational end point. I will not walk-through the JavaScript environment setup (unless there is enough demand). All the needed bits and pieces are readily available with very good documentation.
TwitchTV: - Session 1 - Session 2 - Session 3 - Session 4 YouTube: - Session 1 - Session 2 - Session 3 - Session 4
I frequently say front-end and back-end environments overlook (or under appreciate) the computation-side. However, with a few development requirements the quant-side can deliver to the front-end folks exactly what they need and reduce the amount of processing logic in the front-end. It also conforms to the development team and code writing philosophy of separation of concerns and duties. This opens the door to more modular teams and code with easy to understand handshakes between components and teams.
All the Notebooks, JavaScript code, YouTube and TwitchTV links are in my GitHub repository.
We start with the most simple use of APIFunction[
] I can think of then step into use cases that confront simple issues, which if not understood upfront, can cause delays and frustration for one of more team members. We make API calls to external resources from inside APIFunction[
] and get and put data from and to Wolfram Cloud. We look at producing and returning exactly the structure of JSON needed by the JavaScript (front-end).
This is followed with a look at using APIFunction[
] with NodeJS (backend) building up to dealing with the dreaded CORS issues and look into some security issues.
Lastly, we will look at a few use cases for integrating to AWS resources.
I will update this post and my GitHub as we proceed.
