John: It seems with my Asus Chromebox not connected to any networks (Ethernet or wireless) one has to restart the computer disconnected to a network to force CloudT to run offline in the Chrome browser. But work it does. This is an older chromebox at this point so few things work offline anyway, but CloudT being in browser seems to, just gotta slap it on the side like 60's black and white TV (my parents used me as the "remote control")
Saving CloudT to the home screen on my Moto G5 works in airplane mode too. Regards D. Szasz On Sun, Mar 31, 2019 at 7:16 PM David Szasz <[email protected]> wrote: > Yep, just got back from grocery shopping at Kroger's > > I'll try the save to home screen for fix for a more aggressive cache. That > being said I'd like to build "Mr. T" a raspi or sbc laptop or tablet with > CloudT or VirtualT with GWBasic or PCBasic thrown in for good measure. > > I am such a 80's retro geek > Thanks > D. Szasz > > On Sun, Mar 31, 2019, 4:04 PM John R. Hogerhuis <[email protected]> wrote: > >> >> >> On Sun, Mar 31, 2019 at 1:10 PM David Szasz <[email protected]> wrote: >> >>> This morning I was pondering if one could run CloudT Offline? Possibly >>> using something called "NodeJS", that is to run javascript offline, maybe >>> on a raspberry pi? >>> >>> Just a thought.... any other ways of running javascript and CloutT >>> offline? >>> >>> >> Hmm, well I just tried this in offline mode (network disconnected) on my >> laptop in Chrome and it didn't work. I thought it did. >> >> But on my Moto G6 Play phone, CloudT stored as an home screen app loads >> properly in Airplane mode. So saving as a home screen app caches more >> aggressively, I guess. >> >> I need to add a appcache manifest, or the newer standard, a service >> worker and it cache on Chrome desktop too. >> >> As to Node.JS, Node.JS is a combination Javascript runtime and package >> management system. None of the CloudT javascript code runs in the server, >> just in the browser, so it wouldn't benefit from the Node.JS javascript >> engine. >> >> That said, Node.JS can run some simple webservers. CloudT at this point >> is a static html + javascript site, which means it has no server side code. >> So it would run locally under any web server and maybe even from a local >> directory without trouble. But there are many webservers that will run on a >> Pi. The benefit of Node.JS would be if you want to access some hardware. >> Say a physical serial port. It could be exposed to CloudT from Node.js >> "SerialPort" library as a Websocket to the front end running as a web app. >> >> But if I get the browser caching set up (thought it was!), I think the >> browser would end up being the simplest offline solution. Just browse >> Cloudt once with your browser, and it's effectively "installed". >> >> -- John. >> >
