You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Bending Spoons we like to have our own version of most the UIKit's elements and Katana is very in line with this philosophy.
That said, this is not something we can ask to people that use Katana. In particular Apple provides a widely used view controllers that are used for navigation within iOS applications (e.g., TabBar, NavigationController, ...).
It is totally possible to wrap these view controllers in Katana descriptions and expose an interface to use them. We should provide an example for the community that acts as a starting point for this kind of situations. I suggest to use the navigation example since it is most likely the most common one.
Note that we have a fully declarative, Katana based solution for navigation, but we is not public (yet) because it is at the moment strongly tied to internal conventions and technologies. Moreover it doesn't really solve the problem of using UIKit view controllers, so it isn't a real solution to this issue.
The text was updated successfully, but these errors were encountered:
In Bending Spoons we like to have our own version of most the UIKit's elements and Katana is very in line with this philosophy.
That said, this is not something we can ask to people that use Katana. In particular Apple provides a widely used view controllers that are used for navigation within iOS applications (e.g., TabBar, NavigationController, ...).
It is totally possible to wrap these view controllers in Katana descriptions and expose an interface to use them. We should provide an example for the community that acts as a starting point for this kind of situations. I suggest to use the navigation example since it is most likely the most common one.
Note that we have a fully declarative, Katana based solution for navigation, but we is not public (yet) because it is at the moment strongly tied to internal conventions and technologies. Moreover it doesn't really solve the problem of using UIKit view controllers, so it isn't a real solution to this issue.
The text was updated successfully, but these errors were encountered: