Mix.install([
{:liveview_playground, "~> 0.1.8"},
{:phoenix_ecto, "~> 4.5"},
{:ecto, "~> 3.11"},
{:ecto_sqlite3, "~> 0.13"}
])
defmodule MyAppyWeb.TaskTestLive.Index do | |
use MyAppWeb, :live_view | |
require Logger | |
@impl true | |
def mount(_params, _session, socket) do | |
# Trap exits to catch when a Task is forcibly cancelled. | |
Process.flag(:trap_exit, true) | |
socket = |
{:linters {:mount/defstate {:level :warning}} | |
:hooks {:analyze-call {mount.core/defstate hooks.defstate/defstate}}} |
// Example of OSC control of Hydra video synth w/Orca programming language | |
// by Yancy Way (echophon) | |
// | |
// https://github.com/hundredrabbits/Orca | |
// https://github.com/ojack/hydra | |
// https://github.com/ojack/hydra-examples | |
// https://atom.io/packages/atom-hydra | |
// | |
// Prerequisites: Orca, Atom, Atom-hydra extension | |
// |
I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
;; For supporting more PG types, see https://github.com/remodoy/clj-postgresql | |
(ns pg-test.types | |
(:require [cheshire.core :as json] | |
[clojure.java.jdbc :as jdbc]) | |
(:import [org.postgresql.util PGobject] | |
[java.sql PreparedStatement])) | |
;; Writing | |
(defn- to-pg-json [data json-type] |
Namespace owlet.firebase
serves to integrate a Firebase database into our re-frame web application. We need to talk to Firebase without dropping into evil JS interop — so you shouldn't use .set
! But more generally, we must preserve the integrity of our application's re-frame data flow.
In the description below, I've tried to be entirely consistent in my use of names; i.e. the scope of any name is this entire document. So when you see
your-value
orthe-db-ref
, you can count on those names indicating the same entities when they appear later in the document. Also, "ref" or "reference" refers to an instance of [firebase.database.Reference](https://firebase.google.com/docs/reference/js/firebase.database.Refe
$ npm run help
> epoxy@0.41.2 help /home/vagrant/polymer/epoxy
> npm run & gulp help
Lifecycle scripts included in epoxy:
postinstall
jspm install
start
$ npm run help
> @tangogroup/elmer@1.0.0 help /home/vagrant/polymer/elmer
> npm run & gulp help
Lifecycle scripts included in @tangogroup/elmer:
start
webpack-dev-server --config webpack.toolkit.config.js --open
test
package main | |
import ( | |
"fmt" | |
"time" | |
"github.com/aws/aws-sdk-go/aws" | |
"github.com/aws/aws-sdk-go/aws/session" | |
"github.com/aws/aws-sdk-go/service/athena" | |
) |