Vickcoo
Vickcoo
Hi @andrewtavis, I'd like to work on this! I think your idea makes sense, I might need to dive deeper and do more work to figure out what problems need...
@andrewtavis There's some new progress. Could you review it :)? The English keyboard is done, and I'll update the other keyboards once this idea gets approved. I'll create a new...
Hello @andrewtavis 👋🏻, I would like try to work on this.
So, do you mean we need to merge #476 before starting this issue, or do you just want me to reference it first? And I need a little time to...
Thanks for your patience and explanation @andrewtavis ! I got it. Let's discuss it further over there, Here's a summary of the steps as I understand them 1. solve the...
Hi @andrewtavis, I want to work on this issue :)
Maybe we can start from here [Extensions.swift](https://github.com/scribe-org/Scribe-iOS/blob/main/Keyboards/KeyboardsBase/Extensions.swift). Let's set things up and write simply unit tests to make sure everything is working well. Or you could suggest where would be...
@fabulouiOS-monk you're right! I saw the code, and it left me very confuse. So, should we write unit tests for the code that has class/struct first, or should we handle...
Hi @andrewtavis, I think we can work on the same directory(KeyboardBase), then choose the file that has a complete class or struct for the highest priority, like this [KeyboardStyling.swift](https://github.com/scribe-org/Scribe-iOS/blob/34db0f11885f8161f756245c2f30913fb1964e32/Keyboards/KeyboardsBase/KeyboardStyling.swift) @fabulouiOS-monk...