@soegaard2 Thanks for linking my project! :smile:

I didn’t expect to see myself on hackernews when I woke up this morning :stuck_out_tongue:

@jerome.martin.dev , that’s a very cool looking game. I noticed it only has keyboard based control, so I can’t figure out a way to try it via mobile. This is not a criticism by the way. I’m just curious how hard it is to accept mobile friendly inputs in WASM.

@carl.morris.world Thanks :slightly_smiling_face: Well, the input is handled through javascript, then passed to the wasm layer, so it’s pretty much the same way as any js-based game. You just need to find the coordinates of the finger tap, and send that down.

Anyways the game is not that fun and the AI… approximative… So I’m not really planning to improve this further for now. I could make it fit the screen, and accept touch inputs, but, well, I have bigger fish to fry.

There’s currently no way, afaik to raco pkg install --no-docs foo. Is there a reason why a --no-docs, i.e. please do not scribble docs, is not implemented? It seems like it shouldn’t be too hard and extremelly useful as you might not want them - for example during CI.

@pocmatos I think that would be pretty easy to implement

same here - which is why i wondering why it’s not done already. I never really bothered looking but just noticed that quite a bit of ci time for racket news is actually scribbling docs for some dependencies.

i accept the answer: nobody cared until now. :slightly_smiling_face:

i mentioned because i thought it was strange nobody had cared until now. I actually assumed there was some technicality that I was missing.

@pocmatos often you can avoid that just by not depending on the -docs packages

when I really want to avoid it I use --no-setup and then run raco setup -D.

yes… I can do that for now until we have a -D --no-docs for install. thanks.

Making sure the docs build is a good thing to test. Maybe it’s not necessary to test that on all N jobs in some matrix. Although if the matrix is N versions of Racket, maybe all N should test that. I mean one common doc problem is a bad link, and sometimes things are bad links because some identifier wasn’t added until version X of Racket.

Sorry I’m just kind of thinking out loud here.

I can see situations where skipping doc build for some/all CI builds would be good! I’m just thinking out loud that I probably don’t have any such situations, myself.

I agree one should test docs build but I only need to test that my docs build. Other packages should test theirs and I shouldn’t need to install the docs for all my dependencies in CI. That’s the idea. It could speed up my CI tremendously and I am a very impatient person. :wink:

Ah. Good point.

I mean it’s a good point we don’t need to test other packages’ doc builds. It may also be a good point that you are a very impatient person, but I’m not taking a position on that either way. :smile:

:joy:

Hmm but seriously, is it even possible to build docs for one package, but not the rest?

Something like raco pkg install --no-setup my-package && raco setup my-package && raco setup -D — will that build docs only for my-package? I can’t try now but will later.

I’d like to change my email address on https://pkgs.racket-lang.org but I don’t see how in the web site UI?

Is this infrequent enough not to need a UI, and I should just email someone like Jay or Tony?

Naturally. I was mostly curious because I’d been wanting to try building something interactive on the web using racket and I’m curious about the limitations. Developing html via xexpr was such a pleasant surprise that I’d hoped I could find a way to do dynamic content with racket equally well.