I'd look at the existing ESP8266 one (look under 'reference') and copy that - same functions as the CC3000's WLAN object but it uses callbacks.
I think in this case it's probably worth breaking CC3000 backwards compatibility in order to bring that inline with the callback-based approach, and the same could be done for WIZnet too.
I'd say maybe leave ESP8266-specific stuff in the root object? it won't hurt if nobody calls it :)
So what do we think? WiFi, WLAN, or network? net is used for TCPIP already.
I'd say maybe something non-wifi-specific would be good, given there's also ethernet which exposes the same getIP/setIP.
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.
I'd look at the existing ESP8266 one (look under 'reference') and copy that - same functions as the CC3000's WLAN object but it uses callbacks.
I think in this case it's probably worth breaking CC3000 backwards compatibility in order to bring that inline with the callback-based approach, and the same could be done for WIZnet too.
I'd say maybe leave ESP8266-specific stuff in the root object? it won't hurt if nobody calls it :)
So what do we think?
WiFi
,WLAN
, ornetwork
?net
is used for TCPIP already.I'd say maybe something non-wifi-specific would be good, given there's also ethernet which exposes the same getIP/setIP.