DonKarlssonSan

// Hyperboloc functions by toneburst from 
// https://machinesdontcare.wordpress.com/2008/03/10/glsl-cosh-sinh-tanh/
// These are missing in GLSL 1.10 and 1.20, uncomment if you need them 

/*
/// COSH Function (Hyperbolic Cosine)
float cosh(float val)
{
    float tmp = exp(val);
    float cosH = (tmp + 1.0 / tmp) / 2.0;

dmnsgn

A non-exhaustive list of WebGL and WebGPU frameworks and libraries. It is mostly for learning purposes as some of the libraries listed are wip/outdated/not maintained anymore.

Engines and libraries ⚙️

Name	Stars	Last Commit	Description
three.js	![GitHub

sliminality

{
  // Evaluate file in the open SublimeREPL.
  // Depends on you creating the Packages/User/EvalInREPL.sublime-macro file.
  { "keys": ["super+r"], "command": "run_macro_file", "args": { "file": "Packages/User/EvalInREPL.sublime-macro" },
    "context": [
      { "key": "selector", "operator": "equal", "operand": "source.elm" }
    ]
  },

  // Reindent selection on tab

zacharycarter

Binding to C Libraries with Nim

---

Table of Contents

• Introduction
• C2Nim
• The C Preprocessor
• Pragmas

swannodette

Externs Inference

Integrating third party JavaScript libraries not written with Google Closure Compiler in mind continues to both be a source of error for users when going to production, and significant vigilance and effort for the the broader community (CLJSJS libraries must provide up-to-date and accurate externs).

In truth writing externs is far simpler than most users imagine. You only need externs for the parts of the library you actually intend to use from ClojureScript. However this isn't so easy to determine from Closure's own documentation. Still in the process of writing your code it's easy to miss a case. In production you will see the much dreaded error that some mangled name does not exist. Fortunately it's possible to enable some compiler flags :pretty-print true :pseudo-names true to generate an advanced build with human readable names. However debugging missing externs means compiling your production build for each missed case. So much time wasted for such simple mistakes damages our sen

mrdoob

Experiments

• http://absulit.com/portfolio/demo/webvr/001/
• https://www.clicktorelease.com/code/polygon-shredder/vr/ #positional
• https://www.clicktorelease.com/tmp/threejs/webvr-physics/ #positional #input #haptic
• https://janusweb.metacade.com/ https://github.com/jbaicoianu/janusweb/
• https://jzitelli.github.io/poolvr/
• https://kuva.io/block-background/ #positional #input
• https://www.shadertoy.com/results?filter=vr
• https://vr-batted-ball-vis.herokuapp.com/index.html

elnygren

; The Expression Problem and my sources:
; http://stackoverflow.com/questions/3596366/what-is-the-expression-problem
; http://blog.ontoillogical.com/blog/2014/10/18/solving-the-expression-problem-in-clojure/
; http://eli.thegreenplace.net/2016/the-expression-problem-and-its-solutions/
; http://www.ibm.com/developerworks/library/j-clojure-protocols/


; To begin demonstrating the problem, we first need some
; "legacy code" with datastructures and functionality:

odewahn

I really liked @tjvantoll article Handling Failed HTTP Responses With fetch(). The one thing I found annoying with it, though, is that response.statusText always returns the generic error message associated with the error code. Most APIs, however, will generally return some kind of useful, more human friendly message in the body.

Here's a modification that will capture this message. The key is that rather than throwing an error, you just throw the response and then process it in the catch block to extract the message in the body:

fetch("/api/foo")
  .then( response => {
    if (!response.ok) { throw response }
    return response.json()  //we only get here if there is no error
 })

rniwa

transaction = new DOMTransaction(function (container, articleList) {
    var childCount = container.childNodes.length;
    for (let article of articleList)
        container.append(article);
    // No DOM mutation is made until this function exits.
    console.assert(childCount == container.childNodes.length);
});

transaction.commit(element, articles);

cure53

Calling alert from WebAssembly (WASM)

This very simple and minimal tutorial documents in a few easy steps how to play with WebAssembly (WASM) and get first results within minutes.

While the code below is mostly useless, it will show, how to call the alert function from within a WASM file and thus demonstrate how to import and export DOM objects.

Of course, this exercise has no real use. It is just meant to show, that getting started with WASM isn't hard. And there is no need for a complex build-chain, tons of tools or a dedicated VMs. Just use a browser, one online tool and that's it.

And Now?