Alright, +1 to creating a cordova-plugins repo as an alternative to new
repos for every possible plugin (plugman and registry have for a while
supported git subdirectories so we don't need repo isolation). However, I
would also be fine with just using cordova-labs plugin branch, especially
once plugin registry has pointers to repo location based on metadata, so it
really does not matter where they live.
I would also +1 a generic preferences plugin over something ios-specific,
though the other two really do seem better to be ios specific (although
there may be an android-keyboard plugin at some point, developers may not
necessarily want to use both).
-Michal
On Fri, Oct 18, 2013 at 1:59 PM, Jesse <purplecabb...@gmail.com> wrote:
> If you namespace it to the platform, and later it makes sense to support it
> on another device, you will have even more issues.
> I think the best approach mentioned is the cordova-plugins repo which is
> like the wild-west that is purplecabbage/phonegap-plugins except it is
> managed by cordova contributors only.
>
> Another alternative is to create a generic 'preferences' plugin which IS
> supported by all platforms, BUT the actual preferences differ between
> platforms.
>
> Something like:
> navigator.cordovaPreferences.setPreference('iOS-GapBetweenPages",0);
>
>
>
> @purplecabbage
> risingj.com
>
>
> On Fri, Oct 18, 2013 at 10:45 AM, David Kemp <drk...@google.com> wrote:
>
> > I would hate to see plugins that are currently ios only get put there,
> and
> > then later have another platform supported. That would be ugly.
> >
> > Can we at least insist that any plugin that goes in the ios platform
> have a
> > name like ios-* (likewise for other platforms)
> >
> >
> > On Fri, Oct 18, 2013 at 1:07 PM, Michal Mocny <mmo...@chromium.org>
> wrote:
> >
> > > +1 to metadata for repo location.
> > >
> > > However, I'm still not 100% why these plugins should live in the
> platform
> > > repo? Its just an arbitrary container, right? I think the fact thats
> > its
> > > a plugin is more relevant than the fact that they only support ios. If
> > > cordova-labs doesn't feel right, then why not make a single
> > cordova-plugins
> > > repo? I know we used to have a phonegap-plugins repo and we didn't
> like
> > > that, but thats because it had external contributions and unsupported
> > stale
> > > code.
> > >
> > > It doesn't really matter I guess, but I just don't see the point of
> > having
> > > seperated out all of the plugins into separate repos and now we shove
> > some
> > > back alongside platforms.
> > >
> > > -Michal
> > >
> > >
> > > On Thu, Oct 17, 2013 at 7:32 PM, Shazron <shaz...@gmail.com> wrote:
> > >
> > > > Also, to avoid any "git entanglements" with trying to keep history
> > > between
> > > > the two repos (it's possible but I'm not at level of git black-belt
> > yet),
> > > > I'm just going to copy the folders in, and add them.
> > > >
> > > >
> > > > On Thu, Oct 17, 2013 at 4:11 PM, Shazron <shaz...@gmail.com> wrote:
> > > >
> > > > > I propose moving these iOS only plugins to the cordova-ios repo,
> and
> > > > > adding the corresponding components in JIRA (ios-statusbar,
> > > ios-keyboard)
> > > > > for issue tracking.
> > > > > With https://issues.apache.org/jira/browse/CB-5026 - plus these
> two
> > > > > plugins, that would make a total of three plugins in cordova-ios
> > > > (probably
> > > > > in a plugins subfolder)
> > > > >
> > > > > Also, would be great to add the extra meta-data (new tags?) to
> > > > plugins.xml
> > > > > to show which repo this comes from, where issues are supposed to
> go.
> > I
> > > > > believe we discussed this in the hangout.
> > > > >
> > > > >
> > > >
> > >
> >
>
