Thanks, Julian. Great summary!
Best,
Serge
@lunarserge
-Original Message-
From: Horn, Julian C [mailto:julian.c.h...@intel.com]
Sent: Tuesday, November 18, 2014 1:58 PM
To: dev@cordova.apache.org
Subject: RE: Summarizing thoughts on cordova-browser vs Ripple
I'd like to answer so
-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Tuesday, November 18, 2014 4:04 PM
To: dev@cordova.apache.org
Subject: Re: Summarizing thoughts on cordova-browser vs Ripple
Shouldn't ripple be able to emulate/monkey-patch any of the platforms?
If I am looking at and testing my cordova-ios app i
XDK, that will be totally technically separate from its Cordova
> > implementation. While this is a viable alternative, this just doesn't
> smell
> > right.
> >
> > Best,
> > Serge Lunev
> > Intel XDK Engineering Manager
> > @lunarserge
> >
ux
> Sent: Tuesday, November 18, 2014 9:26 AM
> To: dev@cordova.apache.org
> Subject: Re: Summarizing thoughts on cordova-browser vs Ripple
>
> I'm less interested in copying work being done faster/better in the
> browser devtools. Certainly some UI abstractions are helpful
ll right.
Best,
Serge Lunev
Intel XDK Engineering Manager
@lunarserge
-Original Message-
From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian
LeRoux
Sent: Tuesday, November 18, 2014 9:26 AM
To: dev@cordova.apache.org
Subject: Re: Summarizing thoughts on cordova-br
I'm less interested in copying work being done faster/better in the browser
devtools. Certainly some UI abstractions are helpful (map controls,
acceleromter scrubbing widget, etc) but the returns for dev time are
diminishing for the effort to author/maintain. Esp bad considering we'd
have to pick U
On Tue, Nov 18, 2014 at 9:57 AM, Ray Camden wrote:
>
> >>
> >> On 11/15/14, 2:17 PM, "Michal Mocny" wrote:
> >>
>
> >>Not at all. What is it you think we are proposing? I'm merely
> >>suggesting
> >that the cordova-browser camera plugin implementation shouldn't *also*
> >come
> >with a DOM com
>>
>> On 11/15/14, 2:17 PM, "Michal Mocny" wrote:
>>
>>Not at all. What is it you think we are proposing? I'm merely
>>suggesting
>that the cordova-browser camera plugin implementation shouldn't *also*
>come
>with a DOM component that sits over top of your application to manipulate
>the camera
On Mon, Nov 17, 2014 at 6:37 AM, Ray Camden wrote:
>
>
> On 11/15/14, 2:17 PM, "Michal Mocny" wrote:
>
> >Ray, I think (hope) you are slightly misreading the distinction. Trying
> >to
> >rephrase:
> >
> >Ripple is an (optional) tool for mobile-device-emulation. It just happens
> >to be impleme
On 11/15/14, 2:17 PM, "Michal Mocny" wrote:
>Ray, I think (hope) you are slightly misreading the distinction. Trying
>to
>rephrase:
>
>Ripple is an (optional) tool for mobile-device-emulation. It just happens
>to be implemented in a browser, and yes has historically been used by devs
>to run
Ray, I think (hope) you are slightly misreading the distinction. Trying to
rephrase:
Ripple is an (optional) tool for mobile-device-emulation. It just happens
to be implemented in a browser, and yes has historically been used by devs
to run cordova apps locally in a browser. But ripple does a l
I¹m pretty late to responding to this thread, but I wanted to throw in a
few comments. In the first msg, Michal Mocny said this:
"Basically, browser-platform is for getting apps running in a browser (duh)
with as much working functionality as possible. Its supposed to simplify
the 'if cordova the
ailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Friday, November 14, 2014 4:07 AM
To: dev
Subject: Re: Summarizing thoughts on cordova-browser vs Ripple
From reading this, seems like it could work well to have plugins provide both
browser and ripple implementations. They could make them the
But if they
> at
> > least provide a browser implementation then Ripple has something to fall
> > back on. And if there's something better that can be done, we can always
> > extend Ripple.
> >
>
> Given that the biggest benefit of Ripple is to provide UI t
plugin authors would provide implementations -- but that is
for what we know are classifying as cordova-browser implementations (even
if just stubs / no-ops).
>
> Julian
>
> -Original Message-
> From: Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com]
>
H) [mailto:panar...@microsoft.com]
Sent: Wednesday, November 05, 2014 2:25 PM
To: dev@cordova.apache.org
Subject: RE: Summarizing thoughts on cordova-browser vs Ripple
MSOpenTech is currently working on porting our ripple-platform prototype -
https://github.com/MSOpenTech/cordova-ripple to work on to
> From: panar...@microsoft.com
> To: dev@cordova.apache.org
> Subject: RE: Summarizing thoughts on cordova-browser vs Ripple
> Date: Wed, 5 Nov 2014 19:24:44 +
>
> �MSOpenTech is currently working on porting our ripple-platform prototype -
> https://github.com/MSOpenTech/cord
.
-Original Message-
From: Kirupa Chinnathambi [mailto:kiru...@microsoft.com]
Sent: Wednesday, November 5, 2014 11:04 AM
To: dev@cordova.apache.org
Subject: RE: Summarizing thoughts on cordova-browser vs Ripple
+1 to what you’ve both stated.
Cordova-browser shouldn't be responsibl
would be external to that in some form or fashion.
Cheers,
Kirupa
-Original Message-
From: mikeywbro...@gmail.com [mailto:mikeywbro...@gmail.com] On Behalf Of
Michael Brooks
Sent: Wednesday, November 5, 2014 9:22 AM
To: dev@cordova.apache.org
Subject: Re: Summarizing thoughts on cordova-br
>
> In my view, ripple should be built on top of the browser platform work, and
> ideally also decouple the UI from the plugin instrumentation, but thats up
> to the folks running that effort.
> With all this in mind, I think the cordova-browser effort should proceed
> with current direction, b
20 matches
Mail list logo
