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
Previously accessing this singleton instance would take care of the attaching to the UIWindow, and creating a new UIWindow required to display it's User Interface.
I understand the motivation for this change, which was to remove the use of accessing UIKit specific methods directly, such that Bellerophon was usable within App Extensions. And I agree with the removal of the Singleton. But I believe that the public facing API for Bellerophon lost out on this change, and now the consuming application is required to initialize it's own instance of a Bellerophon Manager by passing in a UIWindow.
As a consumer of this framework I now need to handle logic that I believe is within the domain of the framework itself, and not the app like - "What if there is no key UIWindow (it's an optional property)?"
I suppose I'm asking - is there any way that we can remove this friction between the Client Application and Bellerophon, so that setup is simple, and Bellerophon takes care of these details for me?
The text was updated successfully, but these errors were encountered:
It also looks like the delegate method receivedError(error:) was added to BellerophonManagerDelegate but the documentation doesn't provide any additional detail about when this function is called?
/// The app is notified when a error was received.
///
/// - Parameter error: The error received.
func receivedError(error: NSError)
It would be great if we could update the documentation here. As our project is upgrading the version of Bellerophon used, and this method has since been added, but we are unable to determine how we are expected to handle this function from the headers itself - without digging into the implementation details.
Way back when there was a change made to the project which removed the
sharedInstance
of BellerophonManager. https://github.com/prolificinteractive/Bellerophon/pull/17/filesPreviously accessing this singleton instance would take care of the attaching to the UIWindow, and creating a new UIWindow required to display it's User Interface.
I understand the motivation for this change, which was to remove the use of accessing UIKit specific methods directly, such that Bellerophon was usable within App Extensions. And I agree with the removal of the Singleton. But I believe that the public facing API for Bellerophon lost out on this change, and now the consuming application is required to initialize it's own instance of a Bellerophon Manager by passing in a UIWindow.
As a consumer of this framework I now need to handle logic that I believe is within the domain of the framework itself, and not the app like - "What if there is no key UIWindow (it's an optional property)?"
I suppose I'm asking - is there any way that we can remove this friction between the Client Application and Bellerophon, so that setup is simple, and Bellerophon takes care of these details for me?
The text was updated successfully, but these errors were encountered: