Lyxal opened PR #353 (Vyxal/Vyxal) (Vyxal:fix-304-and-352 → Vyxal:main): Make the stack pad with 0s if no input offline, and fix an issue with set operators
chunkybanana merged PR #353 (Vyxal/Vyxal) (Vyxal:fix-304-and-352 → Vyxal:main): Make the stack pad with 0s if no input offline, and fix an issue with set operators
1) It took my browser a loooong time to load gitcdn.xyz, and I don't think a dependency that takes minutes to load is a good idea. 2) Even after successfully loading gitcdn.xyz and Ctrl-F5ing, I still have white boxes.
I'm on Windows 10; problem occurs in both Firefox and Chrome.
The great service RawGit was already mentioned, but I'll throw another into the ring: GitCDN.link
Benefits:
Lets you link to specific commits, as well as auto-get the latest (aka master)
Incurs no damage from high traffic volumes; RawGit asks that it's dev.rawgit.com links be only used during...
@lyxal I suppose at the very least we could probably do a bit of CSS to make e.g. the boxes black and stuff like that even when it doesn't have the Vylight stuff, just so that it's not so jarring
@AaroneousMiller idk if that'd deliver the files properly
also, you can't use the raw files from github (ie clicking raw and linking that page) because it doesn't deliver it with the right format (ie it doesn't send it as a stylesheet)
One solution is to just have the vylight files inside the repo, but that defeats the point of having vylight as its own repository
Add a branch your project using the name "gh-pages" and then you'll (shortly after branching) be able to use a direct URL such as https://username.github.io/project/master/style.css (using your URL, and assuming "style.css" is a file in the "master" folder in the root of your "project" repository...
@lyxal Could you just clone the Vylight repo in its own directory on your server? I know you said it saves a marginal bit of space to have it somewhere else, but I wouldn't think a couple dozen kilobytes would be a huge deal (and most of that is the demo.html).
Sure, GH Pages could work. It'd be a tradeoff at that point between more work to have everything self-contained vs. less work but a higher possibility of connectivity issues breaking your site.