-
Notifications
You must be signed in to change notification settings - Fork 74
The export problem #319
Comments
Hello, I have the same problem in Linux, with Google Chrome and Chromium browsers. Does anyone know how to fix this? |
I'm afraid the filesystem APIs in Chrome changed since we wrote this and there's no one actively working on the code to fix it. It is likely that the fs.js needs to be rewritten to use more modern APIs. I think it was some time around Chrome 49 when some APIs disappeared and it stopped working. So the only way it would work is to use a very old browser, which is not recommended. I'm sorry about this and perhaps I'll feel bad enough about it sometime to try to work on it. :) But I don't really work with any of this stuff anymore so I've forgotten a lot. It looks like jQuery Mobile hasn't changed since 1.4.5 release in 2014. So it's a shame we don't update this to at least work with that final version in perpetuity. |
Hello Geoff, Thanks for your quick response. Bummer, this doesn't work. It's a great way to build quick and simple GUIs for the ESP8266. Do you know if there is anything else that compares? The other online builders aren't as friendly as RIB. Best Regards, |
You might know more about RIB than me at the moment since I haven't touched it in a long time. But one idea that strikes me is that it is possible to select and copy the text from the "Code" tab in RIB and paste it into a file. While that's a little annoying, if you really find RIB to be your best option that might get you by? I'm afraid I don't know what other options are out there these days. |
Hi,
can somebody helps me to solve the export issue. I've tried the Preview-1 and Preview-2 versions but with both of them I can't export my project. The chrome was lunched with the --enable-file-cookies --allow-file-access-from-files attributes but unfortunately nothing changes. I'm running the RIB on my windows 8.1 OS and localhost based on apache. Even the online version doesn't export. Is it comes from my computer settings or it is some global issue?
The text was updated successfully, but these errors were encountered: