Either way, you will need an Electric Imp account to proceed.
Since this Builder tutorial doesn’t require the use of impt, you can just continue here if you prefer.
If you haven’t yet explored impt, we suggest you do so using our introductory tutorial.
Loops installbuilder code#
For example, having generated your application code using Builder, you can use impt to upload the code to the impCloud and then to devices and agents. This tutorial will introduce you to Builder’s core functionality and show you how this can be achieved.īuilder really comes into its own when it’s paired with impt, Electric Imp’s tool for interacting with impCentral at the command line. It can generate a single source code file from a number of component files, and even perform logic during the generation process that affects the code it outputs. So how can you combine their contents into the agent code and device code blocks that impCentral expects? You can use Builder, Electric Imp’s powerful source code preprocessor. ImpCentral can’t help you manage all those files. For example, you might want to maintain separate files for code that’s unique to the application, for code that is the same on both the agent and the device, for code that is shared by a number of projects, and for non-Squirrel code that needs to be incorporated into the application, such as the HTML and JavaScript that define a web page served by the agent. ImpCentral is a great tool for straightforward projects, but you may soon feel the need to organize your device and agent code in more sophisticated ways. Electric Imp’s online IDE, impCentral™, gives you a means to enter and edit both of these closely connected programs alongside each other. The Electric Imp application architecture centers on two primary units of code: one which runs on the device and another which runs on the device’s cloud-based partner, called its agent.
0 kommentar(er)
