On the other hand, Node.js's connection to Max is a little sparse. The web interface is potentially extremely rich - browsers can render 2D and 3D graphics and support responsive and adaptable user interfaces - so you may be led towards the browser as your natural environment for interface building instead of (or in addition to) Max itself, if you have the coding skills. (The browser could be on the same machine that's running Max, or elsewhere, for example on a phone or tablet.) In the screen, Node.js is actually running a local web server, allowing audio files to be uploaded by a web browser for Max to play back. Once the process is running, it can read and write files and run network services. To get a Node.js process that you can talk to, create a 'node.script' object with an argument naming a JavaScript file to load, and then send it a 'script start' message to launch the Node.js process. Node.js within Max offers a dynamic Web interface for scheduling calendar-based events. And Node.js itself is totally open-source.
Node.js is built into Max itself, so there are no hassles finding and downloading a separate runtime, as is necessary with Java. And you might also have several Node.js processes running at once (which is actually a good thing: they won't interfere with one another). In practice this distinction is largely irrelevant, but it does mean that you have to launch a Node.js process before you can use it (although this can be automated). Whereas the Java runtime loads as part of the Max process, Node.js runs as a separate process. It's generally used for building web services or running utility programs, but thanks to Node for Max, it can now operate as part of Max itself. Node.js is a JavaScript runtime: a program that runs JavaScript outside the context of the web browser.
0 kommentar(er)
