| // | |
| // API.swift | |
| // | |
| // Created by Taro Minowa on 6/10/14. | |
| // Copyright (c) 2014 Higepon Taro Minowa. All rights reserved. | |
| // | |
| import Foundation | |
| typealias JSONDictionary = Dictionary<String, AnyObject> |
| # when I tried to start postgres, I had an error telling me there were no postgres clusters created | |
| # so I had to create one using the `pg_createcluster` command, like the following | |
| pg_createcluster 9.1 main --start | |
| #after creating the cluster, it will start the server because of `--start` | |
| #so I had to change to postgresql user | |
| sudo su - postgres | |
| #to change it's pasword, doing `psql -d <database_name> -U <username> | |
| psql -d postgres -U postgres |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
In a software, what matters for the end users is what the system does, not what the system is. A DVD has no value for the user unless you put it into the machine.
Architecture represents what the system is, while what it does is represented by the messages between objects, which is captured via use cases. Architecture is the form, the shape of something, in this case, the objects and the mechanisms to support them.
A good definition of use case is described as the solution to a particular problem. In Jerry Weinberg's words, "problem is the definition between the current state and the desired state". It's safe to assume that state is what the system is, which can be modified by the interaction between objects.
Objects relate to the end user, its business and its components. Classes don't. Classes are a way to represent objects, the state, but they do very poorly when trying to represent what the system does. Once you hit runtime, objects morph into total obscure forms due to the endless inte
| DS.Adapter.registerTransform('object', { | |
| serialize: function(obj) { return obj; }, | |
| deserialize: function(obj) { return obj; } | |
| }); | |
| MyApp.MyModel = DS.Model.extend({ | |
| location: DS.attr('object') | |
| }); | |
| var model = MyApp.Model.createRecord({ location: { lat: 123, lng: 456 } }); |
| RAILS_ENV=production rake db:setup | |
| # produces the error below.....hmmm.....it's a no-worky | |
| psql:/yourprojectpath/yourproject/db/structure.sql:29: ERROR: could not open extension control file "/usr/share/postgresql/9.1/extension/hstore.control": No such file or directory | |
| # hstore postgresql extension needs to be installed, so.... | |
| sudo apt-get install postgresql-contrib-9.1 | |
| # now your extension should be available to enable so log in with psql | |
| psql -d yourproject_production -U yourdbuser -W |
This is a draft for an Acceptance testing framework in Javascript. See the example code.
WARNING
This gist is outdated! For the most up-to-date information, please see http://emberjs.com/guides/routing/!
An Ember application starts with its main template. Put your header, footer, and any other decorative content in application.handlebars.
<header>
This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.
You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.
