| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This is admittedly pretty hard for me to wrap my head around, and I'm
not even using background threading explicitly yet. Will improve.
|
| |
|
|
|
| |
In preparation for presenters to come in largely, lots of files starting
to go everywhere...
|
| |
|
|
|
| |
Also fixed the scrollview margins while I was at it - it looked weird
being so inside
|
| |
|
|
|
| |
Was a bit awkward to have it as a Date normalised to first day of the
year
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Didn't constrain details label to the bottom of the content container,
so scroll view didn't pick up on it (test with large font on a smaller
viewport phone).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pretty sure I'm meant to launch via SceneDelegate now, was confused by
that probably due to older tutorials. Read a bit about it and it seems
like it's due to multi-instance/screen support, so switched back to
doing it this 'new way'.
Was a bit confused but I think I deleted too much from Info.plist and
got rid of the 'Default Configuration' which launches the SceneDelegate.
I think we're good now though, had to reference a new template project.
References:
- https://sarunw.com/posts/how-to-create-new-xcode-project-without-storyboard/
|
| |
|
|
|
| |
Resources:
- https://www.hackingwithswift.com/articles/71/how-to-use-the-coordinator-pattern-in-ios-apps
|
| |
|
|
|
|
| |
Would make more sense as more lines get added in (especially if ui
elements programatically), as well as since horizontal layout is allowed
if the screen is small you can scroll
|
| |
|
|
|
|
| |
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 :^)
|
| |
|
|
| |
Missed in when ripping out storyboard
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
Using SnapKit and some experimentation around the VC. Next step is to
change segue and then maybe get rid of storyboard all together.
|
| |
|
|
|
|
| |
This took a bit to figure out due to the identifier stuff, but we got
there. I'd like to figure out how to push a VC into the navigation
controller though, rather than relying on storyboard segues.
|
| | |
|
| |
|
|
|
| |
Surely there still is a better way for the trailing constraints on the
labels?
|
| |
|
|
|
|
|
|
| |
I don't think this 100% is the correct way with SnapKit. Need to seek
advice and improve the constraints. However, an improvement over before
is that the accessibility font sizes actually do work as intended now!
Now to add back in the segues somehow...
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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/
|
| |
|
|
| |
Remembered I actually had a public server for me to dump files on lol
|
| | |
|
| |
|
|
|
|
| |
Makes it clear which parts are tightly coupled. I want to learn how to
make this more generic so I can try hooking into other APIs easily
(which make require different destructuring of JSON).
|
| |
|
|
|
|
|
|
|
| |
It might be my web server causing the weird caching with headers (it's
just a json file on nginx). Changing the policy in the request seems to
have fixed it though.
Refresh control references:
- https://stackoverflow.com/questions/24475792/how-to-use-pull-to-refresh-in-swift
|
| | |
|
| |
|
|
|
|
|
|
| |
I'm not 100% sure if this is the best way to do it, but it looks decent
and it works.
Resources:
- https://stackoverflow.com/questions/27960556/loading-an-overlay-when-running-long-tasks-in-ios
|
| |
|
|
|
| |
Resources:
- https://guides.codepath.com/ios/Using-UITableView (was a bit dated)
|
| |
|
|
|
|
|
| |
Resources:
- https://stackoverflow.com/questions/56443859/display-in-json-api-table-view-in-swift
- https://www.avanderlee.com/swift/json-parsing-decoding/
- https://stackoverflow.com/questions/24321165/make-rest-api-call-in-swift
|
| |
|
|
| |
Not sure if this is the correct way of switching into a different cell type with the prototypes, but it works. To review.
|
| |
|
|
| |
https://www.ralfebert.com/ios-examples/uikit/uitableviewcontroller/grouping-sections/
|
| |
|
|
|
|
| |
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/
|
| |
|
