To interaction with the dtime API via Javascript, you need to be able to chain together API calls in a straightforward manner.
Hypermedia APIs rely on state machine logic - given a current state, there are a number of transitions you can make (Valid HTTP verbs on the available rels)
In the code, transition(current_state, rel, opts) is our way to transition.
| class Dtime.View extends Backbone.View | |
| # Call cleanup before removing completely, | |
| # unbind events from this and all children | |
| leave: -> | |
| @cleanup?() | |
| @unbindFromAll() | |
| @remove() | |
| @_leaveChildren() | |
| @_removeFromParent() |
I read this trick on the Soundcloud blog: http://backstage.soundcloud.com/2012/06/building-the-next-soundcloud/
You can return an existing object from a javascript constructor to avoid creating a new object.
I'm using this as an identity map - one instance per id. Adapted to Coffeescript and adding a feature
to update the existing class with any new information (me.set(data)), it looks something like user.coffee.
You have to copy-paste the simple return super constructor into every child class. Without this the code breaks. Not sure how to solve this issue.
Usage:
s3 = AWS::S3.new(...)
s3.buckets['bucket-name'].objects['object-name.jpg'].url_for(:write, content_type: 'image/jpeg')
Generates a signed request allowing a PUT /bucket-name/object-name.jpg with an image file, so that an HTTP PUT can be used instead of a presigned_post request with HTTP POST and a bunch of hidden fields.
| desc 'clears cache' | |
| task 'cache:clear' => 'environment' do | |
| warn "Clearing cache.... #{$cache.flush}" | |
| warn "Removing cache.... #{`rm -rf tmp/body`}" | |
| end |
| require './config/boot' | |
| Dtime::Users::User.find_each do |user| | |
| user.set({ | |
| follower_count: user.follower_ids.size, | |
| following_count: user.followed_user_ids.size | |
| }) | |
| end |
Have you ever seen a website and wondered how it was made? How does a programmer even get started building one? Well, wonder no longer - I'm going to give you a quick rundown of the building blocks for a modern website.
When you access a website via your web browser, you are connecting to another computer that gives you back a set of files that make up the website. This other computer is referred to as a "server" because it serves your browser (the
