-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Add tvOS support [partially completed] #28
Comments
whoever starts on this, just a tip: I pulled from git and started my own local pod spec. Had to make the following changes:
The xib in the project is an iOS xib that prevents TVOS from compiling. Once I excluded it from the pod everything seemed to compile just fine. Testing now. |
As a followup: maybe ResourceStatusOverlay.xib (and maybe related code) should be moved into a subspec called ResourceStatusOverlayIOS |
It would be very beneficial if it could work on watchOs as well. Being able to build one api client for all platforms would be a tremendous improvement EDIT: Actually WatchKit includes way of getting data through the iOS app so it's ok if it's dismissed for now. tvOS would be amazing to get tho. Can we split Siesta and SiestaUI ? |
That was my understanding, but…
I’m all for it if anyone finds a need for it.
I’d welcome a pull request.
Already done. Isolating UIKit code was done by @onekiloparsec for the macOS target, and I already split SiestaUI for SwiftPM support. Siesta & SiestaUI are now two separate subdirectories under Source, separate targets in the Xcode project, separate modules if you build with SwiftPM or Carthage, and separate subspecs if you’re using Cocoapods. I’m only aware of two spots in the core Siesta module that require platform-specific attention: the type of parsed images, and the name of the low memory notification. Both should be easy to resolve. Search |
Looks like maybe @tritt was working on tvOS support? |
#187 added a tvOS target. Specs don’t run on tvOS because of Nocilla, but that seems solvable. I'd like to hear from users about any success / troubles in actual apps before declaring this supported. (See checklist at the top of the issue.) |
(Looks like @djz-code may be working on this on a fork?)
The text was updated successfully, but these errors were encountered: