Problem Running Sugarizer Lite in Chrome

[BlueJay89]

I've been having issues getting sugarizer lite to run in chrome.

OS: Windows 10 Home edition
Chrome Versions: Version 81.0.4044.113 (Official Build) (64-bit)

Attempts to follow the standard command prompt as instructed in the README file did not work.

"C:\Program Files (x86)\Google\Applications\Chrome\chrome.exe" --allow-file-access-from-files opens chrome but does not open sugarizer

"C:\Program Files (x86)\Google\Applications\Chrome\chrome.exe" --allow-file-access-from-files index.html opens chrome with search results for index.html

Opening a new chrome window and using ctr-o to find index.html seems to open sugarizer, but then the screen becomes grayed out and there is no functionality. Once I have this 'grayed out' version of sugarizer open I select right-click -> inspect and find errors in the execution of the html code.

Problem is I know nothing about html so I can't trouble shoot this. Can anyone help?

So, I'm running Windows 10 Pro but with the same Chrome version.

I suspect that what might be happening is that while trying to get three things going at once:

1. Load the browser (The long path starting from C:)
2. Set the browser to allow loading JavaScript code from local files
3. Load the Sugarizer index.html file

you might have changed one item without needing to, and changed a necessary thing to something that didn't in fact work.

Often enough when I am working on something that has a lot of unfamiliar pieces I find changing one thing was what I needed to do, but on the way to figuring that out I changed something unrelated.

Please be sure that just running 1 and 2 together without index.html on the line runs. Only then load the file with Ctrl-o

If it still doesn't work, please try clearing your Chrome history:

https://support.google.com/chrome/answer/95589

and bypassing your cache:

https://en.wikipedia.org/wiki/Wikipedia:Bypass_your_cache

also @jrtechs recommended this sort of approach:

C:\Users\hfoss.learner\AppData\Local\Google\Chrome\Application\chrome.exe --disable-web-security --disable-gpu --user-data-dir=~/chromeTemp

so far as I can tell, --allow-file-access-from-files and -disable-web-security should both override the restriction in the cross-origin request policy that excludes file:// URLs but if one works and the other doesn't so be it.

ok, no luck in my hands with just --disable-web-security

I can only get it to work with --allow-file-access-from-files

I can get it to start navigation though it I pass a URL like file://C:\ to the end of the command line though, eliminating the need to use Ctrl-o

[zsd7200]

Unsure if you ever resolved your issue, but I just submitted a PR with a file that should make opening Sugarizer much easier for you. Hope this solution works out for you!

[jrtechs]

@BlueJay89 are you still having this issue? Also clearing the cache of my web browser helped me fix one issue I was having.

[BlueJay89]

I still cannot get this issue resolved on my personal computer. I attempted to recreate the issue on my wife's computer, but it seemed to work without a problem. The difference I can see is that my wife is running Windows Pro and I am running Windows Home. The version of chrome is the same.

[deejoe]

On Wed, Apr 29, 2020 at 07:48:54AM -0700, BlueJay89 wrote: I still cannot get this issue resolved on my personal computer. I attempted to recreate the issue on my wife's computer, but it seemed to work without a problem. The difference I can see is that my wife is running Windows Pro and I am running Windows Home. The version of chrome is the same.

OK, good to know. I mentioned in IRC on Monday, I think, that I had tried to use the VS Codium Live Server plugin to try to run this, too, with no luck. My other idea is to see if something got corrupted in the local copy of the sugarizer-lite code, or to try running Chrome on some other code base as a sort of experimental control that could help us bisect the problem on that front. To that end, I've put together a relatively small-and simple Javascript project using p5js (p5js.org). I'm not insisting that we figure this out, but I think this has been vexatiously frustrating for several of us. So, if you want to try to continue working on it, you could clone: https://github.com/deejoe/p5js-playground and then try to run the chrome browser the same way, opening (via Ctrl-o) the index.html file in that directory. It should do two things: draw a black circle on a white background in the main browser window. Send the message "Hello, World!" to the console, visible via Ctrl-Shift-i If this is a limitation of the OS version, I would expect the same error. If it is some problem interacting with the particular code, I would expect to see the circle and console log message.

At the very least, for future use and reference, if you haven't had a chance to get into web programming before, if this works for you it's a decent way to wrap this up.

p5js provides, in my opinion, a smaller, cleaner entry point than Sugarizer and has a pretty active and supportive community especially for newcomers.

It's been used recently for IGME-101. I first encountered it and became familiar with it through several faculty teaching that course.

Once again, the Github interface has noted the cross-reference, but to make this explicit for the sake of email notifications in particular, I posted links to p5js over in

#5 (comment)