Closed themetalone closed 8 years ago
Was this part of the requirements for this iteration?
If you are working on this (it's active), please add it instead of the "where is my bus" button on the home screen. If not, I can take care of it now.
Did i make it active? Sry my Bad. I thought it to be since how should the User know that He/she will be picked up
Dominik Skalník notifications@github.com schrieb am Mo., 27. Juni 2016, 13:32:
Was this part of the requirements for this iteration?
If you are working on this (it's active), please add it instead of the "where is my bus" button on the home screen. If not, I can take care of it now.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GSE-Project/SS2016-group2/issues/102#issuecomment-228721172, or mute the thread https://github.com/notifications/unsubscribe/AH2kADCccn1_qdSoqaQdPPWNHMwYfy4qks5qP7TfgaJpZM4I-_sX .
Now we have a basic request state page. We cannot do more until the server provides us more information. I'm postponing this to the next iteration.
Development on branch 102_request_page
I found that the current structure in the data logic is insufficent. I'll perform some major changes for the request states
I think that we should drop the persistance of requests on the client. Rather we should access the Requests States from the Server when needed
I implemented the requestChange into the datalogic. This is ready to integrate into the UI.
The request page updates upon pulling down. This works with the current G1 Server
I'm done with my additions
I'm going to do the colors later today.
We're still missing a page where the user sees the state of his/her requests
Update 28.06.2016