AKA OOP: There it is
binding.pry to play with code live
Dry food: We generally keep her dry food bowl full. The bag is under the kitchen sink. Kitty treats are in the left-most drawer in the kitchen, by the doorway.
Wet food: In the evenings she gets 1/4 of a can of wet food. You can put it in the little glass Pyrex dish on the kitchen floor. The wet food is stored in the fridge with a blue reusable lid. Feel free to use one of the knives sitting in the dish drainer to scoop it out -- just rinse it off well afterward!
Water: She drinks out of the fountain on the floor by the kitchen table. If you can hear water splashing in the fountain, then it could probably use more water. There's a blueish-purplish pitcher on top of the fridge: just fill it up and pour it on the fountain. We'll change the fountain's water filter before we leave, so you shouldn't need to worry about that.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Angular</title> | |
| <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.3.15/angular.min.js"></script> | |
| </head> | |
| <body ng-app="myApp"> | |
| <div ng-controller="myCtrl as VM"> | |
| <a my-dir | |
| attr1="VM.sayHi('Juan')" |
These are the steps you might take to complete this project. There's no right way to make an Express app -- nor any other app.
This walkthrough gets you up to the point of having an app that renders in the browser, makes database queries, and has AJAX -- but is still very bare-bones. The examples below use a "Movie" model, but that can be replaced with anything else.
We strongly recommend that you use the "drive/steer" pairing model on this: only one computer is open, with only one person working on it, while another person directs them and tells them what to type.
I'm intrigued by how you required your env.js and how you connected to your database. Nothing wrong with either of them, except perhaps that it adds some extra length to your app.js; just never seen it done that way before.
Meets expectations
Your d3code.js file seems to contain entirely HTML. Why is it named .js?
I'm not a stickler for following convention with file structure, since I'm all for people organizing their files in a way that makes sense to themselves. However, I have difficulty seeing the logic behind this structure. For instance: you have .html files in two completely separate folders. What was the rationale for organizing files as you did?
There are lots of "app_SOMETHING" files floating around. I'm unsure whether these are actually used in the app... Are they just data backups? If so, I would have liked to have seen them partitioned off in a "backups" folder.
Virtually all of the front-end Javascript is in one file that's over 700 lines long. During our meetings I could see group members physically struggling to scroll through and find stuff in the file. This is really the whole reason for splitting code into separate files in the first place: to keep from having to scroll and find so much.
| <!DOCTYPE html> |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Hello!</title> | |
| </head> | |
| <body> | |
| <h1>What an elegant webpage.</h1> | |
| </body> | |
| </html> |