aboutsummaryrefslogtreecommitdiff
path: root/foray.xcodeproj (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Loading overlay to custom class + add to coordinatorNicholas Tay2022-03-211-0/+4
| | | | | | | Just an idea I had, since it was quite messy that a TableViewController was handling all that. Instead now it should be reusable through the ForayCoordinator itself, which means e.g. on details screen, we can show the loading overlay.
* First try at implementing coordinator patternNicholas Tay2022-03-211-0/+8
| | | | | Resources: - https://www.hackingwithswift.com/articles/71/how-to-use-the-coordinator-pattern-in-ios-apps
* Allow >=iOS 13.0Nicholas Tay2022-03-201-0/+2
|
* Split structs into other file, split networking outNicholas Tay2022-03-201-0/+8
| | | | | | It isn't much so far, as it is just effectively the API retrieval function extracted from the TableViewController. But this should also allow other VCs to get from API too if required :^)
* Merge ForayNewDetailView into the VC itselfNicholas Tay2022-03-191-4/+0
| | | | | | | | Not sure if this is the right move, but it felt extraneous to have a whole UIView to itself for now. Instead just have it right inside the VC. Probably a step in the wrong direction though, but will need to review.
* Storyboard is GONENicholas Tay2022-03-191-31/+4
| | | | | | | | | Note - I had to fo into the Target settings -> Info -> Custom iOS Target Properties -> adjust the Application Scene Manifest there. Resources: - https://ioscoachfrank.com/remove-main-storyboard.html - https://stackoverflow.com/questions/25167458/changing-navigation-title-programmatically
* Detail view is now programatically createdNicholas Tay2022-03-191-0/+4
| | | | | Using SnapKit and some experimentation around the VC. Next step is to change segue and then maybe get rid of storyboard all together.
* Split table view cell into separate fileNicholas Tay2022-03-181-0/+4
| | | | | | | | | Cell no longer uses prototypes as registered in the Storyboard. Instead is a custom class inheriting the UITableViewCell and is manually registered by the VC. This is a first step towards reimplementing the prototype cells. Only has one label at the moment.
* Added SnapKit with Swift package managerNicholas Tay2022-03-182-0/+41
| | | | | | | | | | | | | | | | Was thinking of using CocoaPods as that's what is in use, but either way looked decently straightforward. Decided to start with whatever was already built in and no extra software. Note: it was File > Add Packages > put git link in top right. References I saw seemed to say File > Swift Packages and I couldn't find it. Also some other docs had older screenshots, I presume it's pre-Xcode-13 being slightly different. References: - https://developer.apple.com/documentation/swift_packages/adding_package_dependencies_to_your_app - https://www.raywenderlich.com/7242045-swift-package-manager-for-ios - https://snapkit.io/docs/
* Add gitignore, remove new ignoresNicholas Tay2022-03-161-14/+0
| | | | Luckily it was only one file
* Add a detail viewNicholas Tay2022-03-161-0/+4
| | | | | Resources: - https://guides.codepath.com/ios/Using-UITableView (was a bit dated)
* Learning UITableViewController: array data + custom cellsNicholas Tay2022-03-141-4/+6
| | | | | | Forgot to commit after finishing just the using array data bit. So committing with the custom cells done. https://www.ralfebert.com/ios-examples/uikit/uitableviewcontroller/
* Initial CommitNicholas Tay2022-03-144-0/+394