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
Is there any particular android limitation that forces the downloader process to be started and ran from a second Activity? Would it be possible for the Service to be started from the main plugin instance and managed there.
The reason I ask it that I could see it beneficially for integrators to be able to display progress however they want in their cordova-based HTML UI. I could see the plugin simply emitting events to interested listeners and notifying when it's done:
However, I am curious how to implement this giving the current branching model because it will possibly break the plugin for integrators on the old way of doing it. I'd be glad to take stab at it, but I first wanted to get some feedback on some of these issues and perhaps a some guidance on how (and if) you'd like to see it written.
Thanks!
The text was updated successfully, but these errors were encountered:
Is there any particular android limitation that forces the downloader process to be started and ran from a second Activity? Would it be possible for the Service to be started from the main plugin instance and managed there.
Probably not... might need a lot of code work, though.
As long as it doesn't break backwards compatibility, feel free to work on the 6.5 branch. It wouldn't be a good idea imo to create two versions of this plugin for one version of Cordova. You could add a flag (default 0?) or something. It's (almost?) the same as 5.3.1-auto.
Is there any particular android limitation that forces the downloader process to be started and ran from a second
Activity
? Would it be possible for theService
to be started from the main plugin instance and managed there.The reason I ask it that I could see it beneficially for integrators to be able to display progress however they want in their cordova-based HTML UI. I could see the plugin simply emitting events to interested listeners and notifying when it's done:
However, I am curious how to implement this giving the current branching model because it will possibly break the plugin for integrators on the old way of doing it. I'd be glad to take stab at it, but I first wanted to get some feedback on some of these issues and perhaps a some guidance on how (and if) you'd like to see it written.
Thanks!
The text was updated successfully, but these errors were encountered: