mhotan / dineon Goto Github PK
View Code? Open in Web Editor NEWGit Repository for our 403(13sp) Android application "DineOn"
Git Repository for our 403(13sp) Android application "DineOn"
I know I'm supposed to work on Restaurant side implementation and was directed at the TODO's. Are there any areas in specific or should I start working my way through the RestaurantLoginActivity folder?
Put everyone's components together for SRS
Instead of having a map of string to menu in Restaurant. Wr should have a the Menu class have contain a string member providing its title. That way the map will just turn into a list. Then we should place that list within the Restaurant Info object.
I think some of us our failing to have a smooth import of the projects is because we are ignoring the .project folder. i read this post on SO.
There someone looked up that the eclipse documentation states about the .project folder
The purpose of this file is to make the project self-describing, so that a project that is zipped up or released to a server can be correctly recreated in another workspace.
Create a custom "check in" Icon and look into how to use standerd facebook log in icons.
Also read (Skim through) Android Design documentation
Lets start organizing the documentation and prepare them to be staged remotely.
Reference Phase 2 spec for what is needed. Everything should be done as far as documentation. It just needs to be organized
Our new Git Protocol.
Note: still figuring out how to apply this to Vince
For friday 26th April, give the team a quick demo on how to do a code review through git hub.
I made a slight mistake requiring us to implement a toBundle and unBundle. Conceptually turning our data types into Bundles works for Android data transfer. But looking at some of the classes I realize that the those classes containing a list of other custom objects.
Well there is no easy way to store Bundles of objects but here is a temporary solution
The correct way to do it is have
Reference: http://developer.android.com/reference/android/os/Parcelable.html
Tutorial: http://blog.logicexception.com/2012/09/a-parcelable-tutorial-for-android.html
Parcelable is the actually the most correct answer. If we did this, we can remove the to toBundle and unBundle implementation. We can theoretically turn them into big JSON Object strings and send them through a bundle that way. But that is the most unnatural way and probably will be a pain in the ass. Plus if we did the big string way I feel like if something goes wrong or we find out it doesn't work we are pretty much F'd.
I suggest we change our storable abstract class to implement Parcelable instead of have Bundle and unbundle methods.
TODO: fix this in time for Beta release.
Build an End to End application that defines all possible user negotiation
Finish the following layouts that refer to non list item things
The following are detail oriented layouts for specific data types.
Think of each one of these fragments taking in there respective data types.
Leave the implementation to me(Mike). You should be able to extract all the related fields and populate the layout views.
Be prepared to also help with the Restaurant layouts soon. more to come later
Expand and modify DiningSession class for listing on the restaurant side
Pack and unpack don't work. All the values have to conform to a JSON Object. It lets you ad regular objects but these objects must conform to a JSON. That means all the storable object we are trying to save must call unpack. Please fix your respective classes and reference Parse documentation to make sure you code to their spec.
Also Parcel writing and reading should be done in the exactly the same order
Also, hook up the buttons to call the restaurant, make a reservation, and add to favorites.
2 ways to get there:
Clicking More Info on the RestaurantHomeActivity page.
Clicking on a restaurant and going to the Information tab.
Parse Object to support Java list. Mark and Jordan created a ParseUtil.packListOfStorables and ParseUtil.unpackListOfStorables that need to be used instead. All of the pack and unpack methods need to be updated appropriately.
Hey Vince I created the projects on the UI thread. They are ready to rock for everybody. I saw that you created those two empty folders on the Master branch. We need to delete those and merge the UI and master branch together
Spec: Feature Set: What are your product's major core features? Include at least 3-4 major features your product will provide, along with at least 2 other minor features or aspects you hope to complete.
Spec: For the ZFR, the bug tracking system
should be set up and should have at least one bug or task filed for each active developer.
Complete sequence diagram for the use case where a user is placing an order.
In combination with Jordan.
Complete UML Class diagrams for the applications.
Try to get a general understanding of expandable list view and list items
Also read (Skim through) Android Design documentation
Update April 29th 2013:
Customize the current list in both applications to respect best mobile HCI practices. Refer to current implementations to understand custom event handlers.
Documentation is currently behind an authentication wall on the webster server (I can't access it).
Suggest moving to:
http://students.washington.edu/
http://homes.cs.washington.edu/FAQ.html
Pack and unpack don't work. All the values have to conform to a JSON Object. It lets you ad regular objects but these objects must conform to a JSON. That means all the storable object we are trying to save must call unpack. Please fix your respective classes and reference Parse documentation to make sure you code to their spec
Also Parcel writing and reading should be done in the exactly the same order
And we are going to run into cyclic problem. where object a calls pack on object b but b calls pack on object a
The capital I in DIneOn is gonna bug me until I die.
Reading and writing Parcelables must be conducted in the exact same order for both
Pull latest version from the UI branch to see if the two application and library projects build correctly. Make sure you pull from the UI branch and refresh the workspace.
I click the facebook login button, and then I'm taken to the facebook login screen, where I enter my email and password. I then get a dialog asking for to authorize DineOn to have access to my info, and I click Ok, but then I'm taken back to the login screen. I retry, and "Login failed" pops up, and I'm taken back to the authorization dialog, where I never get past the login page through facebook login.
Wiki page needs to get updated with the work that's been done over the last phase.
Consult with the customer to pick which use case to implement for alpha release.
All activities have to be able to save the state of the UI.
Get a test Android program running and android and a simple web page running with Parse
Pack and unpack don't work. All the values have to conform to a JSON Object. It lets you ad regular objects but these objects must conform to a JSON. That means all the storable object we are trying to save must call unpack. Please fix your respective classes and reference Parse documentation to make sure you code to their spec.
Also Parcel writing and reading should be done in the exactly the same order
And we are going to run into cyclic problem. where object a calls pack on object b but b calls pack on object a
Make sure your fill out your weekly updates! On the wiki page. If the weekly update page is not available then notify Vince or feel free to make a skeleton one
Create a sequence diagram of the use case where users check in to a certain restaurant.
Create and upload the Android project & apk
Spec: Risks, Cuts, Adjustments: It's very difficult to predict exactly how much work a group will finish in a given amount
of time. Describe at least three specific adjustments you will make if the project begins to fall behind schedule. Two
of the adjustments you list can be feature cuts, but at least one must be some other change or cutback, such as
changing specific areas of testing, adjusting your group dynamics or time schedule, etc.
A google doc was created to further define more task to complete phase 2
Under Specification / Phase 2
https://docs.google.com/document/d/1OABUS9mHMt6cgiSGhMgcjHSatSn8tuVjonfmGf58Zlc/edit
Let me know if you have any questions.
After looking at it more, static methods won't work for updating the state of our app or updating the UI. This is because we need to have references to the current running activity and all its members. This is not possible with static methods.
Jaimees Github user name: pellj
Please add this to collaborators I don't think I have permission to do this.
Write the skeleton code in User App so that actions are abstracted and group members can work on the implementation and worry less about the overall workflow.
Place your comments and approval here to implement the Restaurant Service as a Simple Android application. Jordan and I have met and saw we could implement a basic application in 7-8 user screens. The amount of logic implementation would be proportional.
I vote to do it.
There are errors when building with Restaurant.java b/c of naming mismatches and return value mismatch
I created a new Local branch to work on UI stuff from called UI_Phase2. You or I can delete the UI remote branch because it should not be a remote branch.
Also, I dunno why my local branch is known by Github I thought it would be provate to me.
I got three seperate build issues with the follwoing three classes. not really sure why all of a sudden it didn't work. Can you make a alteration to those three a commit and push them to see if that fixes it?
Invalid ZIP archive: src/uw/cse/dineon/library/Reservation.java [in DineOnLibrary]
Invalid ZIP archive: src/uw/cse/dineon/library/RestaurantInfo.java [in DineOnLibrary]
Invalid ZIP archive: src/uw/cse/dineon/library/User.java [in DineOnLibrary]
Find out if check style is capable of designing our code standard. Possibly extract a CheckStyle format file that we could all plug in to our eclipse instances.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.