Indeed. Once we have JS which 'does a similar thing' to answer file (or any other OS related piece of syntax) - hooking it up to that command is relatively straightforward.
The hard part is writing the JavaScript implementations of the various OS services we are so used to using directly in LC. It is important to remember that browsers give no direct access to OS APIs, they are sandboxed and attempt to mitigate security issues as much as they can. The only system type functionality you get is that exposed by supported JS APIs a given browser has. Mark. Sent from my iPhone > On 24 Nov 2016, at 18:41, Roger Eller <roger.e.el...@sealedair.com> wrote: > > File picker should not have to be built in another language, in my > opinion. Ask or Answer file SHOULD just work. Again, my opinion. This is > LiveCode after all. > > ~Roger > >> On Nov 24, 2016 10:49 AM, "Todd Fabacher" <tfabac...@gmail.com> wrote: >> >> Hello LiveCode community, >> >> At Digital Pomegranate we are very excited about the update to LiveCode >> HTML5. We already have several projects that we plan on using the platform >> for. Since our LiveCode team has only a little experience in JavaScript, we >> are thinking of creating a LiveCode.js. This will be both a LC substack >> that wraps a Javascript function library which would be in a file named >> LiveCode.js. >> >> Our thinking is it would have 5+ core functionalities that woul dbe shared >> by most HTML5 apps. I think this would be a great community project and >> help people who may not be so familiar with Javascript and can stay focused >> on LiceCode. >> >> Communications >> tsNet has given LiveCode async server communications, the good news is >> Javascript has had this functionality for quite some time. We would need a >> simple wrapper of the XMLHttpRequest functionality in LiveCode.js, so it >> seems seamless in Livecode. >> >> I know LC can call the browser's javascript, but can the JS do a callback >> to LiveCode? It would be great if we could do sockets in JS and create a >> two way communications system. >> >> RestAPI services >> I have seen recent notes about using revIgniter as a REST server, and there >> are many other options available. We use mostly WP and the WP RestAPI. >> >> Remote Storage >> Mark's LiveCloud is a great option and there are several different options. >> As I said, we mostly use WP, but we also use Node.js w/ mongodb. The >> LiveCode.js will just need a simple way of taking XML. JSON or an encoded >> array and sending it to the remote storage of choice and returning the >> values. >> >> Local Storage >> The ability to create and use a local DB within the local browser. My >> understanding is that LC HTML5 will not because to utilize the database >> library, so we will have to use Javascript localStorage. We just need to >> create a controller that will connect LC to create, read and write to the >> local DB. Javascript even has a way to store the DB and can be accessed for >> the next session. >> >> http://www.w3schools.com/html/html5_webstorage.asp >> >> File Picker & Uploaded >> Not use how to do this in HTML5, but we will need a way to select a file >> and upload it to a server. We could use an HTML+JS dialog box to do it. >> >> Best, >> >> Todd >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
