Giter Club home page Giter Club logo

trivelapp's Introduction

Trivel

This is is to allow users to view different places that they would like to travel to that we offer them. This allows them to view average prices and details of the place they are looking at. This app is designed for families and older couples who would like to travel. I feel like this would also apply to a few in a younger audience that would like to travel the world before they start a family.

Git Config Instructions

git config --global user.name <<<YOUR NAME HERE>>>

git config --global user.email <<<YOUR EMAIL HERE>>>

Pictures Of our App

Splash Screen

alt text

About Us Page

alt text

About Us Page With Translation to Spanish On

alt text

Navigation Drawer

alt text

Credits Page

alt text

Wish List Page with no content added

alt text

Trip Packages that the company offers

alt text

Single Trip Package View

alt text

Fab Button expanded

alt text

Wish List Page with some content added

alt text

Commiting Instructions

Download/Clone the project from the repository

Perform the Git Config Instructions

Perform a git branch -a to see all the branches on the github repo

'git checkout staging' so that it creates a local copy of staging you can branch from

Create a branch that branches from staging and check it out git checkout -b branchname

When you are ready to put your work into staging (the main project) you do the following Checkout staging git checkout staging

Pull staging (ensure your local staging is up to date with the copy on origin) 'git pull'

Checkout your branch git checkout branchname

Merge staging into your branch (This may cause a merge conflict if staging had content it downloaded) 'git merge staging'

Fix any issues that are in your project indicated by <<<<<<head ======== >>>>>>branchname

Once all issues are fixed perform another commit git add . and git commit -m โ€œโ€ Checkout staging git checkout staging

Perform a git pull (to ensure staging did not change while we were making fixes) git pull

IMPORTANT (if there are no changes then we can proceed. If there are changes and updates are downloaded we repeat the above steps)

If no conflicts appeared and everything is up to date you are ready for your code to make its way into staging

Push your branch to github git push origin branchname

Go to GitHub and perform a pull request (possibly tag a group member to get it done faster)

Additional Tips

Document everything you do with JavaDoc Comments

With each commit comment the issue it is addressing git commit -m "#4 this addresses isssue number 4"

trivelapp's People

Contributors

nstajduhar avatar josegeorges8 avatar

Watchers

James Cloos avatar  avatar

trivelapp's Issues

Meeting Minutes #3 (Week 2)

Date: December, 14th, 2017
Attended: Nick
Hours: 2 Hours
Discussed / Accomplished:

Due to inclement weather Jose was not able to make it to the school for our meeting or class. But throughout the week we discussed our app and improved the design a few ways as well as discussed how we are going to create our packages.

For the design we found a open source library for FAB buttons. This allows us to deprecate the contact tab from our tab host and move the remaining buttons to a different fragment once we decide what that fragment will include. In that fab menu we moved the Add to wish list fab, Our Location Intent, and then the Add to Calendar intent. This allowed for our app to have a much cleaner look and a more simplistic design.

MyWishListFragment

create a simple fragment with a recyclerView that gets populated with trips that the user add to it.

trips will be added once the user presses "Add to wish list" in the TripViewFragment

Fab Button Wish List Tag not changing

When the user adds a package to their with list, the tag button changes from "add" to "remove". however, closing and opening this fragment back again will make it "add" again even though it should be "remove"

Trip View

Design a basic layout.

  • Add title
  • Description
  • Contact, Email, Call, etc buttons.
  • Add button to add to the wish list.

Packages

Create packages for trips with the following:

  • name
  • 5 pictures
  • brief description
  • price
  • duration
  • activities
  • location

we should have at least 20 packages for demonstration purposes.

View Pager indicators

Add an indicator for view pager to let the user know that there are more images and which image they are looking at

Meeting Minutes Week #1 Meeting 2

Date: December, 7th, 2017
Attended: Jose, Nick
Hours: 1 Hours
Discussed / Accomplished:

We all booked a study room to conduct our meeting. We met up in the room and started going over what we both have completed over the past week and explained any code that we had questions about. From there we continued to discuss how we would pass the information from the bundle that contains our trip title, images, description, address, etc to the TripView Fragment. As well we also started configuring the images in the ViewPager and started hooking up a fab button for the add to wishlist feature.

Packages/Trips

Create Recycler View for the list of Packages/Trips

  • Temporary Layout for each trip
  • Create OnClickListener to connect to the TripView
  • Populate with temporary trips

Animations

Add animations to the program where needed:

Fragments transactions.
Pressing buttons.
Deleting items from recyclerView.

Clean code

As of right now, the code looks a bit messy. Try to clean code and make this more clear has we go

Implicit Intents

Add following intents:

Email Intent: An intent that will launch a third party app to send an email to Trivel's agency about booking an appointment with us. Email should contain name of the package that was open at the moment.

Call Intent: An intent that will launch a third party app to call our business line.

Location Intent: An intent that points at the location of the specified package in a third party app.

Web Intent: An intent that will open a third party app to show a website about the package (Ask Cai if we can use real websites or make one for our own.

note: location on where the intents are going to be used is not decided 100% yet.

Meeting Minutes #5 (Week 4)

Date: January, 4th, 2018
Attended: Nick
Hours: 2 Hours
Discussed / Accomplished:

Jose was sick and could not attend the meeting. We discussed on facebook what things needed to be completed. This consisted of Animations and the creation of packages for our app. We also went through the overall design and fixed an issue on the trip view which was fixed by adding a scroll view.

During the meeting time Nick worked on creating packages and adding the required scroll view. After the scroll view was added the issue for not being able to read all the description text was fixed. The package creation has begun and some demo package have been added and we have started populating them in the app

Font changes

Fonts should be change following this recommendations:

TITLES
-should be bigger than the rest of the text
-bold

SUBTITLES
-medium size
-bold

REST OF TEXT
-small, regular size.

CreditsFragment

create a simple listView with the credits for each item. The layout could be design like the listView example viewed in class, showing the license in the bottom every time we click the name of a library.

add each item to the list as we used them.

Meeting Minutes (Week #1)

Date: November, 30th, 2017
Attended: Jose and Nick
Hours: 2 Hours
Discussed / Accomplished:

On this meeting we discussed the theme of the app and how the design would go. We finally agreed that the app would be about a Travel Agency called Trivel who's app purpose is to show the travel packages they have available, let you add them to a wish list to organize places you want to go, and contact the company to book an appointment and discuss about the package.

Jose designed a quick sketch of how the app would be distributed and Nick agreed on it.

We also agreed that the drawer menu would have 4 navigation items:
Our Packages: a list containing the packages.
My Wish List: a list containing the packages the user has been selected.
About us: a quick summary of the company and what the app purpose is.
Credits: credits to the third party apps we use and any type of extra data(if any).

We decided that Jose was going to start working with the Our Packages navigation item and Nick was going to start the TripPackage Layout, which is how each package will fully look like.

We also added a couple of issues to work on. This will be updated weekly.

Date: December, 7th, 2017
Attended: Jose, Nick
Hours: 1 Hours
Discussed / Accomplished:

We all booked a study room to conduct our meeting. We met up in the room and started going over what we both have completed over the past week and explained any code that we had questions about. From there we continued to discuss how we would pass the information from the bundle that contains our trip title, images, description, address, etc to the TripView Fragment. As well we also started configuring the images in the ViewPager and started hooking up a fab button for the add to wishlist feature.

Meeting Minutes #6 (Week 5)

Date: January, 11th, 2018
Attended: Jose And Nick
Hours:1 Hour
Discussed / Accomplished:

Nick and I grouped together to finish details on the presentation. We decided the theme for the slides, and how it is going to be structured. We decided to go through with the following order:

  • requirements
  • overall design structure of fragments
  • libraries used
  • how the fragments are split up
  • workload
  • break down of the work done by week
  • some specific issues encountered
  • quick solutions for those issues
  • overall of how the app ended vs how we imagined it

AboutUs Layout

create a layout of how the about us section will look like. it'll have:

  • A quick description of the agency
  • A list of sales reps to contact

Meeting Minutes #4 (Week 3)

Date: December, 21st, 2017
Attended: Nick, Jose
Hours: 2 Hours
Discussed / Accomplished:

At the start of our meeting we went over the current updates of our app and discussed the changes and the design modifications. After our discussion we continued to discuss our needs that had to be completed. We decided that View Pager Indicators, A Logo, and Scroll View where our top priorities.

We added a dependency for PageIndicatorView (romandanylyk). This allowed us to add indicators under the image view so users know they can swipe through the images. We also added a scroll view over the whole trip view this allowed us to have all the content visible on every phone no matter what their screen size is. Jose also found a suitable logo for our app that was Creative Commons

Logo License:

License: Flaticon Basic License.

Icons made by Icon Pond from www.flaticon.com is licensed by CC 3.0 BY

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.