git clone git://github.com/apotonick/dumdidoo.git
cd dumdidoo/
git submodule init
git submodule update
gem install cassandra
gem install simple_uuid
Updated workflow from Up and running with Cassandra.
irb
module Bar | |
def do_sth | |
puts "@proxy: #{@proxy.inspect}" | |
end | |
end | |
class Foo | |
include Bar | |
def initialize |
class MyController < ApplicationController | |
include Apotomo::Rails::ControllerMethods | |
has_widgets do |root| | |
if must_attach_a_wigdet? | |
# current_widget_data is anything that the Cell needs to build | |
# the widget (say, a User record…) | |
root << widget('my_widget', | |
"widget_#{@current_widget_data.id}", |
# in lib/apotomo/widget.rb | |
# This comes redundant with Cells internals, but this is due to what may be a flaw in current Apotomo's design, | |
# which bypass Cells workflow (render_cell_for) and hook directly into AbstractController::Rendering #render_state | |
# Renders the +widget+ (instance or id). | |
def render_widget(widget_id, state=:display, *args) | |
if widget_id.kind_of?(Widget) | |
widget = widget_id | |
else | |
widget = find_widget(widget_id) or raise "Couldn't render non-existent widget `#{widget_id}`" |
# Our goal is to be able to run spec:bricks along spec, when | |
# using the 'rake spec' command. | |
# In lib/tasks/custom_specs.rake, add: | |
require 'rake/testtask' | |
require 'rspec/core/rake_task' | |
namespace :spec do | |
desc "Run bricks specs" | |
RSpec::Core::RakeTask.new('bricks') do |spec| |
key | axis | value | |
---|---|---|---|
min | 1 | 2 | |
avg | 1 | 3.6 | |
max | 1 | 5 | |
min | 2 | 3 | |
avg | 2 | 8.2 | |
max | 2 | 10 | |
min | 3 | 0 | |
avg | 3 | 2.6 | |
max | 3 | 8 |
### | |
FooBar jQuery Plugin v1.0 - It makes Foo as easy as coding Bar (?). | |
Release: 19/04/2013 | |
Author: Joe Average <joe@average.me> | |
http://github.com/joeaverage/foobar | |
Licensed under the WTFPL license: http://www.wtfpl.net/txt/copying/ | |
### | |
(($, window, document) -> |
It's easy overlooking the basics. One must be able to clearly explain how the web works, using the dedicated vocabulary.
I recommend carefully reading the following resources:
A browser mostly "speaks" HTTP. It will craft HTTP requests for you when accessing or interacting with a website. When using JavaScript, you might also create custom HTTP requests. HTTP is the underlying language of the web.
import Graphics.Element exposing (..) | |
import Text | |
type Fifo a | |
= Empty | Node a (List a) | |
empty : Fifo a | |
empty = | |
Empty |