Up tonight, I hope to finish off my efforts to get my simple Backbone.js application, Funky-Backbone.js-Calendar, easily install-able. By "easily install-able", I mean:
➜ tmp git clone git://github.com/eee-c/Funky-Backbone.js-Calendar.git Cloning into Funky-Backbone.js-Calendar... remote: Counting objects: 1027, done. remote: Compressing objects: 100% (534/534), done. remote: Total 1027 (delta 512), reused 961 (delta 446) Receiving objects: 100% (1027/1027), 280.11 KiB | 105 KiB/s, done. Resolving deltas: 100% (512/512), doneIn that cloned directory, I have to follow a temporary additional step—checking out the "dirty" (as in node-dirty) branch. Assuming this goes OK, I will merge this into master and eliminate the step:
➜ tmp cd Funky-Backbone.js-Calendar ➜ Funky-Backbone.js-Calendar git:(requirejs) git co dirty Branch dirty set up to track remote branch dirty from origin. Switched to a new branch 'dirty'Now, I need to install the node.js modules required to run the server:
➜ Funky-Backbone.js-Calendar git:(dirty) npm install firstname.lastname@example.org ./node_modules/dirty email@example.com ./node_modules/dirty-uuid firstname.lastname@example.org ./node_modules/express ├── email@example.com ├── firstname.lastname@example.org ├── email@example.com └── firstname.lastname@example.orgMan, I freaking love npm.
With that, I am ready to start the application server:
➜ Funky-Backbone.js-Calendar git:(dirty) node app The "sys" module is now called "util". It should have a similar interface. Express server listening on port 3000 in development modeHrm... I am not sure what that "sys" vs. "util" message is. I will worry about that another day.
For now, I navigate to
http://localhost:3000and am greeted by an empty calendar:
If I click on any day in the calendar (today's date for instance), I am greeted with an add-appointment dialog:
Clicking "OK" saves that record, which then shows on the calendar:
I can even update and delete appointments by clicking on the appointment title and the little "X" next to it, respectively.
Satisfied that all is in order, I merge the node-dirty branch into master and update the README.
There are a couple of minor little bugs in there. I will likely resolve them quietly. Tomorrow, I hope to do a little cleanup work with jasmine before calling it quits.