You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Brian LeRoux <b...@brian.io> on 2012/07/24 16:58:27 UTC

[DISCUSS] 2.x roadmap planning / first pass at api audit

Hey guys, i've just updated the wiki [1] with some near-term goals and
a first pass at the long desired core API audit. Essentially it notes
where things have moved forward in the standards process or, in some
cases, cordova specific upgrades we've discussed in the past.

Please discuss!

[1] http://wiki.apache.org/cordova/RoadmapProjects

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Paul Plaquette <pa...@linux.intel.com>.
A calendar API ?

it could be similar to the planned evolution for the contact API

http://dev.webinos.org/deliverables/wp3/Deliverable32/wiki$t3-2$List_of_phase_1_specifications.html

http://www.w3.org/TR/2011/WD-calendar-api-20110419/

-
Paul


On 07/24/2012 04:58 PM, Brian LeRoux wrote:
> Hey guys, i've just updated the wiki [1] with some near-term goals and
> a first pass at the long desired core API audit. Essentially it notes
> where things have moved forward in the standards process or, in some
> cases, cordova specific upgrades we've discussed in the past.
>
> Please discuss!
>
> [1] http://wiki.apache.org/cordova/RoadmapProjects
>

-- 
Paul Plaquette
Senior Software Engineer
Open Source Technology Center
Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Jesse <pu...@gmail.com>.
Paul,

I would expect the navigator.getUserMedia API to be the route for capture.
There is a good writeup here;
http://www.html5rocks.com/en/tutorials/getusermedia/intro/

WebAudio is really cool, but way more power than what you would need
for simply playing back an audio file.
I think is safe to expect that there will be several sound apis based
on different uses.
iOS has 4+ ways of playing audio, based on the type of access you need
to the buffer, what type of processing you need to do, and so on.

Cheers,
  Jesse

On Mon, Jul 30, 2012 at 2:34 AM, Paul Plaquette
<pa...@linux.intel.com> wrote:
> hi Brian,
>
> I saw  this note on Media:
>
> Media: requires further audit
> https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html
>
> While porting the current cordova  notification manager and then media to
> tizen, I tried to use the HTML5 audio tag, and W3C Web audio API.
>
> With both we cannot yet record a sound. Both are not yet implementing
> recording.
> With Web Audio API  the issue is we cannot  starts/pause and restarts the
> sound where it was stopped as we have to actually recreated the play sound
> buffer. Of course this might evolve depending on implementations.
>
> Does some one has a deeper knowledge with these sound APIs?
>
> Regards,
>
> Paul
>
>
>
>
> On 07/24/2012 04:58 PM, Brian LeRoux wrote:
>>
>> Hey guys, i've just updated the wiki [1] with some near-term goals and
>> a first pass at the long desired core API audit. Essentially it notes
>> where things have moved forward in the standards process or, in some
>> cases, cordova specific upgrades we've discussed in the past.
>>
>> Please discuss!
>>
>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>
>
> --
> Paul Plaquette
> Senior Software Engineer
> Open Source Technology Center
> Intel Corp.,Montpellier, France



-- 
@purplecabbage
risingj.com

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Paul Plaquette <pa...@linux.intel.com>.
hi Brian,

I saw  this note on Media:

Media: requires further audit 
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html

While porting the current cordova  notification manager and then media 
to tizen, I tried to use the HTML5 audio tag, and W3C Web audio API.

With both we cannot yet record a sound. Both are not yet implementing 
recording.
With Web Audio API  the issue is we cannot  starts/pause and restarts 
the sound where it was stopped as we have to actually recreated the play 
sound buffer. Of course this might evolve depending on implementations.

Does some one has a deeper knowledge with these sound APIs?

Regards,
Paul




On 07/24/2012 04:58 PM, Brian LeRoux wrote:
> Hey guys, i've just updated the wiki [1] with some near-term goals and
> a first pass at the long desired core API audit. Essentially it notes
> where things have moved forward in the standards process or, in some
> cases, cordova specific upgrades we've discussed in the past.
>
> Please discuss!
>
> [1] http://wiki.apache.org/cordova/RoadmapProjects
>

-- 
Paul Plaquette
Senior Software Engineer
Open Source Technology Center
Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Brian LeRoux <b...@brian.io>.
I think html-media-capture is the DOM variant of the programmatic getUserMedia

Eg, this:

<input type="file" accept="image/*" capture="camera">

Instead of:

 navigator.getUserMedia({audio:true, video:true}, console.log)

On Wed, Jul 25, 2012 at 4:01 PM, Shazron <sh...@gmail.com> wrote:
> Brian - So am I correct that it should be HTML Media Capture? (see quoted)
>
> On Tue, Jul 24, 2012 at 2:08 PM, Shazron <sh...@gmail.com> wrote:
>> Under Core API audit / Capture:
>> -> that link points to an obsolete doc, which points to
>> http://dev.w3.org/2011/webrtc/editor/getusermedia.html
>>
>> Which appears to be under the webrtc umbrella (note the url). That is
>> perhaps my confusion (from the other thread). I'm wondering if it
>> should be HTML Media Capture instead or is this another thing? see:
>> http://www.w3.org/TR/html-media-capture/
>>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Shazron <sh...@gmail.com>.
Brian - So am I correct that it should be HTML Media Capture? (see quoted)

On Tue, Jul 24, 2012 at 2:08 PM, Shazron <sh...@gmail.com> wrote:
> Under Core API audit / Capture:
> -> that link points to an obsolete doc, which points to
> http://dev.w3.org/2011/webrtc/editor/getusermedia.html
>
> Which appears to be under the webrtc umbrella (note the url). That is
> perhaps my confusion (from the other thread). I'm wondering if it
> should be HTML Media Capture instead or is this another thing? see:
> http://www.w3.org/TR/html-media-capture/
>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Paul Plaquette <pa...@linux.intel.com>.
Hi,

What about having a messaging API (SMS MMS mail)?

Tizen is proposing a messaging API [1]
W3C [2]and Webinos too [3]

[1] - 
https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
[2]- http://www.w3.org/TR/messaging-api/
[3] - http://dev.webinos.org/specifications/draft/messaging.html

-
Paul

On 07/25/2012 10:06 AM, Shazron wrote:
> Also, Windows Phone 8 phones will be NFC equipped as well, with API
> support (Windows.Networking.Proximity) - which we will eventually
> support I reckon.
>
> On Wed, Jul 25, 2012 at 1:04 AM, Shazron <sh...@gmail.com> wrote:
>> I think this warrants some discussion to be put on the roadmap, esp
>> since Android has a NFC API (there is a Cordova plugin here:
>> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/),
>> and the rumour is the iPhone 5 (this fall) will have one as well.
>>
>> Don't know if any committers are involved with the standards bodies to
>> get an API discussion going with the w3c.
>>
>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>> <pa...@linux.intel.com> wrote:
>>> Any NFC  web APIs support?
>>>
>>> Tizen owns a NFC API  [1]
>>>
>>> I am not sure W3C is having a draft for an API yet (2]
>>> Webinos  is having one - Webinos is a European  Consortium [3]
>>>
>>> [1] -
>>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>>
>>>
>>>
>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>>>>>> a first pass at the long desired core API audit. Essentially it notes
>>>>>>>> where things have moved forward in the standards process or, in some
>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>>>
>>>>>>>> Please discuss!
>>>>>>>>
>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>>>
>>>>>>>
>>>>
>>>
>>> --
>>> Paul Plaquette
>>> Senior Software Engineer
>>> Open Source Technology Center
>>> Intel Corp.,Montpellier, France
>

-- 
Paul Plaquette
Senior Software Engineer
Open Source Technology Center
Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Shazron <sh...@gmail.com>.
Also, Windows Phone 8 phones will be NFC equipped as well, with API
support (Windows.Networking.Proximity) - which we will eventually
support I reckon.

On Wed, Jul 25, 2012 at 1:04 AM, Shazron <sh...@gmail.com> wrote:
> I think this warrants some discussion to be put on the roadmap, esp
> since Android has a NFC API (there is a Cordova plugin here:
> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/),
> and the rumour is the iPhone 5 (this fall) will have one as well.
>
> Don't know if any committers are involved with the standards bodies to
> get an API discussion going with the w3c.
>
> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
> <pa...@linux.intel.com> wrote:
>> Any NFC  web APIs support?
>>
>> Tizen owns a NFC API  [1]
>>
>> I am not sure W3C is having a draft for an API yet (2]
>> Webinos  is having one - Webinos is a European  Consortium [3]
>>
>> [1] -
>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>
>>
>>
>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>
>>>>>>
>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>>>>> a first pass at the long desired core API audit. Essentially it notes
>>>>>>> where things have moved forward in the standards process or, in some
>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>>
>>>>>>> Please discuss!
>>>>>>>
>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>>
>>>>>>
>>>
>>
>> --
>> Paul Plaquette
>> Senior Software Engineer
>> Open Source Technology Center
>> Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Dave Johnson <da...@gmail.com>.
brian are you suggesting we use the same couchdb setup etc as npm is
using (i.e. we fork it) or we actually work on top of the existing npm
registries?

On Thu, Jul 26, 2012 at 11:38 AM, Brian LeRoux <b...@brian.io> wrote:
> So, interestingly the Node dudes have expressed they are ok w/ us
> experimenting w/ the npm registry for our plugin-discovery mechanism.
> This is really great news as that it saves us from having to bikeshed
> the service api, user auth, tech choices, etc. Our CLI tooling is
> already Node so reuse w/ the npm library will be straightforward.
>
> We can bootstrap on top of registry.npmjs.org which is really just an
> Apache CouchDB instance (yay) which means that the system is
> effectively federated by its technical nature, which is to say, that
> anyone can run a registry (which likely we will see happen; speaking
> for Adobe I know we will want to host officially sanctioned plugins
> for the phonegap dist).
>
> So this is good stuff. We are actually not far from plugin discovery,
> creation, validation, publication, installation, and removal!
>
> It is not without some irony that this also means our plugin packaging
> format will be package.json ---which really has bad symmetry with our
> current config/manifest file being config.xml. (I think its fine, for
> now, but something we should discuss.)
>
> Fil/Anis: need to drop the new CLI prototype into labs (soon?)
>
> Bryce: super agree on new APIs being a bit sketchy in their early
> phases. Another win for this plugin reality is that we remove a whole
> tonne of responsibility from the core cordova codebase and can start
> getting super funky with our API experimentation.
>
>
> On Wed, Jul 25, 2012 at 8:09 PM, Bryce Curtis <cu...@gmail.com> wrote:
>> I think the near-term looks fine.  What I consider most important on
>> the list are the plug-in metafiles and config files.  A close second
>> would be the plug-in management tools that will consume/produce these
>> files.  With that said, we probably won't be using the command line
>> tools, so having the metafiles well documented will be important.
>>
>> Next in importance will be to update current plug-ins to latest APIs.
>>
>> As for adding new APIs, I would only caution against implementing
>> early specs that change frequently - lessons learned from the
>> contacts, device and other APIs.   One thing to consider is that the
>> more plug-ins we ship with Cordova, the more we have to maintain &
>> test for each release... and that the goal should be to equally
>> support functionality across the major platforms for each first-class
>> plug-in.
>>
>>
>> On Wed, Jul 25, 2012 at 6:54 PM, Michael Brooks
>> <mi...@michaelbrooks.ca> wrote:
>>> The 2.x roadmap looks good.
>>>
>>> I've moved the "config manifest" under "Nearterm" because it should be
>>> tackled at the same time as plugin-install / remove.
>>>
>>> Michael
>>>
>>> On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com> wrote:
>>>
>>>> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
>>>> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
>>>> adding Tizen and WP8 support once we get the devices.
>>>>
>>>> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
>>>> > NFC def an important emerging tech. Added it to the backlog with a
>>>> > note about the w3c group:
>>>> > http://www.w3.org/wiki/Near_field_communications_(NFC)
>>>> >
>>>> >
>>>> >
>>>> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
>>>> > <pa...@linux.intel.com> wrote:
>>>> >> hi,
>>>> >>
>>>> >> with NFC,  another API that might be of interest is a payment API
>>>> several
>>>> >> groups are proposing one or working on it.  W3C has a working group,
>>>> >> Webinos an API
>>>> >>
>>>> >> http://www.w3.org/ECommerce/Micropayments/
>>>> >> http://dev.webinos.org/specifications/draft/payment.html
>>>> >>
>>>> >> -
>>>> >> Paul
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On 07/25/2012 10:04 AM, Shazron wrote:
>>>> >>>
>>>> >>> I think this warrants some discussion to be put on the roadmap, esp
>>>> >>> since Android has a NFC API (there is a Cordova plugin here:
>>>> >>>
>>>> >>>
>>>> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/
>>>> ),
>>>> >>> and the rumour is the iPhone 5 (this fall) will have one as well.
>>>> >>>
>>>> >>> Don't know if any committers are involved with the standards bodies to
>>>> >>> get an API discussion going with the w3c.
>>>> >>>
>>>> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>>>> >>> <pa...@linux.intel.com> wrote:
>>>> >>>>
>>>> >>>> Any NFC  web APIs support?
>>>> >>>>
>>>> >>>> Tizen owns a NFC API  [1]
>>>> >>>>
>>>> >>>> I am not sure W3C is having a draft for an API yet (2]
>>>> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
>>>> >>>>
>>>> >>>> [1] -
>>>> >>>>
>>>> >>>>
>>>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>>>> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>>>> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term
>>>> goals
>>>> >>>>>>>>> and
>>>> >>>>>>>>> a first pass at the long desired core API audit. Essentially it
>>>> >>>>>>>>> notes
>>>> >>>>>>>>> where things have moved forward in the standards process or, in
>>>> some
>>>> >>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>> >>>>>>>>>
>>>> >>>>>>>>> Please discuss!
>>>> >>>>>>>>>
>>>> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>> Paul Plaquette
>>>> >>>> Senior Software Engineer
>>>> >>>> Open Source Technology Center
>>>> >>>> Intel Corp.,Montpellier, France
>>>> >>>
>>>> >>>
>>>> >>
>>>> >> --
>>>> >> Paul Plaquette
>>>> >> Senior Software Engineer
>>>> >> Open Source Technology Center
>>>> >> Intel Corp.,Montpellier, France
>>>>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Patrick Mueller <pm...@gmail.com>.
On Thu, Jul 26, 2012 at 2:38 PM, Brian LeRoux <b...@brian.io> wrote:

> So, interestingly the Node dudes have expressed they are ok w/ us
> experimenting w/ the npm registry for our plugin-discovery mechanism.
> This is really great news ...
>

I love being able to reuse the npm commands/structure for our plugins - one
less thing for us to invent.  But I don't think using a registry will work
in practice for our "built in" plugins.  The way I've pictured this is that
when you d/l a Cordova build, you get all our existing "built in" plugins
with the download.  And then you can add/remove from that set.  You should
also be able to add/remove from other places, and npmjs.org would be a
great place to move existing content to, that currently exists in
github/phonegap-plugins.

But maintaining the built-in plugins in npmjs.org seems like it's going to
be a bit of a pain to me.


> It is not without some irony that this also means our plugin packaging
> format will be package.json ---which really has bad symmetry with our
> current config/manifest file being config.xml. (I think its fine, for
> now, but something we should discuss.)
>

So, it's weird, having JSON and XML as "config files".  But frankly, having
XML files as "config files" just seems weirder every day to me.  :-)

As a final note, using "node package standards" means we can likely make
use of Browserify, for folks that want to optimize their JS, or otherwise
are happy with a "build" (like me).  Doing a build means I can put a single
script/src in my html, and then just do a build to concat all the modules
together.  And if you care, Browserify also includes some node-compatible
packages like events.

The one thing about using Browserify is that we'll need to allow for our
require() to be swapped out with Browserify's, as theirs is more complete
than ours.

-- 
Patrick Mueller
http://muellerware.org

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Filip Maj <fi...@adobe.com>.
Anis your pushed killed all the history :(

On 7/26/12 11:52 AM, "Anis KADRI" <an...@gmail.com> wrote:

>CLI tool is in incubator-cordova-labs/cordova-client branch
>I will be adding my changes to it soon.
>
>On Thu, Jul 26, 2012 at 11:38 AM, Brian LeRoux <b...@brian.io> wrote:
>
>> So, interestingly the Node dudes have expressed they are ok w/ us
>> experimenting w/ the npm registry for our plugin-discovery mechanism.
>> This is really great news as that it saves us from having to bikeshed
>> the service api, user auth, tech choices, etc. Our CLI tooling is
>> already Node so reuse w/ the npm library will be straightforward.
>>
>> We can bootstrap on top of registry.npmjs.org which is really just an
>> Apache CouchDB instance (yay) which means that the system is
>> effectively federated by its technical nature, which is to say, that
>> anyone can run a registry (which likely we will see happen; speaking
>> for Adobe I know we will want to host officially sanctioned plugins
>> for the phonegap dist).
>>
>> So this is good stuff. We are actually not far from plugin discovery,
>> creation, validation, publication, installation, and removal!
>>
>> It is not without some irony that this also means our plugin packaging
>> format will be package.json ---which really has bad symmetry with our
>> current config/manifest file being config.xml. (I think its fine, for
>> now, but something we should discuss.)
>>
>> Fil/Anis: need to drop the new CLI prototype into labs (soon?)
>>
>> Bryce: super agree on new APIs being a bit sketchy in their early
>> phases. Another win for this plugin reality is that we remove a whole
>> tonne of responsibility from the core cordova codebase and can start
>> getting super funky with our API experimentation.
>>
>>
>> On Wed, Jul 25, 2012 at 8:09 PM, Bryce Curtis <cu...@gmail.com>
>> wrote:
>> > I think the near-term looks fine.  What I consider most important on
>> > the list are the plug-in metafiles and config files.  A close second
>> > would be the plug-in management tools that will consume/produce these
>> > files.  With that said, we probably won't be using the command line
>> > tools, so having the metafiles well documented will be important.
>> >
>> > Next in importance will be to update current plug-ins to latest APIs.
>> >
>> > As for adding new APIs, I would only caution against implementing
>> > early specs that change frequently - lessons learned from the
>> > contacts, device and other APIs.   One thing to consider is that the
>> > more plug-ins we ship with Cordova, the more we have to maintain &
>> > test for each release... and that the goal should be to equally
>> > support functionality across the major platforms for each first-class
>> > plug-in.
>> >
>> >
>> > On Wed, Jul 25, 2012 at 6:54 PM, Michael Brooks
>> > <mi...@michaelbrooks.ca> wrote:
>> >> The 2.x roadmap looks good.
>> >>
>> >> I've moved the "config manifest" under "Nearterm" because it should
>>be
>> >> tackled at the same time as plugin-install / remove.
>> >>
>> >> Michael
>> >>
>> >> On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com>
>> wrote:
>> >>
>> >>> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
>> >>> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
>> >>> adding Tizen and WP8 support once we get the devices.
>> >>>
>> >>> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
>> >>> > NFC def an important emerging tech. Added it to the backlog with a
>> >>> > note about the w3c group:
>> >>> > http://www.w3.org/wiki/Near_field_communications_(NFC)
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
>> >>> > <pa...@linux.intel.com> wrote:
>> >>> >> hi,
>> >>> >>
>> >>> >> with NFC,  another API that might be of interest is a payment API
>> >>> several
>> >>> >> groups are proposing one or working on it.  W3C has a working
>>group,
>> >>> >> Webinos an API
>> >>> >>
>> >>> >> http://www.w3.org/ECommerce/Micropayments/
>> >>> >> http://dev.webinos.org/specifications/draft/payment.html
>> >>> >>
>> >>> >> -
>> >>> >> Paul
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On 07/25/2012 10:04 AM, Shazron wrote:
>> >>> >>>
>> >>> >>> I think this warrants some discussion to be put on the roadmap,
>>esp
>> >>> >>> since Android has a NFC API (there is a Cordova plugin here:
>> >>> >>>
>> >>> >>>
>> >>>
>> 
>>http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-applic
>>ation-with-phonegap/
>> >>> ),
>> >>> >>> and the rumour is the iPhone 5 (this fall) will have one as
>>well.
>> >>> >>>
>> >>> >>> Don't know if any committers are involved with the standards
>> bodies to
>> >>> >>> get an API discussion going with the w3c.
>> >>> >>>
>> >>> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>> >>> >>> <pa...@linux.intel.com> wrote:
>> >>> >>>>
>> >>> >>>> Any NFC  web APIs support?
>> >>> >>>>
>> >>> >>>> Tizen owns a NFC API  [1]
>> >>> >>>>
>> >>> >>>> I am not sure W3C is having a draft for an API yet (2]
>> >>> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
>> >>> >>>>
>> >>> >>>> [1] -
>> >>> >>>>
>> >>> >>>>
>> >>>
>> 
>>https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.ap
>>i.device%2Ftizen%2Fnfc.html
>> >>> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>> >>> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>> >>> >>>>
>> >>> >>>>
>> >>> >>>>
>> >>> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some
>>near-term
>> >>> goals
>> >>> >>>>>>>>> and
>> >>> >>>>>>>>> a first pass at the long desired core API audit.
>>Essentially
>> it
>> >>> >>>>>>>>> notes
>> >>> >>>>>>>>> where things have moved forward in the standards process
>>or,
>> in
>> >>> some
>> >>> >>>>>>>>> cases, cordova specific upgrades we've discussed in the
>>past.
>> >>> >>>>>>>>>
>> >>> >>>>>>>>> Please discuss!
>> >>> >>>>>>>>>
>> >>> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>
>> >>> >>>>
>> >>> >>>> --
>> >>> >>>> Paul Plaquette
>> >>> >>>> Senior Software Engineer
>> >>> >>>> Open Source Technology Center
>> >>> >>>> Intel Corp.,Montpellier, France
>> >>> >>>
>> >>> >>>
>> >>> >>
>> >>> >> --
>> >>> >> Paul Plaquette
>> >>> >> Senior Software Engineer
>> >>> >> Open Source Technology Center
>> >>> >> Intel Corp.,Montpellier, France
>> >>>
>>


Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Filip Maj <fi...@adobe.com>.
Yay anis you fixed it! Thank you :D

On 7/26/12 11:52 AM, "Anis KADRI" <an...@gmail.com> wrote:

>CLI tool is in incubator-cordova-labs/cordova-client branch
>I will be adding my changes to it soon.
>
>On Thu, Jul 26, 2012 at 11:38 AM, Brian LeRoux <b...@brian.io> wrote:
>
>> So, interestingly the Node dudes have expressed they are ok w/ us
>> experimenting w/ the npm registry for our plugin-discovery mechanism.
>> This is really great news as that it saves us from having to bikeshed
>> the service api, user auth, tech choices, etc. Our CLI tooling is
>> already Node so reuse w/ the npm library will be straightforward.
>>
>> We can bootstrap on top of registry.npmjs.org which is really just an
>> Apache CouchDB instance (yay) which means that the system is
>> effectively federated by its technical nature, which is to say, that
>> anyone can run a registry (which likely we will see happen; speaking
>> for Adobe I know we will want to host officially sanctioned plugins
>> for the phonegap dist).
>>
>> So this is good stuff. We are actually not far from plugin discovery,
>> creation, validation, publication, installation, and removal!
>>
>> It is not without some irony that this also means our plugin packaging
>> format will be package.json ---which really has bad symmetry with our
>> current config/manifest file being config.xml. (I think its fine, for
>> now, but something we should discuss.)
>>
>> Fil/Anis: need to drop the new CLI prototype into labs (soon?)
>>
>> Bryce: super agree on new APIs being a bit sketchy in their early
>> phases. Another win for this plugin reality is that we remove a whole
>> tonne of responsibility from the core cordova codebase and can start
>> getting super funky with our API experimentation.
>>
>>
>> On Wed, Jul 25, 2012 at 8:09 PM, Bryce Curtis <cu...@gmail.com>
>> wrote:
>> > I think the near-term looks fine.  What I consider most important on
>> > the list are the plug-in metafiles and config files.  A close second
>> > would be the plug-in management tools that will consume/produce these
>> > files.  With that said, we probably won't be using the command line
>> > tools, so having the metafiles well documented will be important.
>> >
>> > Next in importance will be to update current plug-ins to latest APIs.
>> >
>> > As for adding new APIs, I would only caution against implementing
>> > early specs that change frequently - lessons learned from the
>> > contacts, device and other APIs.   One thing to consider is that the
>> > more plug-ins we ship with Cordova, the more we have to maintain &
>> > test for each release... and that the goal should be to equally
>> > support functionality across the major platforms for each first-class
>> > plug-in.
>> >
>> >
>> > On Wed, Jul 25, 2012 at 6:54 PM, Michael Brooks
>> > <mi...@michaelbrooks.ca> wrote:
>> >> The 2.x roadmap looks good.
>> >>
>> >> I've moved the "config manifest" under "Nearterm" because it should
>>be
>> >> tackled at the same time as plugin-install / remove.
>> >>
>> >> Michael
>> >>
>> >> On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com>
>> wrote:
>> >>
>> >>> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
>> >>> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
>> >>> adding Tizen and WP8 support once we get the devices.
>> >>>
>> >>> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
>> >>> > NFC def an important emerging tech. Added it to the backlog with a
>> >>> > note about the w3c group:
>> >>> > http://www.w3.org/wiki/Near_field_communications_(NFC)
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
>> >>> > <pa...@linux.intel.com> wrote:
>> >>> >> hi,
>> >>> >>
>> >>> >> with NFC,  another API that might be of interest is a payment API
>> >>> several
>> >>> >> groups are proposing one or working on it.  W3C has a working
>>group,
>> >>> >> Webinos an API
>> >>> >>
>> >>> >> http://www.w3.org/ECommerce/Micropayments/
>> >>> >> http://dev.webinos.org/specifications/draft/payment.html
>> >>> >>
>> >>> >> -
>> >>> >> Paul
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On 07/25/2012 10:04 AM, Shazron wrote:
>> >>> >>>
>> >>> >>> I think this warrants some discussion to be put on the roadmap,
>>esp
>> >>> >>> since Android has a NFC API (there is a Cordova plugin here:
>> >>> >>>
>> >>> >>>
>> >>>
>> 
>>http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-applic
>>ation-with-phonegap/
>> >>> ),
>> >>> >>> and the rumour is the iPhone 5 (this fall) will have one as
>>well.
>> >>> >>>
>> >>> >>> Don't know if any committers are involved with the standards
>> bodies to
>> >>> >>> get an API discussion going with the w3c.
>> >>> >>>
>> >>> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>> >>> >>> <pa...@linux.intel.com> wrote:
>> >>> >>>>
>> >>> >>>> Any NFC  web APIs support?
>> >>> >>>>
>> >>> >>>> Tizen owns a NFC API  [1]
>> >>> >>>>
>> >>> >>>> I am not sure W3C is having a draft for an API yet (2]
>> >>> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
>> >>> >>>>
>> >>> >>>> [1] -
>> >>> >>>>
>> >>> >>>>
>> >>>
>> 
>>https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.ap
>>i.device%2Ftizen%2Fnfc.html
>> >>> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>> >>> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>> >>> >>>>
>> >>> >>>>
>> >>> >>>>
>> >>> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some
>>near-term
>> >>> goals
>> >>> >>>>>>>>> and
>> >>> >>>>>>>>> a first pass at the long desired core API audit.
>>Essentially
>> it
>> >>> >>>>>>>>> notes
>> >>> >>>>>>>>> where things have moved forward in the standards process
>>or,
>> in
>> >>> some
>> >>> >>>>>>>>> cases, cordova specific upgrades we've discussed in the
>>past.
>> >>> >>>>>>>>>
>> >>> >>>>>>>>> Please discuss!
>> >>> >>>>>>>>>
>> >>> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>>>>
>> >>> >>>>>
>> >>> >>>>
>> >>> >>>> --
>> >>> >>>> Paul Plaquette
>> >>> >>>> Senior Software Engineer
>> >>> >>>> Open Source Technology Center
>> >>> >>>> Intel Corp.,Montpellier, France
>> >>> >>>
>> >>> >>>
>> >>> >>
>> >>> >> --
>> >>> >> Paul Plaquette
>> >>> >> Senior Software Engineer
>> >>> >> Open Source Technology Center
>> >>> >> Intel Corp.,Montpellier, France
>> >>>
>>


Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Anis KADRI <an...@gmail.com>.
CLI tool is in incubator-cordova-labs/cordova-client branch
I will be adding my changes to it soon.

On Thu, Jul 26, 2012 at 11:38 AM, Brian LeRoux <b...@brian.io> wrote:

> So, interestingly the Node dudes have expressed they are ok w/ us
> experimenting w/ the npm registry for our plugin-discovery mechanism.
> This is really great news as that it saves us from having to bikeshed
> the service api, user auth, tech choices, etc. Our CLI tooling is
> already Node so reuse w/ the npm library will be straightforward.
>
> We can bootstrap on top of registry.npmjs.org which is really just an
> Apache CouchDB instance (yay) which means that the system is
> effectively federated by its technical nature, which is to say, that
> anyone can run a registry (which likely we will see happen; speaking
> for Adobe I know we will want to host officially sanctioned plugins
> for the phonegap dist).
>
> So this is good stuff. We are actually not far from plugin discovery,
> creation, validation, publication, installation, and removal!
>
> It is not without some irony that this also means our plugin packaging
> format will be package.json ---which really has bad symmetry with our
> current config/manifest file being config.xml. (I think its fine, for
> now, but something we should discuss.)
>
> Fil/Anis: need to drop the new CLI prototype into labs (soon?)
>
> Bryce: super agree on new APIs being a bit sketchy in their early
> phases. Another win for this plugin reality is that we remove a whole
> tonne of responsibility from the core cordova codebase and can start
> getting super funky with our API experimentation.
>
>
> On Wed, Jul 25, 2012 at 8:09 PM, Bryce Curtis <cu...@gmail.com>
> wrote:
> > I think the near-term looks fine.  What I consider most important on
> > the list are the plug-in metafiles and config files.  A close second
> > would be the plug-in management tools that will consume/produce these
> > files.  With that said, we probably won't be using the command line
> > tools, so having the metafiles well documented will be important.
> >
> > Next in importance will be to update current plug-ins to latest APIs.
> >
> > As for adding new APIs, I would only caution against implementing
> > early specs that change frequently - lessons learned from the
> > contacts, device and other APIs.   One thing to consider is that the
> > more plug-ins we ship with Cordova, the more we have to maintain &
> > test for each release... and that the goal should be to equally
> > support functionality across the major platforms for each first-class
> > plug-in.
> >
> >
> > On Wed, Jul 25, 2012 at 6:54 PM, Michael Brooks
> > <mi...@michaelbrooks.ca> wrote:
> >> The 2.x roadmap looks good.
> >>
> >> I've moved the "config manifest" under "Nearterm" because it should be
> >> tackled at the same time as plugin-install / remove.
> >>
> >> Michael
> >>
> >> On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com>
> wrote:
> >>
> >>> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
> >>> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
> >>> adding Tizen and WP8 support once we get the devices.
> >>>
> >>> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
> >>> > NFC def an important emerging tech. Added it to the backlog with a
> >>> > note about the w3c group:
> >>> > http://www.w3.org/wiki/Near_field_communications_(NFC)
> >>> >
> >>> >
> >>> >
> >>> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
> >>> > <pa...@linux.intel.com> wrote:
> >>> >> hi,
> >>> >>
> >>> >> with NFC,  another API that might be of interest is a payment API
> >>> several
> >>> >> groups are proposing one or working on it.  W3C has a working group,
> >>> >> Webinos an API
> >>> >>
> >>> >> http://www.w3.org/ECommerce/Micropayments/
> >>> >> http://dev.webinos.org/specifications/draft/payment.html
> >>> >>
> >>> >> -
> >>> >> Paul
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> On 07/25/2012 10:04 AM, Shazron wrote:
> >>> >>>
> >>> >>> I think this warrants some discussion to be put on the roadmap, esp
> >>> >>> since Android has a NFC API (there is a Cordova plugin here:
> >>> >>>
> >>> >>>
> >>>
> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/
> >>> ),
> >>> >>> and the rumour is the iPhone 5 (this fall) will have one as well.
> >>> >>>
> >>> >>> Don't know if any committers are involved with the standards
> bodies to
> >>> >>> get an API discussion going with the w3c.
> >>> >>>
> >>> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
> >>> >>> <pa...@linux.intel.com> wrote:
> >>> >>>>
> >>> >>>> Any NFC  web APIs support?
> >>> >>>>
> >>> >>>> Tizen owns a NFC API  [1]
> >>> >>>>
> >>> >>>> I am not sure W3C is having a draft for an API yet (2]
> >>> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
> >>> >>>>
> >>> >>>> [1] -
> >>> >>>>
> >>> >>>>
> >>>
> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
> >>> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
> >>> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
> >>> >>>>
> >>> >>>>
> >>> >>>>
> >>> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
> >>> >>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term
> >>> goals
> >>> >>>>>>>>> and
> >>> >>>>>>>>> a first pass at the long desired core API audit. Essentially
> it
> >>> >>>>>>>>> notes
> >>> >>>>>>>>> where things have moved forward in the standards process or,
> in
> >>> some
> >>> >>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
> >>> >>>>>>>>>
> >>> >>>>>>>>> Please discuss!
> >>> >>>>>>>>>
> >>> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
> >>> >>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>>>>
> >>> >>>>>
> >>> >>>>
> >>> >>>> --
> >>> >>>> Paul Plaquette
> >>> >>>> Senior Software Engineer
> >>> >>>> Open Source Technology Center
> >>> >>>> Intel Corp.,Montpellier, France
> >>> >>>
> >>> >>>
> >>> >>
> >>> >> --
> >>> >> Paul Plaquette
> >>> >> Senior Software Engineer
> >>> >> Open Source Technology Center
> >>> >> Intel Corp.,Montpellier, France
> >>>
>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Brian LeRoux <b...@brian.io>.
So, interestingly the Node dudes have expressed they are ok w/ us
experimenting w/ the npm registry for our plugin-discovery mechanism.
This is really great news as that it saves us from having to bikeshed
the service api, user auth, tech choices, etc. Our CLI tooling is
already Node so reuse w/ the npm library will be straightforward.

We can bootstrap on top of registry.npmjs.org which is really just an
Apache CouchDB instance (yay) which means that the system is
effectively federated by its technical nature, which is to say, that
anyone can run a registry (which likely we will see happen; speaking
for Adobe I know we will want to host officially sanctioned plugins
for the phonegap dist).

So this is good stuff. We are actually not far from plugin discovery,
creation, validation, publication, installation, and removal!

It is not without some irony that this also means our plugin packaging
format will be package.json ---which really has bad symmetry with our
current config/manifest file being config.xml. (I think its fine, for
now, but something we should discuss.)

Fil/Anis: need to drop the new CLI prototype into labs (soon?)

Bryce: super agree on new APIs being a bit sketchy in their early
phases. Another win for this plugin reality is that we remove a whole
tonne of responsibility from the core cordova codebase and can start
getting super funky with our API experimentation.


On Wed, Jul 25, 2012 at 8:09 PM, Bryce Curtis <cu...@gmail.com> wrote:
> I think the near-term looks fine.  What I consider most important on
> the list are the plug-in metafiles and config files.  A close second
> would be the plug-in management tools that will consume/produce these
> files.  With that said, we probably won't be using the command line
> tools, so having the metafiles well documented will be important.
>
> Next in importance will be to update current plug-ins to latest APIs.
>
> As for adding new APIs, I would only caution against implementing
> early specs that change frequently - lessons learned from the
> contacts, device and other APIs.   One thing to consider is that the
> more plug-ins we ship with Cordova, the more we have to maintain &
> test for each release... and that the goal should be to equally
> support functionality across the major platforms for each first-class
> plug-in.
>
>
> On Wed, Jul 25, 2012 at 6:54 PM, Michael Brooks
> <mi...@michaelbrooks.ca> wrote:
>> The 2.x roadmap looks good.
>>
>> I've moved the "config manifest" under "Nearterm" because it should be
>> tackled at the same time as plugin-install / remove.
>>
>> Michael
>>
>> On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com> wrote:
>>
>>> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
>>> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
>>> adding Tizen and WP8 support once we get the devices.
>>>
>>> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
>>> > NFC def an important emerging tech. Added it to the backlog with a
>>> > note about the w3c group:
>>> > http://www.w3.org/wiki/Near_field_communications_(NFC)
>>> >
>>> >
>>> >
>>> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
>>> > <pa...@linux.intel.com> wrote:
>>> >> hi,
>>> >>
>>> >> with NFC,  another API that might be of interest is a payment API
>>> several
>>> >> groups are proposing one or working on it.  W3C has a working group,
>>> >> Webinos an API
>>> >>
>>> >> http://www.w3.org/ECommerce/Micropayments/
>>> >> http://dev.webinos.org/specifications/draft/payment.html
>>> >>
>>> >> -
>>> >> Paul
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On 07/25/2012 10:04 AM, Shazron wrote:
>>> >>>
>>> >>> I think this warrants some discussion to be put on the roadmap, esp
>>> >>> since Android has a NFC API (there is a Cordova plugin here:
>>> >>>
>>> >>>
>>> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/
>>> ),
>>> >>> and the rumour is the iPhone 5 (this fall) will have one as well.
>>> >>>
>>> >>> Don't know if any committers are involved with the standards bodies to
>>> >>> get an API discussion going with the w3c.
>>> >>>
>>> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>>> >>> <pa...@linux.intel.com> wrote:
>>> >>>>
>>> >>>> Any NFC  web APIs support?
>>> >>>>
>>> >>>> Tizen owns a NFC API  [1]
>>> >>>>
>>> >>>> I am not sure W3C is having a draft for an API yet (2]
>>> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
>>> >>>>
>>> >>>> [1] -
>>> >>>>
>>> >>>>
>>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>>> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>>> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term
>>> goals
>>> >>>>>>>>> and
>>> >>>>>>>>> a first pass at the long desired core API audit. Essentially it
>>> >>>>>>>>> notes
>>> >>>>>>>>> where things have moved forward in the standards process or, in
>>> some
>>> >>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>> >>>>>>>>>
>>> >>>>>>>>> Please discuss!
>>> >>>>>>>>>
>>> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>>
>>> >>>>>
>>> >>>>
>>> >>>> --
>>> >>>> Paul Plaquette
>>> >>>> Senior Software Engineer
>>> >>>> Open Source Technology Center
>>> >>>> Intel Corp.,Montpellier, France
>>> >>>
>>> >>>
>>> >>
>>> >> --
>>> >> Paul Plaquette
>>> >> Senior Software Engineer
>>> >> Open Source Technology Center
>>> >> Intel Corp.,Montpellier, France
>>>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Bryce Curtis <cu...@gmail.com>.
I think the near-term looks fine.  What I consider most important on
the list are the plug-in metafiles and config files.  A close second
would be the plug-in management tools that will consume/produce these
files.  With that said, we probably won't be using the command line
tools, so having the metafiles well documented will be important.

Next in importance will be to update current plug-ins to latest APIs.

As for adding new APIs, I would only caution against implementing
early specs that change frequently - lessons learned from the
contacts, device and other APIs.   One thing to consider is that the
more plug-ins we ship with Cordova, the more we have to maintain &
test for each release... and that the goal should be to equally
support functionality across the major platforms for each first-class
plug-in.


On Wed, Jul 25, 2012 at 6:54 PM, Michael Brooks
<mi...@michaelbrooks.ca> wrote:
> The 2.x roadmap looks good.
>
> I've moved the "config manifest" under "Nearterm" because it should be
> tackled at the same time as plugin-install / remove.
>
> Michael
>
> On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com> wrote:
>
>> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
>> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
>> adding Tizen and WP8 support once we get the devices.
>>
>> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
>> > NFC def an important emerging tech. Added it to the backlog with a
>> > note about the w3c group:
>> > http://www.w3.org/wiki/Near_field_communications_(NFC)
>> >
>> >
>> >
>> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
>> > <pa...@linux.intel.com> wrote:
>> >> hi,
>> >>
>> >> with NFC,  another API that might be of interest is a payment API
>> several
>> >> groups are proposing one or working on it.  W3C has a working group,
>> >> Webinos an API
>> >>
>> >> http://www.w3.org/ECommerce/Micropayments/
>> >> http://dev.webinos.org/specifications/draft/payment.html
>> >>
>> >> -
>> >> Paul
>> >>
>> >>
>> >>
>> >>
>> >> On 07/25/2012 10:04 AM, Shazron wrote:
>> >>>
>> >>> I think this warrants some discussion to be put on the roadmap, esp
>> >>> since Android has a NFC API (there is a Cordova plugin here:
>> >>>
>> >>>
>> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/
>> ),
>> >>> and the rumour is the iPhone 5 (this fall) will have one as well.
>> >>>
>> >>> Don't know if any committers are involved with the standards bodies to
>> >>> get an API discussion going with the w3c.
>> >>>
>> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>> >>> <pa...@linux.intel.com> wrote:
>> >>>>
>> >>>> Any NFC  web APIs support?
>> >>>>
>> >>>> Tizen owns a NFC API  [1]
>> >>>>
>> >>>> I am not sure W3C is having a draft for an API yet (2]
>> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
>> >>>>
>> >>>> [1] -
>> >>>>
>> >>>>
>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>> >>>>
>> >>>>
>> >>>>
>> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term
>> goals
>> >>>>>>>>> and
>> >>>>>>>>> a first pass at the long desired core API audit. Essentially it
>> >>>>>>>>> notes
>> >>>>>>>>> where things have moved forward in the standards process or, in
>> some
>> >>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>> >>>>>>>>>
>> >>>>>>>>> Please discuss!
>> >>>>>>>>>
>> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> Paul Plaquette
>> >>>> Senior Software Engineer
>> >>>> Open Source Technology Center
>> >>>> Intel Corp.,Montpellier, France
>> >>>
>> >>>
>> >>
>> >> --
>> >> Paul Plaquette
>> >> Senior Software Engineer
>> >> Open Source Technology Center
>> >> Intel Corp.,Montpellier, France
>>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Michael Brooks <mi...@michaelbrooks.ca>.
The 2.x roadmap looks good.

I've moved the "config manifest" under "Nearterm" because it should be
tackled at the same time as plugin-install / remove.

Michael

On Wed, Jul 25, 2012 at 4:45 PM, Don Coleman <do...@gmail.com> wrote:

> I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
> plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
> adding Tizen and WP8 support once we get the devices.
>
> On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
> > NFC def an important emerging tech. Added it to the backlog with a
> > note about the w3c group:
> > http://www.w3.org/wiki/Near_field_communications_(NFC)
> >
> >
> >
> > On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
> > <pa...@linux.intel.com> wrote:
> >> hi,
> >>
> >> with NFC,  another API that might be of interest is a payment API
> several
> >> groups are proposing one or working on it.  W3C has a working group,
> >> Webinos an API
> >>
> >> http://www.w3.org/ECommerce/Micropayments/
> >> http://dev.webinos.org/specifications/draft/payment.html
> >>
> >> -
> >> Paul
> >>
> >>
> >>
> >>
> >> On 07/25/2012 10:04 AM, Shazron wrote:
> >>>
> >>> I think this warrants some discussion to be put on the roadmap, esp
> >>> since Android has a NFC API (there is a Cordova plugin here:
> >>>
> >>>
> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/
> ),
> >>> and the rumour is the iPhone 5 (this fall) will have one as well.
> >>>
> >>> Don't know if any committers are involved with the standards bodies to
> >>> get an API discussion going with the w3c.
> >>>
> >>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
> >>> <pa...@linux.intel.com> wrote:
> >>>>
> >>>> Any NFC  web APIs support?
> >>>>
> >>>> Tizen owns a NFC API  [1]
> >>>>
> >>>> I am not sure W3C is having a draft for an API yet (2]
> >>>> Webinos  is having one - Webinos is a European  Consortium [3]
> >>>>
> >>>> [1] -
> >>>>
> >>>>
> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
> >>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
> >>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
> >>>>
> >>>>
> >>>>
> >>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term
> goals
> >>>>>>>>> and
> >>>>>>>>> a first pass at the long desired core API audit. Essentially it
> >>>>>>>>> notes
> >>>>>>>>> where things have moved forward in the standards process or, in
> some
> >>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
> >>>>>>>>>
> >>>>>>>>> Please discuss!
> >>>>>>>>>
> >>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Paul Plaquette
> >>>> Senior Software Engineer
> >>>> Open Source Technology Center
> >>>> Intel Corp.,Montpellier, France
> >>>
> >>>
> >>
> >> --
> >> Paul Plaquette
> >> Senior Software Engineer
> >> Open Source Technology Center
> >> Intel Corp.,Montpellier, France
>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Don Coleman <do...@gmail.com>.
I'm interested in NFC.  Kevin Griffin and I wrote a phonegap-nfc
plugin https://github.com/chariotsolutions/phonegap-nfc.  We plan on
adding Tizen and WP8 support once we get the devices.

On Wed, Jul 25, 2012 at 5:44 PM, Brian LeRoux <b...@brian.io> wrote:
> NFC def an important emerging tech. Added it to the backlog with a
> note about the w3c group:
> http://www.w3.org/wiki/Near_field_communications_(NFC)
>
>
>
> On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
> <pa...@linux.intel.com> wrote:
>> hi,
>>
>> with NFC,  another API that might be of interest is a payment API several
>> groups are proposing one or working on it.  W3C has a working group,
>> Webinos an API
>>
>> http://www.w3.org/ECommerce/Micropayments/
>> http://dev.webinos.org/specifications/draft/payment.html
>>
>> -
>> Paul
>>
>>
>>
>>
>> On 07/25/2012 10:04 AM, Shazron wrote:
>>>
>>> I think this warrants some discussion to be put on the roadmap, esp
>>> since Android has a NFC API (there is a Cordova plugin here:
>>>
>>> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/),
>>> and the rumour is the iPhone 5 (this fall) will have one as well.
>>>
>>> Don't know if any committers are involved with the standards bodies to
>>> get an API discussion going with the w3c.
>>>
>>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>>> <pa...@linux.intel.com> wrote:
>>>>
>>>> Any NFC  web APIs support?
>>>>
>>>> Tizen owns a NFC API  [1]
>>>>
>>>> I am not sure W3C is having a draft for an API yet (2]
>>>> Webinos  is having one - Webinos is a European  Consortium [3]
>>>>
>>>> [1] -
>>>>
>>>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>>>
>>>>
>>>>
>>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals
>>>>>>>>> and
>>>>>>>>> a first pass at the long desired core API audit. Essentially it
>>>>>>>>> notes
>>>>>>>>> where things have moved forward in the standards process or, in some
>>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>>>>
>>>>>>>>> Please discuss!
>>>>>>>>>
>>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>
>>>>
>>>> --
>>>> Paul Plaquette
>>>> Senior Software Engineer
>>>> Open Source Technology Center
>>>> Intel Corp.,Montpellier, France
>>>
>>>
>>
>> --
>> Paul Plaquette
>> Senior Software Engineer
>> Open Source Technology Center
>> Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Brian LeRoux <b...@brian.io>.
NFC def an important emerging tech. Added it to the backlog with a
note about the w3c group:
http://www.w3.org/wiki/Near_field_communications_(NFC)



On Wed, Jul 25, 2012 at 1:36 AM, Paul Plaquette
<pa...@linux.intel.com> wrote:
> hi,
>
> with NFC,  another API that might be of interest is a payment API several
> groups are proposing one or working on it.  W3C has a working group,
> Webinos an API
>
> http://www.w3.org/ECommerce/Micropayments/
> http://dev.webinos.org/specifications/draft/payment.html
>
> -
> Paul
>
>
>
>
> On 07/25/2012 10:04 AM, Shazron wrote:
>>
>> I think this warrants some discussion to be put on the roadmap, esp
>> since Android has a NFC API (there is a Cordova plugin here:
>>
>> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/),
>> and the rumour is the iPhone 5 (this fall) will have one as well.
>>
>> Don't know if any committers are involved with the standards bodies to
>> get an API discussion going with the w3c.
>>
>> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
>> <pa...@linux.intel.com> wrote:
>>>
>>> Any NFC  web APIs support?
>>>
>>> Tizen owns a NFC API  [1]
>>>
>>> I am not sure W3C is having a draft for an API yet (2]
>>> Webinos  is having one - Webinos is a European  Consortium [3]
>>>
>>> [1] -
>>>
>>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>>
>>>
>>>
>>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals
>>>>>>>> and
>>>>>>>> a first pass at the long desired core API audit. Essentially it
>>>>>>>> notes
>>>>>>>> where things have moved forward in the standards process or, in some
>>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>>>
>>>>>>>> Please discuss!
>>>>>>>>
>>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>
>>> --
>>> Paul Plaquette
>>> Senior Software Engineer
>>> Open Source Technology Center
>>> Intel Corp.,Montpellier, France
>>
>>
>
> --
> Paul Plaquette
> Senior Software Engineer
> Open Source Technology Center
> Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Paul Plaquette <pa...@linux.intel.com>.
hi,

with NFC,  another API that might be of interest is a payment API 
several groups are proposing one or working on it.  W3C has a working 
group,  Webinos an API

http://www.w3.org/ECommerce/Micropayments/
http://dev.webinos.org/specifications/draft/payment.html

-
Paul



On 07/25/2012 10:04 AM, Shazron wrote:
> I think this warrants some discussion to be put on the roadmap, esp
> since Android has a NFC API (there is a Cordova plugin here:
> http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/),
> and the rumour is the iPhone 5 (this fall) will have one as well.
>
> Don't know if any committers are involved with the standards bodies to
> get an API discussion going with the w3c.
>
> On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
> <pa...@linux.intel.com> wrote:
>> Any NFC  web APIs support?
>>
>> Tizen owns a NFC API  [1]
>>
>> I am not sure W3C is having a draft for an API yet (2]
>> Webinos  is having one - Webinos is a European  Consortium [3]
>>
>> [1] -
>> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
>> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>>
>>
>>
>> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>
>>>>>>
>>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>>>>> a first pass at the long desired core API audit. Essentially it notes
>>>>>>> where things have moved forward in the standards process or, in some
>>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>>
>>>>>>> Please discuss!
>>>>>>>
>>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>>
>>>>>>
>>>
>>
>> --
>> Paul Plaquette
>> Senior Software Engineer
>> Open Source Technology Center
>> Intel Corp.,Montpellier, France
>

-- 
Paul Plaquette
Senior Software Engineer
Open Source Technology Center
Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Shazron <sh...@gmail.com>.
I think this warrants some discussion to be put on the roadmap, esp
since Android has a NFC API (there is a Cordova plugin here:
http://www.phonegap.com/2011/09/26/building-an-nfc-enabled-android-application-with-phonegap/),
and the rumour is the iPhone 5 (this fall) will have one as well.

Don't know if any committers are involved with the standards bodies to
get an API discussion going with the w3c.

On Wed, Jul 25, 2012 at 12:46 AM, Paul Plaquette
<pa...@linux.intel.com> wrote:
> Any NFC  web APIs support?
>
> Tizen owns a NFC API  [1]
>
> I am not sure W3C is having a draft for an API yet (2]
> Webinos  is having one - Webinos is a European  Consortium [3]
>
> [1] -
> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>
>
>
> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>
>>>>>
>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>>>> a first pass at the long desired core API audit. Essentially it notes
>>>>>> where things have moved forward in the standards process or, in some
>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>
>>>>>> Please discuss!
>>>>>>
>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>
>>>>>
>>
>
> --
> Paul Plaquette
> Senior Software Engineer
> Open Source Technology Center
> Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Paul Plaquette <pa...@linux.intel.com>.
Hi,

by the way here are a list for webinos device apis

may be several could be interesting for Cordova

http://dev.webinos.org/specifications/draft/

-
Paul

On 07/25/2012 09:46 AM, Paul Plaquette wrote:
> Any NFC  web APIs support?
>
> Tizen owns a NFC API  [1]
>
> I am not sure W3C is having a draft for an API yet (2]
> Webinos  is having one - Webinos is a European  Consortium [3]
>
> [1] -
> https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
>
> [2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
> [3] - http://dev.webinos.org/specifications/draft/nfc.html
>
>
> 2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>
>>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals
>>>>>> and
>>>>>> a first pass at the long desired core API audit. Essentially it notes
>>>>>> where things have moved forward in the standards process or, in some
>>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>>
>>>>>> Please discuss!
>>>>>>
>>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>>
>>
>

-- 
Paul Plaquette
Senior Software Engineer
Open Source Technology Center
Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Paul Plaquette <pa...@linux.intel.com>.
Any NFC  web APIs support?

Tizen owns a NFC API  [1]

I am not sure W3C is having a draft for an API yet (2]
Webinos  is having one - Webinos is a European  Consortium [3]

[1] - 
https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.help.web.api.device%2Ftizen%2Fnfc.html
[2] - http://www.w3.org/wiki/Near_field_communications_(NFC)
[3] - http://dev.webinos.org/specifications/draft/nfc.html


2 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>
>>>>> Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>>> a first pass at the long desired core API audit. Essentially it notes
>>>>> where things have moved forward in the standards process or, in some
>>>>> cases, cordova specific upgrades we've discussed in the past.
>>>>>
>>>>> Please discuss!
>>>>>
>>>>> [1] http://wiki.apache.org/cordova/RoadmapProjects
>>>>
>

-- 
Paul Plaquette
Senior Software Engineer
Open Source Technology Center
Intel Corp.,Montpellier, France

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Shazron <sh...@gmail.com>.
Also, for the API audit / Camera plugin - this has been a frequent
feature request -- right now we only select the back facing camera,
there is no choice for the front-facing one.

On Tue, Jul 24, 2012 at 2:08 PM, Shazron <sh...@gmail.com> wrote:
> Under Core API audit / Capture:
> -> that link points to an obsolete doc, which points to
> http://dev.w3.org/2011/webrtc/editor/getusermedia.html
>
> Which appears to be under the webrtc umbrella (note the url). That is
> perhaps my confusion (from the other thread). I'm wondering if it
> should be HTML Media Capture instead or is this another thing? see:
> http://www.w3.org/TR/html-media-capture/
>
> On Tue, Jul 24, 2012 at 9:11 AM, Brian LeRoux <b...@brian.io> wrote:
>> Mike/Fil: updated the wiki.
>>
>> Lets kick up discussions about both File and Media in sep threads.
>>
>> On Tue, Jul 24, 2012 at 8:27 AM, Filip Maj <fi...@adobe.com> wrote:
>>> Things that I see missing are:
>>>
>>> - shipping with no "core" APIs/plugins (but that hinges on master cli
>>> script and plugin discovery).
>>> - Getting Andrew Lunny's plugin spec [1] documented / integrated
>>>
>>> Things that warrant more discussion:
>>>
>>> - what specifically to do about the media API. Highest priority I think
>>> based on # of issues that exist related to it in the JIRA.
>>> - file API path normalization. For sure. Also a "fuller" implementation:
>>> right now, the Entry objects have no association to a FileSystem object.
>>> So if you request a TEMPORARY FS and create an Entry in that FileSystem,
>>> and later do the same using a PERSISTENT FS, you will not be able to tell
>>> the difference between the two (unless you do it manually based on the
>>> probably platform-specific and differing paths each will have).
>>> - notifications API: YES!!! We already have plugins in the wild that we
>>> simply need to normalize the JS interface to the w3c spec
>>>
>>> [1] https://github.com/alunny/cordova-plugin-spec
>>>
>>> On 7/24/12 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>>
>>>>Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>>a first pass at the long desired core API audit. Essentially it notes
>>>>where things have moved forward in the standards process or, in some
>>>>cases, cordova specific upgrades we've discussed in the past.
>>>>
>>>>Please discuss!
>>>>
>>>>[1] http://wiki.apache.org/cordova/RoadmapProjects
>>>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Shazron <sh...@gmail.com>.
Under Core API audit / Capture:
-> that link points to an obsolete doc, which points to
http://dev.w3.org/2011/webrtc/editor/getusermedia.html

Which appears to be under the webrtc umbrella (note the url). That is
perhaps my confusion (from the other thread). I'm wondering if it
should be HTML Media Capture instead or is this another thing? see:
http://www.w3.org/TR/html-media-capture/

On Tue, Jul 24, 2012 at 9:11 AM, Brian LeRoux <b...@brian.io> wrote:
> Mike/Fil: updated the wiki.
>
> Lets kick up discussions about both File and Media in sep threads.
>
> On Tue, Jul 24, 2012 at 8:27 AM, Filip Maj <fi...@adobe.com> wrote:
>> Things that I see missing are:
>>
>> - shipping with no "core" APIs/plugins (but that hinges on master cli
>> script and plugin discovery).
>> - Getting Andrew Lunny's plugin spec [1] documented / integrated
>>
>> Things that warrant more discussion:
>>
>> - what specifically to do about the media API. Highest priority I think
>> based on # of issues that exist related to it in the JIRA.
>> - file API path normalization. For sure. Also a "fuller" implementation:
>> right now, the Entry objects have no association to a FileSystem object.
>> So if you request a TEMPORARY FS and create an Entry in that FileSystem,
>> and later do the same using a PERSISTENT FS, you will not be able to tell
>> the difference between the two (unless you do it manually based on the
>> probably platform-specific and differing paths each will have).
>> - notifications API: YES!!! We already have plugins in the wild that we
>> simply need to normalize the JS interface to the w3c spec
>>
>> [1] https://github.com/alunny/cordova-plugin-spec
>>
>> On 7/24/12 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>
>>>Hey guys, i've just updated the wiki [1] with some near-term goals and
>>>a first pass at the long desired core API audit. Essentially it notes
>>>where things have moved forward in the standards process or, in some
>>>cases, cordova specific upgrades we've discussed in the past.
>>>
>>>Please discuss!
>>>
>>>[1] http://wiki.apache.org/cordova/RoadmapProjects
>>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Brian LeRoux <b...@brian.io>.
Mike/Fil: updated the wiki.

Lets kick up discussions about both File and Media in sep threads.

On Tue, Jul 24, 2012 at 8:27 AM, Filip Maj <fi...@adobe.com> wrote:
> Things that I see missing are:
>
> - shipping with no "core" APIs/plugins (but that hinges on master cli
> script and plugin discovery).
> - Getting Andrew Lunny's plugin spec [1] documented / integrated
>
> Things that warrant more discussion:
>
> - what specifically to do about the media API. Highest priority I think
> based on # of issues that exist related to it in the JIRA.
> - file API path normalization. For sure. Also a "fuller" implementation:
> right now, the Entry objects have no association to a FileSystem object.
> So if you request a TEMPORARY FS and create an Entry in that FileSystem,
> and later do the same using a PERSISTENT FS, you will not be able to tell
> the difference between the two (unless you do it manually based on the
> probably platform-specific and differing paths each will have).
> - notifications API: YES!!! We already have plugins in the wild that we
> simply need to normalize the JS interface to the w3c spec
>
> [1] https://github.com/alunny/cordova-plugin-spec
>
> On 7/24/12 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:
>
>>Hey guys, i've just updated the wiki [1] with some near-term goals and
>>a first pass at the long desired core API audit. Essentially it notes
>>where things have moved forward in the standards process or, in some
>>cases, cordova specific upgrades we've discussed in the past.
>>
>>Please discuss!
>>
>>[1] http://wiki.apache.org/cordova/RoadmapProjects
>

Re: [DISCUSS] 2.x roadmap planning / first pass at api audit

Posted by Filip Maj <fi...@adobe.com>.
Things that I see missing are:

- shipping with no "core" APIs/plugins (but that hinges on master cli
script and plugin discovery).
- Getting Andrew Lunny's plugin spec [1] documented / integrated

Things that warrant more discussion:

- what specifically to do about the media API. Highest priority I think
based on # of issues that exist related to it in the JIRA.
- file API path normalization. For sure. Also a "fuller" implementation:
right now, the Entry objects have no association to a FileSystem object.
So if you request a TEMPORARY FS and create an Entry in that FileSystem,
and later do the same using a PERSISTENT FS, you will not be able to tell
the difference between the two (unless you do it manually based on the
probably platform-specific and differing paths each will have).
- notifications API: YES!!! We already have plugins in the wild that we
simply need to normalize the JS interface to the w3c spec

[1] https://github.com/alunny/cordova-plugin-spec

On 7/24/12 7:58 AM, "Brian LeRoux" <b...@brian.io> wrote:

>Hey guys, i've just updated the wiki [1] with some near-term goals and
>a first pass at the long desired core API audit. Essentially it notes
>where things have moved forward in the standards process or, in some
>cases, cordova specific upgrades we've discussed in the past.
>
>Please discuss!
>
>[1] http://wiki.apache.org/cordova/RoadmapProjects