1) 2 modules is probably better... I don't see any real reason why not - people may just want Date and not clock, and then they won't want the extra memory used up...
2) You should be able to do:
var x =require("http://foo/bar.js");
If you have a webserver on your PC, you should be able to load from localhost... @JumJum's made a 'project' extension for the Web IDE that allows local files, but I've yet to integrate it properly I'm afraid.
4) I'm afraid not. It's an interesting thought actually. To date, most of the modules have been interfacing to hardware so tests haven't been an issue. Perhaps we should start a tests folder. If tests were arranged like: https://github.com/espruino/Espruino/tree/master/tests then the existing Espruino executable could test them...
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
1) 2 modules is probably better... I don't see any real reason why not - people may just want Date and not clock, and then they won't want the extra memory used up...
2) You should be able to do:
If you have a webserver on your PC, you should be able to load from localhost... @JumJum's made a 'project' extension for the Web IDE that allows local files, but I've yet to integrate it properly I'm afraid.
3) I'd try
https://github.com/espruino/EspruinoDocs/tree/master/modules
4) I'm afraid not. It's an interesting thought actually. To date, most of the modules have been interfacing to hardware so tests haven't been an issue. Perhaps we should start a tests folder. If tests were arranged like: https://github.com/espruino/Espruino/tree/master/tests then the existing Espruino executable could test them...