-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unified diary screen #870
Unified diary screen #870
Conversation
Pulled out functionality from the InfiniteDiaryListCtrl into the new module, 'infscrolltripitem'. This new scope includes the surveyOpt, itemHt, and showDetail function for the new directive. This relates to issue e-mission#740, Unifying label and diary views.
Created a new module for a diary item directive. Pulled out the necessary functions; created the diary_list_item.html as a template for the directive.
These changes include the stylistic changes to the css layout of the unified diary screen, changes to the multi-label button layout, changes to the java script of the trip item directive, and removing the diary tab from the bottom ion-tab. Issues - - reading in the trip percentages; When I attempted to use the DiaryHelper.getPercentages in converting the trip object to geojson in the trip item directive, the tripgj did not have a sections attribute. I then went into services to see if I could add this, and then I went down a rabbit hole of different functions missing different attributes. I will attempt to fix this soon.
@tyleryandt18 I don't see the commit history from the savoir-faire linux codebase. Please note my comment:
without the commit history, we don't know the reason for each change, and we can't easily make additional changes. It is very tempting from a coding perspective to check in a giant commit with tons of changes, but it is very problematic from a maintenance perspective. |
@tyleryandt18 Can you also indicate the testing that you did? In particular, does the draft functionality actually work? My guess is not. |
@shankari I'm not sure on how to merge the Savoir Faire Linux commit history. If I didn't fork the repo from them, then I'm not sure how to merge from them. If you could please outline some steps, then I can go ahead and fetch their commit history. A lot of the functionality testing is visual. I tested it on both Android and iOS. For example, the in-line map is there, the date breaks are there, the filter tabs still work, and the showDetail() function still works. I will make sure to include lots of in-code testing for the date selector that I implement over the weekend! This is how I tested the isDraft. I know it's elementary, but I'm not sure how else to test it. It displays false for each trip, which at least leads me to believe that the function is setting trip.isDraft to something. Now, I don't have any drafted trips so I'm not sure how to test the flip side of that. |
I would pull into a new branch just to ensure that you are not messing up your current changes, and then copy over your changes from this branch into the new branch. |
Are you sure you don't have draft trips? Take a trip that ends at around 30 mins after the hour and then check the diary immediately afterwards. The trip should stay as draft for the next 30 mins at least. |
Can you also upload a video showing that the android version works? Even if you scroll by clicking on the map... |
Here is the Android Screen Recording: |
@shankari I can't seem to figure out how to get the commit history with git pull. My mamobilite repo is in Documents/GitHub/mamobilite, and my phone repo is in Documents/GitHub/e-mission-phone. When I do git pull, it says that the mamabolite Dev branch does not exist, and when I list out the branches that I have access to with git branch -r, it doesn't appear there either. This makes sense to me, but I'm not sure how to then pull their commit history. |
what is the actual command that you used? |
|
You need to use the remote repo
|
Not yet added displaying the trips only for that date
I just returned from the gym, and OpenPATH on my phone records a drafted trip, but not the devapp. This occurs on both the master branch and my Unified Diary Screen branch. Furthermore, I use |
That's because the data is still on your phone. Wait ~ 5 mins to push the data, or manually "force sync". Then, in the window between the data being pushed to the server and the pipeline running (at 15 mins past the hour), the trip will show up as draft in the devapp as well. Note that after the pipeline runs, the trip will no longer be draft. So you have ~ 45 min chunks to work on the feature. If you were running this against a server on your local laptop, you could control when the pipeline runs. Not sure if you want to make that change to your setup for now, though. |
That's why I suggested that you make the changes in a separate branch. Did you make your new branch from You can also ask them to merge everything from master -> a branch on their repo so you could pull from it. But I don't know if they can do this over the weekend. Or you can resolve the merge conflicts that you have; they are probably fairly simple - your choice! Note that if you don't resolve the merge conflicts now, then they will have to deal with them when they pull our changes, which is a disincentive to pull our changes and will lead to diverging code branches. you are not done with the change unless it has the commit history from savoirfairelinux. I would do this first before making additional changes and leading to even more merge conflicts |
LMK when you are done fixing the commit history and the draft trips. I'd hoped you would be able to figure why the percentages don't work, but at this point, I might just have to tell you the answer and make some server-side changes. |
Current update, just so that is documented on this GitHub thread. @shankari knows that I am unable to log onto my work laptop, but since OpenPATH is opensource, I can access my changes from my personal laptop. I have created a branch that has pulled the commit history from SavoirFaireLinux. I then merged the conflicts manually, and then pulled the changes from this branch, committed, so that the branch has the commit history and my changes made. I recall that there was an issue with this new branch, but am now unable to recover and investigate that issue since I am locked out of my work laptop. I will now test it on my personal laptop, but I don't know how to convert line endings from dos to unix to run the shell scripts to setup and activate the server. Investigating now. |
I have gone through all of these options to try and convert the line endings in order to run a server, but to no avail. I can submit a pr for the branch that has the commit history and changes on it, but I know for a fact that there was an issue when I tried to run it. I can also merge the branches again, but at the current moment, I am unable to test the code. This is why I had switched to a Mac work laptop. |
|
I have ran it on a Cygwin terminal and a Windows command prompt. Quite honestly I'm not sure what the difference between the two are, but I believe that they both execute Linux. |
|
I was able to run |
I don't see any output from you should get something like
Did you get any other errors? If not, you may need to install node.js 14.7.0 manually since probably nvm doesn't work for windows After installing node.js manually, you should comment out everything between these lines:
in and try to set up again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good overall.
I have not recommended any substantive changes, since we don't have time to make them anyway. My comments are primarily around making it easier for others to pick this up later, and focus on:
- describing the rationale for the changes,
- removing commented out code
- justifying the addition of new dependencies
Please make sure to handle the "25 hidden comments" as well.
@tyleryandt18 After you address all these comments, and you finish the pull from saviorfairelinux + resolving merge conflicts, please re-test with multiple form factors and submit screenshots. See the form factor comments. |
Glad to see that you have made some changes. However, just to re-clarify the expectation:
|
#91d4ff -> #80D0FF
@shankari wrt to the issues that I am having running a server, the package that is missing, according to the debugger console, is |
I found a similar issue here. e-mission/e-mission-docs#275. But when I run |
$#$#$# windows |
Preaching to the choir. Here is the results. |
one is a javascript file. The other (in spite of the file extension) is a bash script. |
@shankari Android Studio and Windows has not been kind to me. I have a poor quality laptop, so I don't know if that is the issue here or not. I have set looking at my laptop for the past hour. My android emulator is continuously trying to connect to the server, alternating between the "tap to cancel" screen and "extracting" screen. I successfully launched the app earlier, but I switched over to a different branch. I had pulled the from the savoir faire linux branch onto said branch, then pulled my Unified-Diary-Branch onto said branch, and now am trying to test it just to ensure the merging worked fine. But I cannot test it if my computer cannot connect to the server. I don't know what to do, it simply is stuck trying to connect, and there are no console log errors. I have to wake up at 5 tomorrow for my flight, so I am done for tonight. |
@tyleryandt18 please:
|
Thank you @sebastianbarry! It was a pleasure working this summer with both of you! Thank you for all your assistance. |
@sebastianbarry thank you so much for doing this @tyleryandt18 definitely owes you one! Now, can you also make sure that the changes in the related PR (with the Ma Mobilitie changes) work? For example, I seem to remember that Ma Mobilitie had used an action sheet instead of a popup; that might be a change that we want to keep from their side, as our mode string lengths keep increasing ("e-car, with others") is pretty long. |
@sebastianbarry, @tyleryandt18 has already done most of this in #871 |
@sebastianbarry since @tyleryandt18's internship has ended, can you make the following changes?
Let's merge this such, so we don't have lots of pending PRs sitting around, and then address the remaining unification changes in separate PRs. |
I made the below changes in this Commit
I am not sure how to add this commit to the PR however, because I don't have access to edit Tyler's |
I made the below change in this Commit
I DID NOT add the new label screen directive in the old diary screen in the interest of time because it was taking me a while to figure out. Also, if we are planning on eventually getting rid of the old Diary screen and incorporating it into this new improved Label (with the Diary screen built in) screen, then it may be a waste of time trying to figure this out. With this and my previous Commits, we should be good to ship this as-is for testing. Then... Next steps
|
So that we can close this PR, I created a new updated PR on this same issue, containing the changes I made to the branch: [New] Unified diary screen (adapted from Tyleryandt18's Unified diary screen) #883 |
Closing this since it is superceded by #883 |
Here is my PR with the current response to Tyler's code review: #883 There are still a handfull of things to go over; any conversation that doesn't end in Confirmed this change as complete still needs to be addressed. |
Changes Include:
Still working on implementing the date selector.
Issues: