-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Open tasks] Replace storyboards with code #15
Comments
Hi @misteu, I would like to work on this issue. |
Hi @InsanelyHarsh! Please tell me which screen you want to translate into code. I will create an issue and assign it to you. Have a great weekend! |
I think i will start with Add new Language View |
Assign me, I have replaced NewLanguageViewController with Code! |
Hi there and thank you! |
I am taking up the |
Hi @Kanishka3 ! Can you comment inside of the issue for this screen (#20)? I will assign it to you then. Actually, it is already assigned to somebody else but I don't think there wasn't any work done yet. Please comment there and maybe let's wait until tomorrow if he reacts. |
Alright. Replies there. I am almost halfway done with the task. |
all done! |
GOAL
Replace all the storyboards with UIs created via code.
For not having one really huge branch, this will be split up in issues on a screen basis!
If you are interested in working on some screen, please comment on any of the open subtasks listed below.
Subtasks
NewLanguageViewController
[Replace Storyboard] NewLanguageViewController #17
HomeScreenViewController
[Open Task] Replace storyboard for
HomeScreenViewController
with code. beginners-welcome #20LanguageScreenViewController
[Open Task] Replace storyboard for
LanguageScreenViewController
with code. #21AddNewWordViewController
[Open Task] Replace storyboard for
AddNewWordViewController
with code. #22Main.storyboard
references from the project, updateAppDelegate
.WHY
Storyboards are slow to load in Xcode and they are harder to maintain compared to plain code.
AC
There should not be any storyboards in the app.
Optional
First choice would be UIKit. It might make sense to also have a look whether it might make sense to start rewriting screens using SwiftUI. However, this will be way more work as it's a rewrite of everything.
The text was updated successfully, but these errors were encountered: