start new:
tmux
start new with session name:
tmux new -s myname
W3C Introduction to Web Components - explainer/overview of the technologies
#!/bin/sh | |
echo Install all AppStore Apps at first! | |
# no solution to automate AppStore installs | |
read -p "Press any key to continue... " -n1 -s | |
echo '\n' | |
echo Install and Set San Francisco as System Font | |
ruby -e "$(curl -fsSL https://raw.github.com/wellsriley/YosemiteSanFranciscoFont/master/install)" | |
echo Install Homebrew, Postgres, wget and cask | |
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)" |
Pub has two commands for working with transformers, build
and serve
. Both of those currently are hardcoded to only see stuff in your package's web/
, asset/
, and lib/
directories. We've been wanting to have support for test/
, example
, and others for a while (see #14673 and #15924). This sketches out what I'm thinking to handle this. Feedback is welcome!
The basic idea is that build and serve will be able to see of these directories: asset/
, benchmark/
, bin/
, example/
, test/
, and web/
. Transformers will be able to run on assets in any of those.
Right now, pub build creates a build/
directory containing the output of the build process. That directory only contains the outputs whose path is within web/
. If we start building tests and examples into there, stuff could start colliding.
So the first change is that we'll reorganize the build/
directory to match your package. Outputs within web/
will
Spent a bunch of time talking to Nathan, Siggy, and Kevin about how to handle pub serve
with stuff outside of web/
. Our goals are:
Root-relative URLs inside web/
, test/
, example/
, and even things like
subdirectories of example/
should be supported. This means that the root
directory being served needs to be constrained to those.
We can't require the user to hit localhost:8080/example/example1/foo.html
because it would break a root-relative URL in foo.html
.
More than one of these directories needs to be servable simultaneously. If you have to shut down the server and restart it (which entails rebuilding
#!/usr/bin/env bash | |
set +o xtrace | |
USER=$USER | |
PROJECT=dart-compute-project | |
INSTANCE_NAME=dart-compute | |
TAGS=dart | |
MACHINE_TYPE=f1-micro | |
NETWORK=default | |
IP=ephemeral |
Here is a high level overview for what you need to do to get most of an Android environment setup and maintained.
Prerequisites (for Homebrew at a minimum, lots of other tools need these too):
xcode-select --install
will prompt up a dialog)Install Homebrew:
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
/// Dart is built around a timer, which basically schedules functions in a queue. | |
/// The Future class is essentially just sugar on top of the event loop. | |
/// To help people understand what the event loop actually does, I have written code which implements the event loop. | |
/// See https://www.dartlang.org/articles/event-loop/ for more information. | |
import "dart:async"; | |
class EventLoop { | |
/// Function Queue. | |
static final List<Function> queue = []; |