more or less yes, there is also difference in display driver, there are three - one mine in javascript+inline c, two made by jeffmer - lcd_spi_unbuf -unbuffered driver - sends data to screen directly as it is drawn (a bit slow) - this is also part of my build but unused/untested. Later jeffmer also made buffered driver similar to mine. both of his drivers are part of espruino binary. so you need to check how the js code draws to screen - buffered driver needs to call g.flip() when you want to push currently modified area to screen.
also another difference is where the storage is - internal nrf52 flash (about 600kb) or spi flash 8MB or both. my latest build on github is for internal flash but no problem to build other variants (i just don't use them much, 600kb was enough for me)
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.
more or less yes, there is also difference in display driver, there are three - one mine in javascript+inline c, two made by jeffmer - lcd_spi_unbuf -unbuffered driver - sends data to screen directly as it is drawn (a bit slow) - this is also part of my build but unused/untested. Later jeffmer also made buffered driver similar to mine. both of his drivers are part of espruino binary. so you need to check how the js code draws to screen - buffered driver needs to call
g.flip()
when you want to push currently modified area to screen.also another difference is where the storage is - internal nrf52 flash (about 600kb) or spi flash 8MB or both. my latest build on github is for internal flash but no problem to build other variants (i just don't use them much, 600kb was enough for me)