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

chore: update tab bar icons for selected unselected states #81

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

saeedbashir
Copy link

Update the tan bar icons for selected and unselected states as per the design team feedback
image

@rnr
Copy link
Collaborator

rnr commented Sep 25, 2024

@saeedbashir
If we want to be mergeable with upstream, we don't need to replace the icons in that PR, right? We could split the tab icons into _acive and _inactive, but leave the upstream icons there. And replace them with a Whitelabvel script. What do you think?

@moiz994
Copy link

moiz994 commented Sep 25, 2024

@rnr agreed, if we can easily do a white label script that would be good since there is a difference in icons used by schema and 2U.
@HamzaIsrar12 did we decide on the discovery icon?

@saeedbashir
Copy link
Author

@rnr agreed, if we can easily do a white label script that would be good since there is a difference in icons used by schema and 2U. @HamzaIsrar12 did we decide on the discovery icon?

In that case, we will have the same icon for the selected/unselected states for the upstream which doesn't looks good even for making the case. I believe we have already discussed it with Axim and they were ok with the approach. The only thing that will come under discussion while pushing to upstream will be the icons for tabs.

In my opinion. we will update the icons in the codebase, and while pushing it to upstream we will see whether the like the icons or not. If not then we will have different copies for upstream and edX.

@rnr
Copy link
Collaborator

rnr commented Sep 25, 2024

@rnr agreed, if we can easily do a white label script that would be good since there is a difference in icons used by schema and 2U. @HamzaIsrar12 did we decide on the discovery icon?

In that case, we will have the same icon for the selected/unselected states for the upstream which doesn't looks good even for making the case. I believe we have already discussed it with Axim and they were ok with the approach. The only thing that will come under discussion while pushing to upstream will be the icons for tabs.

In my opinion. we will update the icons in the codebase, and while pushing it to upstream we will see whether the like the icons or not. If not then we will have different copies for upstream and edX.

@saeedbashir
if "I believe we have already discussed it with Axim and they were ok with the approach" then there is not a problem to have "the same icon for the selected/unselected states" - when they decided which icons they want they will just replace it. But all this time upstream icon will look as earlier.

@moiz994
Copy link

moiz994 commented Sep 26, 2024

@rnr I think we can use the same icon that Schema is using. I also think their icon and our icon is the same as per the figma file. For them, the selected and unselected state is a value added for schema. When this PR goes to RG, they can either accept our icons or we can accept theirs no need to maintain different icon sets. It might add complexity for now.

We can look at a white label script later.

public static let learnActive = ImageAsset(name: "learn_active")
public static let learnInactive = ImageAsset(name: "learn_inactive")
public static let profileActive = ImageAsset(name: "profile_active")
public static let profileInactive = ImageAsset(name: "profile_inactive")
public static let programs = ImageAsset(name: "programs")

Choose a reason for hiding this comment

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

There are two modes of TabView mentioned in MainScreenView.swift

  • list
  • gallery

In list view, we should also add selected and unselected states:

.tabItem {
  CoreAssets.programs.swiftUIImage.renderingMode(.template)
  Text(CoreLocalization.Mainscreen.programs)
}

If we are not going to maintain list view then we should entirely remove list view related icons and changes.

WDYT?

Copy link
Author

@saeedbashir saeedbashir Oct 3, 2024

Choose a reason for hiding this comment

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

The list view is not our need nor the axim, both providers are using gallery view. If any provider wants to use it, they can configure (open PR) according to their need.

@saeedbashir saeedbashir merged commit 746d3d1 into 2U/develop Oct 3, 2024
3 checks passed
@saeedbashir saeedbashir deleted the saeed/LEARNER-10142 branch October 3, 2024 05:25
rnr added a commit that referenced this pull request Dec 17, 2024
* feat: banner when register with already linked social account (#54)

* fix: fix lint warnings

* chore: added banner when register with already linked social account

* style: changed text color

---------

Co-authored-by: Anton Yarmolenko <[email protected]>

* chore: fix after merge

* chore: update tab bar icons for selected unselected states (#81)

* chore: Elm theme improvements on Profile (#82)

* chore: fix after merge

* fix: fix tab bar color not properly applying (#85)

* fix: fix tar bar color not properly applying
* chore: parity with android for discover icon

* chore: added missed colors

---------

Co-authored-by: Anton Yarmolenko <[email protected]>
Co-authored-by: Saeed Bashir <[email protected]>
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.

4 participants