leopard-js
Projects that don't seem to translate
I tried with https://scratch.mit.edu/projects/312769512/. I get a black screen at https://leopardjs.now.sh/?id=312769512
Even https://scratch.mit.edu/projects/401788041/ doesn't work (or doesn't work as expected). I can see some green moving the mouse around, but not what is visible in Scratch
I tried with https://scratch.mit.edu/projects/312769512/. I get a black screen at https://leopardjs.now.sh/?id=312769512
Same with https://scratch.mit.edu/projects/115364400
@PullJosh Maybe you should create a project board that contains a list of projects that don't properly translate. This would help keep down clutter in this issue.
This is like #79 but with many, many more links! ✨
I'm not going to be able to address all of these individually yet, but rest assured that I'm going to be working on compatibility across a wide range of Scratch projects going forward, including specific investigations to many individual projects to try to diagnose any compatibility errors. We've already made a lot of progress since 2020 (including a significant amount of work in the last 2-3 weeks), so many of these links may be partially or entirely working now. It's definitely worth checking these out again later, so thanks for the extensive list!
Here you are the revised list:
Translation going on forever (both via link and when uploading):
- https://scratch.mit.edu/projects/312769512/
- https://scratch.mit.edu/projects/414675446/
- https://scratch.mit.edu/projects/443365331/
Not working as expected:
- https://scratch.mit.edu/projects/401788041/ (original: press space and move the mouse around to see 3D landscape; leopard: press space and see black screen with cross at the center, no change when moving mouse around)
- https://scratch.mit.edu/projects/434793972/ (original: progress variable goes -slowly- up to 100% then it shows a rendered scene line by line; leopard: every time I click the "green flag" button the progress variable goes up to 4/9/12/etc% then it "stops" for e very long time, then it goes up again a little bit, then... I don't know, it seems that it never gets to 100%)
Error converting project via link (and translation going on forever when uploading):
- https://scratch.mit.edu/projects/115364400/
- https://scratch.mit.edu/projects/395011295/
Error when converting project (both via link and when uploading):
- https://scratch.mit.edu/projects/147259154/
Error when converting project via link (it works when uploading):
- https://scratch.mit.edu/projects/112008562/
In general: is it possible to get an alert when the leopard project is updated? So that I can recheck my list of problematic projects. Thanks in advance
Thanks! If you aren't following the whole repository, you can click "Watch" near the top of the page and choose "Custom", then click the checkbox for "Releases". When we release new versions of Leopard they will show up like on the page here: https://github.com/leopard-js/leopard/releases
There is some delay between releasing a version of Leopard on GitHub and actually pushing it to the website, though (usually a couple days or so). We don't have automatic deployment prepared yet (we're discussing that in #172).
You can run the latest version of Leopard locally using my project sb-edit-playground, which converts sb3 to Leopard in the command line. See my quick start guide here: https://github.com/leopard-js/sb-edit/issues/67#issuecomment-1464082816
(To get the latest version of Leopard and sb-edit when they release, just cd into sb-edit-playground and run npm install leopard@latest and npm install sb-edit@latest.)
There is some delay between releasing a version of Leopard on GitHub and actually pushing it to the website, though (usually a couple days or so). We don't have automatic deployment prepared yet
How do I know if the website is aligned to the latest version?
I checked in with PullJosh about this a few days ago. The website is always up to date with the Leopard library, which is the runtime code (for example if there are bugs with the project renderer, as soon as we make a fix and it is part of a release in the Releases page, projects should receive the fix basically immediately). However, the project generation code, sb-edit, does not get pushed to the Leopard website automatically. That means if there is an error translating a project, and we release a fix, it needs to be pushed to the website manually.
I don't believe there's any way to see the version of sb-edit which is present just by visiting the website. (I'll file a bug since this is useful information!) Currently you can see what version is on the website by viewing the website's package.json file. A recent commit in that list should show something like "Upgrade to sb-edit 0.13.12" etc. If this matches the version in sb-edit's package.json (right at the top), then the Leopard website should be up to date.