Hmm didn't think about JavaScript - the easiest is obfuscation with Closure or something (with exclusions for cordova objects).
On Tue, Jun 18, 2013 at 7:30 AM, Ken Wallis <kwal...@blackberry.com> wrote: > On BB10, that native side gets compiled into a .so file that you would > distribute. > > Of course there is still the javascript side. Depends on which side of the > plugin you are worried about IP in. > -- > > Ken Wallis > > Product Manager – WebWorks > > BlackBerry > > 289-261-4369 > > ________________________________________ > From: Simon MacDonald [simon.macdon...@gmail.com] > Sent: Tuesday, June 18, 2013 7:14 AM > To: dev@cordova.apache.org > Subject: Re: Plugins and IP > > Same deal on Android except you would use a jar or if UI is involved a > library project. > Simon Mac Donald > http://hi.im/simonmacdonald > > > On Tue, Jun 18, 2013 at 10:07 AM, Shazron <shaz...@gmail.com> wrote: > > Forgot to mention, you should build the lib as a fat binary with all > > architectures, don't forget i386 if your users plan to test on the > Simulator > > > > > > On Tue, Jun 18, 2013 at 7:04 AM, Shazron <shaz...@gmail.com> wrote: > > > >> For iOS plugins, compile the source as a lib (.a file). For example, in > >> the TestFlightPlugin I include TestFlight's lib: > >> https://github.com/shazron/TestFlightPlugin > >> https://github.com/shazron/TestFlightPlugin/blob/master/plugin.xml#L35 > >> > >> and provide the headers of course > >> > >> > >> On Tue, Jun 18, 2013 at 6:42 AM, Wargo, John <john.wa...@sap.com> > wrote: > >> > >>> Any recommendations on the best way to implement plugins while > protecting > >>> the source code? Our development teams are trying to figure out the > most > >>> efficient way to deliver Cordova plugins to our customers but hide the > IP > >>> and I would like to learn how others are managing this. > >>> > >>> > >> > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. >
