I wanted to let you know about a tool I’ve been creating. I got a bit fed up with not being able to use local libraries since I’ve been working for multiple companies with the Electric Imp platform. Its still pretty early but the tools is pretty useful right now.
Here is the project page:
You’ll have to build it yourself, and I’ll be working on documentation after my current workload dies down.
Here is a list of features that Wrench allows though:
Run Squirrel Files locally - wrench run <file_name> runs any file locally
Library Support - Create a master .nut file from multiple different .nut files.
Basic Build API support - wrench build; wrench upload -r; wrench device log <device_id> does the same thing as the web ide. These may get combined later on to a new command. You can also list devices, models, and assign devices to a model.
Basic Testing Support - wrench test will recursively look for .test.nut files and generate a file and run it locally. More support for testing will be coming. Including later on support for server.sleep and correct nv table emulation.
I’m going to attempt to get more support from electric imp. I’d really love to see good code reuse and tools. Later on I’d like to incorporate a linter, and possibly dynamic #defines that allow you to mutate your code based on EI model, but those will likely be much later on. Currently wrench lets you decompose your projects down and use ides that you are more accustom to.
I’m always willing to look and merge pull requests. Wrench is currently writen in go, and should be very easy later on to run multiple squirrel vms inside. Allowing you to test both agent and device locally, but I’ll need help to get to that point. The best way to contact me right now is probably through email until the community grows and we setup a irc or forum.
I’ll try to get a tutorial/starting project up and going at some point as well.
Sean Sill firstname.lastname@example.org