card game. • 60 card decks, yet tens of thousands of exist. • Turns are taken playing creature or spell effects from hand. • Goal is to murder your rival player(s). Why we picked this as our topic: • We like it! • The source database was well organized and comprehensive. • But mostly because our original topic got prof blocked. //Scraped from Deckbrew Restful API
cards and sets Made separate model for artists because MtG card art is awesome Edition model is the link between the other three models Cards, Artists, and Sets (and Editions).
information from the SQL database. Inject the information into an HTML template using module and controllers. Insert the HTML template into the container on the main layout page (index.html) by using ng-view. ng-Sanitize and ng-BindHtml utilized for cost icon generation and symbols in card text. Utilization of D3’s Hexbin library for splash page widget. "cost": "{2}{G}{G}{W}{W}{U}{U}" "text": "Flying\nAt the beginning of your upkeep, sacrifice Arcades Sabboth unless you pay {G}{W}{U}. \nEach untapped creature you control gets +0/+2 as long as it's not attacking.\n{W}: Arcades Sabboth gets +0/+1 until end of turn."
Search (Sanitized) • Search page organizes data into 2 tables (AND, OR) Backend for search: • SQL/Python for search, highlighting, and pagination. SQL Search Engine
system independent and alleviate the pain associated with Carina … We created Bash Scripts! (Warning! Side effects include: dizziness, nausea, headaches, dry heaving, and loss of patience and friends.) Next up: Unit Tests with Mark and Stephanie
de la Garza: 11 • Shanell Smith: 13 • Stephanie Wilbur: 10 • Mark Lindberg: 10 Closed • Peter Scamman: 8 • Javier de la Garza: 15 • Shanell Smith: 18 • Stephanie Wilbur: 8 • Mark Lindberg: 7
2. Learned how to coordinate and collaborate more often. 3. Learned how to use SQL queries for many things. 4. Only 1.5 of us actually understand Carina at this point... 5. We overlooked empty files in part 1 and didn’t make static pages. 6. Our original directory structure was not good. 7. We organized our roles well! 8. We all rose to the occasion when things came up. :)
done well to also implement error visibility) 3. Search is functional but the results have only one column 4. Data is incomplete (Only 4 states) 5. Pagination is unusual: No limit on number of pages at bottom 6. Google maps is integrated for states and cities but not for neighborhoods (just shows world) 7. Access to their API was spotty Basking… get it?