Re: Plugin discussion: Feature detection

2015-08-11 Thread Carlos Santana
No objections, move forward and create a Github Issue :-p - Carlos Sent from my iPhone On Aug 11, 2015, at 7:56 PM, Shazron shaz...@gmail.com wrote: If no one has any objections, there should be a JIRA issue tracking this task so it doesn't get lost or forgotten. On Thu, Jul 23, 2015 at

Re: Plugin discussion: Feature detection

2015-08-11 Thread Shazron
If no one has any objections, there should be a JIRA issue tracking this task so it doesn't get lost or forgotten. On Thu, Jul 23, 2015 at 6:49 AM, Carlos Santana csantan...@gmail.com wrote: +1 cordova-js have the logic to handle this at bootstrap, it's a matter of staring for a few minutes to

Re: Plugin discussion: Feature detection

2015-07-22 Thread Carlos Santana
+1 cordova-js have the logic to handle this at bootstrap, it's a matter of staring for a few minutes to see what are the entry points that Jesse describe. For the plug and play scenario, where you plugin something way after deviceready/bootstrap then something dynamic to query for the

Re: Plugin discussion: Feature detection

2015-07-21 Thread Jesse
There are a couple different ways to go about this, but ultimately the mechanisms are already there. 1. WaitForInit If you look at the cordova-device plugin, it pre-populates data about the device it is running on, and this info is available when the deviceready event fires. Essentially the

Plugin discussion: Feature detection

2015-07-20 Thread Rob Paveza
We chatted briefly about this at the hangout last week, and I wanted to continue on the discussion. I gave the example that the Quirks section of CameraOptions [1] is longer than the actual API documentation. I like to pick on the Camera plugin because it's one of the most-used and is very