cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <>
Subject Re: Plugman support for Android libraries
Date Tue, 13 May 2014 20:03:23 GMT
Makes sense. Before we lose track of this, best to file an issue:

... so it can be tracked and evaluated by the devs, and you can be notified.

Sign up here:!default.jspa


On Thu, May 8, 2014 at 6:53 AM, Martin Bektchiev <> wrote:

> Hi guys,
> I want to ask you for ideas about how would it be best to solve an issue
> that I'm facing. Sometimes a plugin's implementation depends on a native
> library, but there's no easy way to embed it as a .jar file in Android if
> the library has resources. Let's take
> and
> for example. The former one
> can't be automatically installed and requires manually adding the
> FacebookSDK library. While the latter one relies on a gross hack which
> copies the resource files to the Cordova application project and then
> dynamically finds their IDs instead of using the R.* class. This is far
> from optimal because it makes updating the underlying library a lot more
> difficult, adds a lot of overhead in the plugin.xml file, adds performance
> overhead at runtime for retrieving the IDs and most importantly doesn't
> always work (e.g. the plugin installation will fail if the app itself
> contains a res/values/colors.xml file).
> Instead of these approaches it would be much better if plugman was capable
> of adding library references itself. How do you think that this should be
> implemented? Is it a good idea to use the framework tag? Should the
> implementation depend on calling "android update project" or would it be
> better to directly edit the file?
> Any ideas and suggestions will be more than welcome! Looking forward to
> your thoughts!
> Best regards,
> Martin Bektchiev

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message