Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.39 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Thu, 26 Jul 2012 17:05:10 -0700
Subject: Re: [DISCUSS] 2.x roadmap planning / first pass at api audit
Thread-Topic: [DISCUSS] 2.x roadmap planning / first pass at api audit
Thread-Index: Ac1riwJLEycRJh4mTyu3HBRCygMEjA==
Message-ID: <CC37293B.AE29%fil@adobe.com>
In-Reply-To: 
 <CANpVHHzAAm2wgyiuRhaN1aQTQWbEkzuKHoH8pAnjkiw8=kDy-A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Anis your pushed killed all the history :(

On 7/26/12 11:52 AM, "Anis KADRI" <anis.kadri@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 <curtis.bryce@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
>> > <michael@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 <don.coleman@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
>> >>> > <paul.plaquette@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:
>> >>> >>>
>> >>> >>>
>> >>>
>>=20
>>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
>> >>> >>> <paul.plaquette@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] -
>> >>> >>>>
>> >>> >>>>
>> >>>
>>=20
>>https://developer.tizen.org/help/index.jsp?topic=3D%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
>> >>>
>>