cs329e-presentation

Transcript

1. CANJA
2. Team CANJA • Carlos Loya ◦ Full stack • Andrew Chen ◦ Full Stack • Nancy Tran ◦ Front end • Jatin Konchady ◦ Front end • Andrew Rogalla ◦ DevOps
3. Issue Tracker/Deployment • 47 Issues • GCP 502 Bad Gateway (NGINX) • Unit tests would stall when linked to About page • Stretch goal to implement an autocomplete live search feature from splash page
4. Unit Tests https://travis-ci.org/arr3385/cs329e-idb
5. Storyboarding
6. Design Philosophy Material Design (Quantum Paper) Responsive Web Design
7. Logic • Many-to-Many ◦ Books to Authors • Many-to-One ◦ Books to Publishers • Association ◦ Relates each book instance to each of its authors and publishers
8. Association Table
9. Database • PostgreSQL ◦ SQLAlchemy ORM • Caches were used to avoid duplicates in our DB
10. Data Tables • Server-side processing • Custom column definitions for each attribute • Utilizes CDNs to load jQuery and Data Tables
11. Demo http://canja.fun
12. Self-Critique What could we have done better? • We were unable to run our unit tests successfully on our website; our website would hang after a while, so we had to compromise and link to Travis • We were unable to fully implement a search function on our splash page. We got a live search working where a user would get suggestions but we couldn’t figure out how to make the right URL request to these suggested pages. • Our website currently has a rather simple color scheme, which is something we plan on making more complex and interesting in the future. • The data models do not look nice when viewed on a phone. The tables are not responsive and the footer doesn’t extend to cover the page properly.
13. Self-Critique What we did well • Implementing the parallax scroll on our about and splash page • We were able to solve the intermittent 502 gateway error we kept receiving by transferring to a new project using a new database • Everything was well documented and can be easily replicated using our instructions on our GitHub ReadMe
14. Self-Critique What we learned: • We learned how to apply our readings from XP Installed from throughout the semester. • All of us were new to flask, and are now aware of its uses and capabilities for future use. • Using ORMs like SQLAlchemy with relational database management systems such as PostgreSQL • Developed good practices with version control and git • Learned how difficult deploying a web application can be ◦ Extremely simplified with GCP • An understanding of how web browsers and web servers communicate • HTTP request processing
15. Booksgalore.me Critique What did they do well? • The tabination on their about page gave it a clean look • The data tables look nice and well populated. The fact that they display “N/A” in empty fields of the tables is very neat. • Models are interconnected and can jump from authors to books to publishers with ease. • We liked the fact that they displayed some books on the splash page, it grabs the interest of a user.
16. Booksgalore.me Critique What could they have done better? • Implemented more CSS styling so that the splash page could be more dynamic • Create buffer white space on the sides so text does not go edge to edge • BooksGalore on the navbar is a button, but it doesn’t do anything • Update the about page to more accurately reflect commits/issues
17. Booksgalore.me Critique What did we learn from their project? • Tabination on the about page can be a good clean design choice • Adding default values to NULL attributes in Data Tables