Skip to content
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

Ui changes steph #112

Merged
merged 37 commits into from
Mar 19, 2017
Merged

Ui changes steph #112

merged 37 commits into from
Mar 19, 2017

Conversation

superpowers11
Copy link
Collaborator

@superpowers11 superpowers11 commented Mar 7, 2017

Here is the first round of UI changes.

I haven't touched the overlays for a signature, and I think swap components might look a little weird. But I have made a good number of changes in general, so I thought I would put this out in case you guys want to give feedback or merge stuff with master so that we can make sure the new code and functionality, which we are adding elsewhere, conforms to the new UI setup.

UPDATE:

  • This is a beta version, but I think it is good to merge. In fact, I think we should merge sooner rather than later, as it is getting more and more laborious to merge conflicts with master.
  • I did some changing of the messages displayed for signatures, depending on what's been signed. So take a look and see what you think. I found it a little confusing that a text input box (albeit a disabled one) was still being displayed after someone had already signed, and a submit button was still available, even though there was nothing to submit. Thus, I switched it so that instead they get a friendly message saying they've already signed. And their only option is a back button.

@eanyanwu
Copy link
Member

eanyanwu commented Mar 7, 2017

I too, can get behind a gradual rolling out of ui changes.

@eanyanwu
Copy link
Member

eanyanwu commented Mar 8, 2017

Oh boy new commits...trying them on now...

@eanyanwu
Copy link
Member

I'm thinking I should just merge this.
So far, it is looking good (I did find a bug with the modal poping up when it shouldn, but that should be an easy fix).
By merging it, I can easily integrate it to the rest of my branches.
If that is ok by you peeps, I'll be merging it within the next two days.

@superpowers11
Copy link
Collaborator Author

I just closed it, so that I can reopen it when it is actually ready. But if you want to merge what was there, feel free.

@superpowers11
Copy link
Collaborator Author

I think this is good to go for now and should be merged. I am sure there is more improvement that can happen, but we should probably go ahead and merge it in.

@superpowers11 superpowers11 reopened this Mar 19, 2017
@eanyanwu
Copy link
Member

Do you want to resolve the conflicts or should I?

@superpowers11
Copy link
Collaborator Author

Conflicts resolved! #conflictresolutionstrategies #growexperienceserve #reslife

@eanyanwu
Copy link
Member

eanyanwu commented Mar 19, 2017

Is the search icon supposed to be outside the search box?
capture d ecran 2017-03-19 a 07 58 17

EDIT: Actually...we don't need a search button....since the search updates dynamically. Feel free to remove the button.?

Copy link
Member

@eanyanwu eanyanwu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, this look real good. Excited to have it be our new UI.
HOWEVER, there are few things that are currently broken. I tried to track them down to find the reason and I've commented as such below.
Checkout works pretty well as far as I’ve tested!
I haven't tested Swap Components yet since Input is not currently saving.

@@ -1,8 +1,10 @@
@model Phoenix.Models.Rci

@{
ViewBag.Title = "Damage Input";
ViewBag.Title = "Damage Input: " + TempData["user"];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't work...think about when the RA is logged in and viewing someone else's RCI.
Solutions:

  • Pass the name of the user from the controller, using a view bag.
  • Use a view model :)



/* Add a div to the right component. This div will contain a :
<p> element displaying a damage
<input> hidden element that will be used when submitting the form
*/
function addDamage(componentID) {
var pElement = "<p class='divAddOn-field new-damage'>" + $("#text-input-" + componentID).val() + "</p><i class='divAddOn-item material-icons' onclick='deleteNewDamages(event, this);'>delete</i>";
var pElement = "<p class=damage-element new-damage'>" + $("#text-input-" + componentID).val() + "</p><i class='material-icons' onclick='deleteNewDamages(event, this);'>close</i>";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You forgot a quote... consequence: damages don't save 🙅

@@ -0,0 +1,45 @@
@model Phoenix.Models.ViewModels.CheckoutRciViewModel
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you add an index view page to RciCheckout 0_) ?

<input class="divAddOn-item adding-fines" type="number" placeholder="2.00" id="fine-amount-input-@component.RciComponentID" />
<button class="divAddOn-item" onclick="addFine(@component.RciComponentID);" id="add-@component.RciComponentID">Add</button>
</div>
<div class="div-list" id="div-list-@component.RciComponentID">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think when stuff was moved around, the id got renamed?
It's supposed to be fine-list-@component.RciComponentID
I use it as a hook to know where to insert new fines. Currently nothing happens when you click Add

</ul>
}

<div class="view" data="@Model.GordonID">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should probably still have this <div> tag wrapping everything. It contain a data attribute which stores the person's ID which is used by rci-checkout.js.


<div>

@if (Model.GordonID == ViewBag.GordonID)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ViewBag.GordonID isn't set anywhere... this displays the wrong overlay when the RA is logged in.

@eanyanwu
Copy link
Member

eanyanwu commented Mar 19, 2017

Steph said I could push directly to solve the issues outlined.
Don't be scared by the number of commits. They are all just one-liners.
I separated them so it will be clear what was done.
I'll continue testing this throughout the day and will merge once done.

Copy link
Member

@eanyanwu eanyanwu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Second batch of reviews
EDIT: These have now been solved.

}

function RASigSubmit() {
var rciSig = "";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here. (This might be more of Rachel's error)
The RA never has three input fields to fill. Yet you get three values. This means that sometimes, depending on the situation, one or two of those values is going to be undefined. This isn't bad thing, except that it causes weird behavior in the SaveRASigs method in the RciInput Service when the RA is signing his own rci.
The gist of this comment is that we need to make sure than when the rci belongs to the RA, he signs both the CheckinSigRA and CheckinSigRes fields. Right now it doesn't do that :/

}

});
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You forgot to include the check() method for RDs that queues an rci to be signed 🙅‍♂️

@eanyanwu
Copy link
Member

The next commit is going to be simply styling tweaks, especially for mobile.

@eanyanwu
Copy link
Member

Sweet, I think we good now.
Tweaks:

  • Fix the weird Add button issue on smalls screens
  • Separated the color of divAddOn-vert from its layout ( I use that same class in common area checkouts, and the color didn't fit :/)
  • divAddOn-vert and divAddOn-vert-field were flipped in some places

@eanyanwu
Copy link
Member

Thanks Steph!
As I said in the previous comments, I hardly changed anything. It looks like I did a lot because I made commits for each thing I did just so you know what changed.
Merging now.

@eanyanwu eanyanwu merged commit afe43b9 into master Mar 19, 2017
@superpowers11
Copy link
Collaborator Author

superpowers11 commented Mar 19, 2017 via email

@superpowers11 superpowers11 mentioned this pull request Mar 20, 2017
@eanyanwu eanyanwu deleted the ui-changes-steph branch April 1, 2017 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants