cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: The plugin repos and reality
Date Wed, 03 Apr 2013 18:24:49 GMT
We can file infra requests to modify names / add more repos for plugins as
needed, so that shouldn't be an issue. Some plugins may not be completely
cross-platform (debug console, for example, will likely only have iOS
native code).

As for landing it all in 2.7: also not a big deal. We can try to get it
done for 2.8. Or 2.9. Hopefully for 3.0 :)

It seems reasonable to extract code that is commonly used by various
plugins into some kind of a Cordova utils class (or something). Since
you're starting down this path already Joe, you probably have the clearest
idea of where to go from here. Perhaps start writing down the issues you
see in a new wiki page, and then we can all take a look and come up with
some kind of proposal for a blessed Java API for cordova-android? The
other platforms I'm sure will come across similar (but maybe not exactly
the same) issues so this is a good exercise to go through earlier rather
than later.

On 4/3/13 2:17 PM, "Joe Bowser" <> wrote:

>I've started moving the various Android plugins into their
>corresponding repositories, and it seems that these were made up, and
>that they don't really correspond to what exists in the code today.  I
>don't think that it's realistic for us to get this done for 2.7
>because there are certain plugins that don't have a home (i.e. App,
>Compass, AudioPlayer, Echo) and others that don't make any sense to
>have (i.e. Console, Vibration) or are unclear (Media).
>Also, at least for Android, we're going to have to nail down a Java
>API.  Many of the plugins use some common code for file manipulation
>such as the Capture, Camera and of course the File APIs. It would be
>good to actually expose them to plugin developers so that we're all on
>the same page as to where files should and should not go.
>It would have been good to create the repositories based on what we
>already have implemented more or less, and to go from there.  That
>being said, I don't know if there is a one-to-one mapping between
>Android and iOS components, let alone any of the other platforms.
>Anyone else have thoughts on this?

View raw message