Arc Forumnew | comments | leaders | submitlogin
3 points by shawn 472 days ago | link | parent

Yeah, it was worth the effort to make the drawing code client side. Someone showed up and made a software rasterizer.


2 points by krapp 470 days ago | link

why not go all the way and render client-side in a canvas as well?

As it is, the more "pixels" you have, the slower the page loads. You could probably have just a single canvas and a single event handler.

You could preserve functionality for non-js users by using an imagemap (assuming browsers still even support those) or sticking the existing code in noscript tags.


2 points by krapp 469 days ago | link

OK... I don't know where I got "single event handler from," that obviously wouldn't be true, but it would still be simpler than having each pixel be a separate HTML form....


1 point by shawn 469 days ago | link

Wanna hop into discord and we can chat about the design?

The repo's open, and I could help get you set up with it if you wanted to work on some of this.

It should be a matter of:

  git clone
  cd laarc
  rlwrap bin/arc
  ((load "news.arc"))
and then http://localhost:8080/place


2 points by krapp 468 days ago | link

Let me actually see if I can come up with a POC first, at least for the canvas and javascript. Realistically, since it's just GET requests that don't need authentication, I shouldn't even need laarc running, I can just send the same requests by AJAX.


2 points by shawn 468 days ago | link is the API, by the way! I should probably mention that somewhere.