I send pull request to GitHub and explain my rationale for that implementaiton. https://github.com/apache/cordova-plugins/pull/5
2014-02-25 13:58 GMT+06:00 Shazron <shaz...@gmail.com>: > Core plugins exist in their own repo by themselves and are cross-platform > generally. Core plugins are also released weekly. > The StatusBar plugin has none of those attributes. cordova-plugins are > really "labs" kinda stuff. > > In any case, you could always fork the repo and send a pull request, we can > continue discussion there (Github) regarding its applicability/suitability. > > > On Mon, Feb 24, 2014 at 11:02 PM, Joe Bowser <bows...@gmail.com> wrote: > > > It's not in its own repo, that's the main difference. The iOS Status > > Bar and its adjustable opacity is unique to iOS. On Android, an app > > can either be Full Screen and block the notification bar, or non-full > > screen and have the notification bar appear. A config.xml setting > > doesn't need a special plugin. > > > > On Mon, Feb 24, 2014 at 10:39 PM, Tommy-Carlos Williams > > <to...@devgeeks.org> wrote: > > > Calling that not core seems a stretch (since it's in an apache cordova > > repo and all), but the maintainer is Shazron, as far as I know... if that > > helps. > > > > > > > > > > > > > > > On 25 Feb 2014, at 5:29 pm, Andrey Kurdumov <kant2...@googlemail.com> > > wrote: > > > > > >> I want to extend StatusBar plugin to support Android. And yesterday I > > file > > >> issue > > >> https://issues.apache.org/jira/browse/CB-6095. It was soon closed > with > > >> suggestion contact plugin maintainer, because StatusBar is not core > > plugin. > > >> Maybe I file issue incorrectly, and specify wrong component/ something > > >> else, not sure about this. > > >> But I clearly see the StatusBar plugin in > > >> https://github.com/apache/cordova-plugins repository which is clone > of > > >> git://git.apache.org/cordova-plugins.git > > >> Both seems to be belonging to Cordova project. > > >> > > >> I do have fix for this issue, and willing to contribute that back. > > >> What route should I take? > > > > > >
