nicovalencia

import React from 'react';

const DataContext = React.createContext();

class DataProvider extends React.Component {
  state = {
    items: [
      "Thing 1",
      "Thing 2",
      "Thing 3",

elenadimitrova

contract EternalStorage{

    mapping(bytes32 => uint) UIntStorage;

    function getUIntValue(bytes32 record) constant returns (uint){
        return UIntStorage[record];
    }

    function setUIntValue(bytes32 record, uint value)
    {

whichlight

If I'm talking about participatory and interactive art, we've got to do some demos together. Not sure how this will turn out, but that's part of the fun. Turn the sound up, maybe lock your screen orientation, and check these out:

1. bubblegum postcard - mobile or laptop
2. dancey dots - mobile or laptop
3. cellular - mobile only

yay arpegiattor

1. sounds for spring - mobile or laptop

robacarp

##Intro

Generator frameworks spend way too much time creating obscure and pointless DSL syntax just to make the code trendy and cute. This generator comes in the form of pure ruby, instantiates real model objects (which fire their pre-, post- and other hooks appropriately), and still allows for a simple syntax to override parameters of generated objects.

Standard Ruby syntax allows for easier adoption by new programmers and reinforces ruby paradigms, instead of breaking them down with a cute, often incomplete, and entirely superfluous DSL syntax.

Specific complaints against existing frameworks:

• Rails fixtures: definition syntax (yaml) doesn't provide a powerful enough interface to rapidly creating objects.
• FactoryGirl: Factories are evaluated at load-time, making some factories just awful to define. No further comment on DSLs.