Skip to content

Code review2 payton#20

Open
turnbopd wants to merge 9 commits intomasterfrom
Code-review2_Payton
Open

Code review2 payton#20
turnbopd wants to merge 9 commits intomasterfrom
Code-review2_Payton

Conversation

@turnbopd
Copy link
Copy Markdown
Collaborator

@turnbopd turnbopd commented Apr 5, 2022

This is my code review 2 due Tuesday

@turnbopd
Copy link
Copy Markdown
Collaborator Author

turnbopd commented Apr 5, 2022

Analysis of the program:

Overall, I made progress on the Interface side of the application.

  • Added text edit search bars for user to be able to search. Added buttons for search as well.
  • figured out color hex for design so I was able to try different colors
  • Fixed my main activity file. Last code review I had errors so I corrected them.

Was the program available in UC Github on time:
Yes

Is the program documented/commented well enough for you to understand:
Yes
Does the program compile:
Yes
Rationale behind your changes:
I had to change the Main_Activity.kt file because it was errors and didn't have any of the interface items that were needed like the button and edit text. I was working on the colors in the kt file but then I realized I should have been working on it in the xml file so I worked on it in there as well as the main_activity.xml file.

Commit Links
07ac54d
7c91be3
7ad0749
5b7801c

@turnbopd
Copy link
Copy Markdown
Collaborator Author

turnbopd commented Apr 5, 2022

specific technical concepts :

Learned setClickListener used for buttons
How to do navigation toolbar (still learning but getting there)

@turnbopd turnbopd marked this pull request as ready for review April 5, 2022 21:28
@turnbopd
Copy link
Copy Markdown
Collaborator Author

turnbopd commented Apr 5, 2022

5b7801c

Comments for this commit:

Still trying to figure out the navigation bar and how to make it work properly. Kept getting errors when trying to implement it

@turnbopd
Copy link
Copy Markdown
Collaborator Author

turnbopd commented Apr 5, 2022

07ac54d

Comments for this commit:
These are test colors. Found a helpful source that show color palettes that attract users and are flattering.

@turnbopd
Copy link
Copy Markdown
Collaborator Author

turnbopd commented Apr 5, 2022

7ad0749

Comments for this commit:
Fixed the errors that were in the previous code review. I added user input i think but I have to retest it with out the errors. Need to figure out the code that goes into the button. What it should do when the user clicks.

Comment on lines +26 to +31
// your code to perform when the user clicks on the button

result.text = "the $name was released in $year"


Toast.makeText(this@MainActivity, "You clicked me.", Toast.LENGTH_SHORT).show()
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This looks like an incomplete feature.
Are you using these anywhere?
If not in use, remove them. Keep the codebase as small as possible to do the job you want to do. Unused code is clutter, and bad documentation, which increases technical debt.
Only complete features, which meet the team's Definition of Done, should be merged to Main/Master.

Comment on lines +1 to +11
package com.example.mymovieinfo.ui.theme
import androidx.compose.foundation.shape.RoundedCornerShape
import androidx.compose.material.Shapes
import androidx.compose.ui.unit.dp

val Shapes =Shapes(
small = RoundedCornerShape(4.dp),
medium = RoundedCornerShape(5.dp),
large = RoundedCornerShape(0.dp)
//add more shapes
) No newline at end of file
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It looks like this group is using XML layouts. If that's the case, Compose themes will not be used, and this can be discarded.

Comment on lines +5 to +7
val Silver100 = Color(0xFFF0FFFF)
//Figure out hex color values for various colors
//create theme file to use text type, color, and shape data
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It looks like this group is using XML layouts. If that's the case, Compose themes will not be used, and this can be discarded.

Comment on lines +9 to +14
val Typography = Typography(
body1 = TextStyle(
fontFamily = FontFamily.SansSerif,
fontWeight = FontWeight.Normal,
fontSize = 16.sp
//add back up set of typography just in case
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It looks like this group is using XML layouts. If that's the case, Compose themes will not be used, and this can be discarded.

@discospiff
Copy link
Copy Markdown

I lean against merging this branch, as:

  • It introduces incomplete functionality.
  • It adds Compose themes, and the group is not using Compose.

New functionality should be kept in a separate branch until it is complete and meets the team's Definition of Done. Thus, if the team would like these features, they can keep the branch open and continue to work on it, and then merge once it meets the Definition of Done. Otherwise, if they do not want these changes, they can abandon/delete this branch and not merge it.

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.

2 participants