Internet Video
Game Database
What We Did
(feel free to open your computer or mobile device during our
presentation to check out our web-application for yourself @)
http://ivgdb.herokuapp.com
Our idea for this project was to develop a database of video games, game developers, and gaming platforms.
The Pirates of SI Valley
Doug Goldstein (Leader Project 1)
Noah Cho (Leader Project 2)
Arash Ghoreyshi (Leader Project 3)
Cristhian Escobar
Robert Hammond
Richard Lage
Group Responsibilites
- repository maintenance
- model design
- web site design
- data collection
- research and understanding of tools used
#GroupWorkSelfie
Doug The Architect
Name:
Doug Goldstein
Focus:
- Apiary API
- Apiary Tests
- Django Testing
- Static Pages
Capn'
Noah
Focus:
- Tastypie coding
- Tastypie testing
- Twitter Bootstrap
Name:
Noah Cho
Arash The Grey
Name:
Arash Ghoreyshi
Focus:
- Django Guide
- Django Coding
- Dynamic Web Pages
Cristhian
America
Name:
Cristhian Escobar
Focus:
Cristhian Escobar
Focus:
- UML Designs
- Twitter Bootstrap
- Testing
Rob
Shakespear
Name:
Robert Hammond
Focus:
-
Technical Report
-
Slid.es
-
Presentation
Richard
Giovanni
Name:
Richard Lage
Focus:
-
Nintendo mastermind
- Tastypie Testing
- JSON file
- SQL Queiries
Navigation of the site
Search
-
Create a search capability
- The result of a search must be a list of links to crises and/or organizations and/or people (e.g. like Google).
- The search results must be contextualized and the search terms must show up.
- The search results must be clickable.
-
Multi-word search must show and results followed by or results.
https://github.com/ddgold/cs373-idb/blob/master/idb/views.py
https://github.com/ddgold/cs373-idb/blob/master/templates/search.html
Search...
API
-
Create a page that exercises your API from the client side in a unique, interesting, and useful way.
- This may require additions and/or modifications to the API.
-
The page must have a clear English description and be rendered attractively.
SQL
-
Write/implement five, interesting, and useful SQL queries.
-
Create a page with the results of those queries.
-
The queries must have clear English descriptions.
-
The results can be rendered in whatever way SQL outputs.
Unit Tests
But does the damned thing run?
We Have Issues
Reflection
What did we do well?
- Thanks to our wizard friend Arash we did fairly well on the Django portion of the project and AngularJS
- Doug's Architect skills helped develop a pretty awesome Apiary Blueprint
- Richard was always on point with subject matter knowledge and quality assurance
- Rob kept a big picture summary of the project and its parts together with the report and presentation.
- Noah was essential in the Tastypie transition process that went smooth
- Cristhian was great at keeping us motivated and Twitter Bootstrap Coding
Reflection
What did we learn?
-
How to take RESTful API code from its blueprint stage in apiary to an actual web host like Heroku
- How to work as a group to deliver a product of value using Agile, Extreme Programming, Pair Programming, and Continuous Integration methods
- How to work productively under a git push/pull source control environment
- How to test under realistic conditions
- How to implement different tools in programming web-applications like AngularJS for frontend data manipulation or Twitter Bootstrap for a beautiful UI
Reflection
What can we do better?
- With concern to our search we could add more data so that when we batch search we actually have a full alphabet bar to sort through
- We could have been a bit more organized with our data attributes in our JSON file since we had to go back and edit these a few times because they didn't match
- We could have used an accordion on our SQL page to make the data separate
Reflection
What puzzles us?
- Making fragments work in the correct order with Slid.es was a pain
- At first we had trouble understanding the difference between our Angular and Twitter Bootstrap tools till Arash and some doc reading cleared it up
- Tastypie had some pooly written docs that made it rough to integrate our API from our blueprint to the real deal
SXSWE
What did they do well?
- The accordion that they used for their SQL section is nice and clean looking
- We all thought the explore circle device they used for their acceptance test page was really cool
- Their choice of layout for the page was very nice and organized
SXSWE
What did we learn from their website?
- The way they handled their SQL queries was perfect with the accordion, we should have done the same with our SQL queries on our site
- Back to top links should be used on the bottom of long webpages
- We liked the way they used thumbnails for related classes in each objects page instead of just hyperlinked text
SXSWE
What can they do better?
- Put more pictures on each object we could only find one image for any object on the page
- Get rid of the search description it is overused since it searches urls and returns the full url
- Organize searches so we know what class the objects returned belong to
- Add resume links to your group member names on splash page so you can use this for job interviews
- When you click Event's at the bottom of the splash page then click a venue it does nothing
- The text in the circle on the acceptance test page is hard to read when it is vertical and clicking on a single object should link us to its page instead of taking up the whole circle
- The background and the buttons on the bottom of the splash page need to be something other than white, maybe you can use the jumbotron image for background
SXSWE
What puzzles us about their website?
- What is that circle thing called and is it going to eat our young?
- Some of the "back to top" buttons are on the bottom of pages where we can already see the top of the page