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 2013/01/03 21:34:55 UTC
the great seperatino of concerns
Our general goal for Cordova 3.x is composability. Extending the core
should be trivially simple, with tools for discovering, adding,
removing, creating, validating, and publishing Plugin Packages. This
will make creating downstream distributions easier, developers using
Cordova won't be building from a 'kitchen sink', and most importantly
we will have a sane way to extend the platform in new directions.
Anis has been working w/ Fil, Lunny, and Mike on the Plugman tool. As
just mentioned by Fil it is now stable enough to start looking at
stripping our API surface from individual platforms and putting them
into their own repos. This is going to kind of suck at first.
Additional tools will be required.
Fil, "first we need to identify which platforms we want to support
with auto plugin management". Agree, think we should strive for
support in the 'Core Platforms' [1].
This would mean the next steps would be:
- BlackBerry support for Plugman
- Windows Phone support for Plugman
- Bada support for Plugman (Do we still consider this a core platform
in 2013 or should Tizen take this spot??)
In parallel, we'd look at moving core plugins out into individual
repos. We should take this slow, and start w/ something simple, like
org.apache.cordova.geolocation (which will help us move Coho and
Robson tools to make this transition transparent to the users
downloading downstream distributions.)
Thoughts?
[1] http://wiki.apache.org/cordova/PlatformSupport
[1] http://wiki.apache.org/cordova/PlatformSupport
RE: the great seperatino of concerns
Posted by Carlos Lopez <cl...@inversionescgi.net>.
ave
-----Mensaje original-----
De: brian.leroux@gmail.com [mailto:brian.leroux@gmail.com] En nombre de
Brian LeRoux
Enviado el: jueves, 03 de enero de 2013 21:35
Para: dev@cordova.apache.org
Asunto: the great seperatino of concerns
Our general goal for Cordova 3.x is composability. Extending the core should
be trivially simple, with tools for discovering, adding, removing, creating,
validating, and publishing Plugin Packages. This will make creating
downstream distributions easier, developers using Cordova won't be building
from a 'kitchen sink', and most importantly we will have a sane way to
extend the platform in new directions.
Anis has been working w/ Fil, Lunny, and Mike on the Plugman tool. As just
mentioned by Fil it is now stable enough to start looking at stripping our
API surface from individual platforms and putting them into their own repos.
This is going to kind of suck at first.
Additional tools will be required.
Fil, "first we need to identify which platforms we want to support with auto
plugin management". Agree, think we should strive for support in the 'Core
Platforms' [1].
This would mean the next steps would be:
- BlackBerry support for Plugman
- Windows Phone support for Plugman
- Bada support for Plugman (Do we still consider this a core platform in
2013 or should Tizen take this spot??)
In parallel, we'd look at moving core plugins out into individual repos. We
should take this slow, and start w/ something simple, like
org.apache.cordova.geolocation (which will help us move Coho and Robson
tools to make this transition transparent to the users downloading
downstream distributions.)
Thoughts?
[1] http://wiki.apache.org/cordova/PlatformSupport
[1] http://wiki.apache.org/cordova/PlatformSupport
Re: the great seperatino of concerns
Posted by Brian LeRoux <b...@brian.io>.
The idea has been proposed that we even add an ./emulate folder for
Ripple to consume ---tests, docs, src, and emulation all into the
Package format.
On Thu, Jan 3, 2013 at 3:11 PM, Michael Brooks <mi...@michaelbrooks.ca> wrote:
> @fil @dave, yes to both test suite and docs.
>
> On Thu, Jan 3, 2013 at 5:09 PM, Dave Johnson <da...@gmail.com>wrote:
>
>> @fil and docs too
>>
>> On Thursday, January 3, 2013, Filip Maj wrote:
>>
>> >
>> > >In parallel, we'd look at moving core plugins out into individual
>> > >repos. We should take this slow, and start w/ something simple, like
>> > >org.apache.cordova.geolocation (which will help us move Coho and
>> > >Robson tools to make this transition transparent to the users
>> > >downloading downstream distributions.)
>> >
>> > Just throwing this out there as it just occurred to me, but this also
>> > implies that we are partitioning mobile-spec into discrete test suites
>> > that will be the responsibility of the plugins to maintain moving
>> forward,
>> > yes?
>> >
>> >
>>
Re: the great seperatino of concerns
Posted by Michael Brooks <mi...@michaelbrooks.ca>.
@fil @dave, yes to both test suite and docs.
On Thu, Jan 3, 2013 at 5:09 PM, Dave Johnson <da...@gmail.com>wrote:
> @fil and docs too
>
> On Thursday, January 3, 2013, Filip Maj wrote:
>
> >
> > >In parallel, we'd look at moving core plugins out into individual
> > >repos. We should take this slow, and start w/ something simple, like
> > >org.apache.cordova.geolocation (which will help us move Coho and
> > >Robson tools to make this transition transparent to the users
> > >downloading downstream distributions.)
> >
> > Just throwing this out there as it just occurred to me, but this also
> > implies that we are partitioning mobile-spec into discrete test suites
> > that will be the responsibility of the plugins to maintain moving
> forward,
> > yes?
> >
> >
>
Re: the great seperatino of concerns
Posted by Dave Johnson <da...@gmail.com>.
@fil and docs too
On Thursday, January 3, 2013, Filip Maj wrote:
>
> >In parallel, we'd look at moving core plugins out into individual
> >repos. We should take this slow, and start w/ something simple, like
> >org.apache.cordova.geolocation (which will help us move Coho and
> >Robson tools to make this transition transparent to the users
> >downloading downstream distributions.)
>
> Just throwing this out there as it just occurred to me, but this also
> implies that we are partitioning mobile-spec into discrete test suites
> that will be the responsibility of the plugins to maintain moving forward,
> yes?
>
>
Re: the great seperatino of concerns
Posted by Anis KADRI <an...@gmail.com>.
https://github.com/imhotep/plugman
On Mon, Jan 7, 2013 at 8:49 AM, Plaquette, Paul <pa...@intel.com>wrote:
> Hi,
>
> I can help on this for Tizen.
>
> Where can I find accurate informations on that Plugman ?
>
> Regards,
> Paul
>
> On Thu, Jan 3, 2013 at 10:37 PM, Filip Maj <fi...@adobe.com> wrote:
>
> > >
> > >This would mean the next steps would be:
> > >
> > >- BlackBerry support for Plugman
> > >- Windows Phone support for Plugman
> >
> >
> > Jesse and I sent pull requests to Lunny's original pluginstall repo for
> > support for both blackberry and wp7 a LONG time ago. At the time there
> was
> > more focus from Lunny on PhoneGap Build so it never got integrated. We'd
> > have to audit the two pull requests [1] [2] for integration into plugman
> > but the gist of the code is there.
> >
> > >- Bada support for Plugman (Do we still consider this a core platform
> > >in 2013 or should Tizen take this spot??)
> >
> > I'll kick up a new thread about this. I think auditing other aspects of
> > platforms are in order too. Will delve into more details in new thread.
> >
> > [1] https://github.com/alunny/pluginstall/pull/9
> > [2] https://github.com/alunny/pluginstall/pull/8
> >
> > ---------------------------------------------------------------------
> > Intel Corporation SAS (French simplified joint stock company)
> > Registered headquarters: "Les Montalets"- 2, rue de Paris,
> > 92196 Meudon Cedex, France
> > Registration Number: 302 456 199 R.C.S. NANTERRE
> > Capital: 4,572,000 Euros
> >
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). Any review or distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> >
> >
>
>
> --
> ____________________________
>
> Paul Plaquette,
> Senior Software Engineer
> Intel Corporation SAS
> Open source Technology Center - OTC
> France, Montpellier
>
Re: the great seperatino of concerns
Posted by "Plaquette, Paul" <pa...@intel.com>.
Hi,
I can help on this for Tizen.
Where can I find accurate informations on that Plugman ?
Regards,
Paul
On Thu, Jan 3, 2013 at 10:37 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >This would mean the next steps would be:
> >
> >- BlackBerry support for Plugman
> >- Windows Phone support for Plugman
>
>
> Jesse and I sent pull requests to Lunny's original pluginstall repo for
> support for both blackberry and wp7 a LONG time ago. At the time there was
> more focus from Lunny on PhoneGap Build so it never got integrated. We'd
> have to audit the two pull requests [1] [2] for integration into plugman
> but the gist of the code is there.
>
> >- Bada support for Plugman (Do we still consider this a core platform
> >in 2013 or should Tizen take this spot??)
>
> I'll kick up a new thread about this. I think auditing other aspects of
> platforms are in order too. Will delve into more details in new thread.
>
> [1] https://github.com/alunny/pluginstall/pull/9
> [2] https://github.com/alunny/pluginstall/pull/8
>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number: 302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
--
____________________________
Paul Plaquette,
Senior Software Engineer
Intel Corporation SAS
Open source Technology Center - OTC
France, Montpellier
Re: the great seperatino of concerns
Posted by Filip Maj <fi...@adobe.com>.
>
>This would mean the next steps would be:
>
>- BlackBerry support for Plugman
>- Windows Phone support for Plugman
Jesse and I sent pull requests to Lunny's original pluginstall repo for
support for both blackberry and wp7 a LONG time ago. At the time there was
more focus from Lunny on PhoneGap Build so it never got integrated. We'd
have to audit the two pull requests [1] [2] for integration into plugman
but the gist of the code is there.
>- Bada support for Plugman (Do we still consider this a core platform
>in 2013 or should Tizen take this spot??)
I'll kick up a new thread about this. I think auditing other aspects of
platforms are in order too. Will delve into more details in new thread.
[1] https://github.com/alunny/pluginstall/pull/9
[2] https://github.com/alunny/pluginstall/pull/8
Re: the great seperatino of concerns
Posted by Filip Maj <fi...@adobe.com>.
>In parallel, we'd look at moving core plugins out into individual
>repos. We should take this slow, and start w/ something simple, like
>org.apache.cordova.geolocation (which will help us move Coho and
>Robson tools to make this transition transparent to the users
>downloading downstream distributions.)
Just throwing this out there as it just occurred to me, but this also
implies that we are partitioning mobile-spec into discrete test suites
that will be the responsibility of the plugins to maintain moving forward,
yes?