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

Design for seed backup and move new wallet seed verification to after setup #502

Closed
wants to merge 9 commits into from

Conversation

macsleven
Copy link
Contributor

closes #461

@macsleven macsleven added this to In progress in dcrios board Jul 8, 2019
@macsleven macsleven marked this pull request as ready for review July 8, 2019 22:24
@macsleven macsleven moved this from In progress to Review in dcrios board Jul 8, 2019
@@ -29,7 +29,7 @@
<rect key="frame" x="0.0" y="0.0" width="414" height="896"/>
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<subviews>
<stackView hidden="YES" opaque="NO" contentMode="scaleToFill" axis="vertical" alignment="center" spacing="6" translatesAutoresizingMaskIntoConstraints="NO" id="EJZ-78-Rgs">
<stackView hidden="YES" opaque="NO" contentMode="scaleToFill" axis="vertical" alignment="center" spacing="8" translatesAutoresizingMaskIntoConstraints="NO" id="EJZ-78-Rgs">
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this spacing increased to 8? Have you considered how devices with shorter screen height will be affected by this change? I don't see this change as being necessary to the feature being added by this PR. Revert please.

<view hidden="YES" clipsSubviews="YES" contentMode="scaleToFill" translatesAutoresizingMaskIntoConstraints="NO" id="aaU-uk-JKT">
<rect key="frame" x="8" y="110.66666666666666" width="398" height="48"/>
<subviews>
<stackView opaque="NO" contentMode="scaleToFill" distribution="fillProportionally" alignment="center" translatesAutoresizingMaskIntoConstraints="NO" id="3zw-6M-uXq">
Copy link
Contributor

Choose a reason for hiding this comment

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

  • This StackView is the only child of the parent View. Tells me that the parent view element is unnecessary, why not use the StackView directly rather than embed it inside a View?

  • Also, this StackView holds a text and an image. Can't a button be used for this?

  • Summary, replace this view and stackview with a button

@@ -15,6 +15,8 @@ class OverviewViewController: UIViewController {
@IBOutlet weak var fetchingBalanceIndicator: UIImageView!
@IBOutlet weak var totalBalanceLabel: UILabel!
@IBOutlet weak var recentActivityTableView: UITableView!
@IBOutlet weak var backupWallet: UIView!
@IBOutlet weak var backupViewSpacing: UIView!
Copy link
Contributor

Choose a reason for hiding this comment

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

  • I don't really see a need for this IBOutlet
  • The view referenced by this IBOutlet was added before this PR and it's purpose was certainly not to space the newly added backup view. This tells me that this variable is named wrongly. Which further leads me to question its usage.

let tapGesture = UITapGestureRecognizer(target: self, action: #selector(backupSeedAction))
self.backupWallet.addGestureRecognizer(tapGesture)
self.backupWallet.isHidden = false
self.backupViewSpacing.isHidden = true
Copy link
Contributor

Choose a reason for hiding this comment

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

As alluded to in the preceding comment, I don't see why it is necessary to hide this spacing.

@macsleven
Copy link
Contributor Author

macsleven commented Nov 18, 2019

This issue is moved to version 2 UI #530

@macsleven macsleven closed this Nov 18, 2019
@macsleven macsleven removed this from Review in dcrios board Nov 25, 2019
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.

new seed verification process can take place after wallet use
3 participants