-
A. Schneider, "Real-Time Volumetric Cloudscapes," in GPU Pro 7: Advanced Rendering Techniques, 2016, pp. 97-127. (Follow up presentations here, and here.)
-
S. Hillaire, "Physically Based Sky, Atmosphere and Cloud Rendering in Frostbite" in Physically Based Shading in Theory and Practice course, SIGGRAPH 2016. [video] [course notes] [scatter integral shadertoy]
-
[R. Högfeldt, "Convincing Cloud Rendering – An Implementation of Real-Time Dynamic Volumetric Clouds in Frostbite"](https://odr.chalmers.se/hand
I made a documentation generator that cashes in on Clojure's dynamism. See the play-cljs docs (a ClojureScript game library) for an example of its output.
Like many of you, I've often wondered what my final regret will be on my deathbed. My best guess came to me in a dream recently. I was walking across the charred earth of an apocalyptic future world, maneuvering around the remains of the less fortunate. I was startled to find a young girl, barely holding onto her life. She murmured something to me. I asked her to repeat it, and she said more loudly: "I...wish your Clojure projects didn't have such crappy documentation."
;; React supports "refs" as a way for a component to get a | |
;; handle to its children. Classically, refs were string-based. | |
;; Recent versions of React support callback attributes as a | |
;; more elegant variant of accessing DOM notes or components. | |
;; | |
;; This example uses a Form-3 component as per | |
;; https://github.com/Day8/re-frame/wiki/Creating-Reagent-Components | |
;; | |
;; For callback refs, see React's documentation | |
;; https://facebook.github.io/react/docs/more-about-refs.html |
https://www.youtube.com/watch?v=MzVFrIAwwS8 | |
http://jonathancreamer.com/ | |
https://basarat.gitbooks.io/typescript/content/docs/project/tsconfig.html | |
http://henleyedition.com/implicit-code-splitting-with-react-router-and-webpack/ | |
https://github.com/nfl/react-helmet |
public class RealmListParcelConverter implements TypeRangeParcelConverter<RealmList<? extends RealmObject>, RealmList<? extends RealmObject>> { | |
private static final int NULL = -1; | |
@Override | |
public void toParcel(RealmList<? extends RealmObject> input, Parcel parcel) { | |
if (input == null) { | |
parcel.writeInt(NULL); | |
} else { | |
parcel.writeInt(input.size()); | |
for (RealmObject item : input) { |
(ns deep-merge-spec | |
(:require [midje.sweet :refer :all] | |
[util :as u])) | |
(fact (u/deep-merge {:one 1 :two 2} | |
{:one 1 :two {}}) | |
=> {:one 1 :two {}}) | |
(fact (u/deep-merge {:one 1 :two {:three 3 :four {:five 5}}} | |
{:two {:three {:test true}}}) |
We're working on a project that uses the Datomic Pull API to pull specific attributes out of Datomic entities. Here's an example of query that uses the Pull API:
(d/q '[:find [(pull ?e [:sales/deal_number :sales/deal_close_date :sales/state]) ...]
:in $ ?date
:where [?e :sales/deal_close_date ?d _ _] [(> ?d ?date)]]
db
(days-ago-at-midnight 1))
;; I could have used a closed dispatch (aka cond) but you may find this version more enjoyable | |
;; the spec format is the one provided by BG | |
(defprotocol Selector | |
(-select [s m])) | |
(defn select [m selectors-coll] | |
(reduce conj {} (map #(-select % m) selectors-coll))) | |
(extend-protocol Selector |
(defn uuid [] (str (java.util.UUID/randomUUID))) |