cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <mmo...@chromium.org>
Subject Re: cordova serve broken
Date Thu, 07 Nov 2013 15:37:53 GMT
Ah, I'm getting the picture.  I've only ever thought of using serve for (a)
app harness and (b) livereload on a device.  For both those I wouldn't want
any mocking of cordova stuff at all.

So what Ripple brings to the table is (c) the ability to run on unsupported
platforms via browser.

I agree we want all these options, but I'm still not necessarily sold that
they should all be merged.  Since I'm not doing the work, I'll trust you
all to make the right call here!

-Michal


On Thu, Nov 7, 2013 at 9:53 AM, Brian LeRoux <b@brian.io> wrote:

> During the lull in Ripple's development it definitely felt risky but the
> project has become rather active again of late. The big advantage is the
> mocking for all the Cordova specific stuff (like deviceready).
>
> We do need a lightweight option for App Harness. I believe we can treat
> Ripple as a middleware so maybe exposing this is the right way.
>
>
> On Thu, Nov 7, 2013 at 2:42 PM, Michal Mocny <mmocny@chromium.org> wrote:
>
> > Forgive the ignorance, but, why should we be depending on ripple for
> > implementing cordova serve?
> >
> > One advantage I see, is that we already do want to support Ripple as a
> > client, and I'm deducing that Ripple has a server component which serves
> > files, so why reinvent the wheel, lets share code, great.
> >
> > One disadvantage that I see, is that Ripple (the client) is not
> necessarily
> > going to be used by everyone who wants to use cordova serve for e.g. app
> > harness.  So, ripple seems like a heavy dependency just to serve files
> for
> > app harness -- does it even work on all platforms we target (windows
> etc?).
> >  I remember having issues in the past with depending on it.
> >
> > Just want to understand what it buys and what it costs us before we move
> > forward.
> >
> > -Michal
> >
> >
> > On Thu, Nov 7, 2013 at 8:54 AM, Bryan Higgins <bryan@bryanhiggins.net
> > >wrote:
> >
> > > Is there a JIRA for the serve issue? Josh recently added some content
> to
> > > make the landing page functional.
> > >
> > > Ripple integration sounds great. Gord - is there a way to make ripple
> run
> > > chromeless for the app harness?
> > >
> > > On Thu, Nov 7, 2013 at 7:54 AM, Gord Tanner <gtanner@gmail.com> wrote:
> > >
> > > > I can code up a quick sample integration to see what cordova serve
> > > (powered
> > > > by ripple) would look like.
> > > >
> > > >
> > > >
> > > >
> > > > On Thu, Nov 7, 2013 at 7:16 AM, Josh Soref <jsoref@blackberry.com>
> > > wrote:
> > > >
> > > > > Brian wrote:
> > > > > > Feels like we're starting to regress rather often on the CLI
> these
> > > past
> > > > > two releases.
> > > > > > This is due to not running tests (or indeed writing them).
> > > > >
> > > > > > Thats fine. Stuff happens. A gentle reminder:
> > > > >
> > > > > > - If there is a bug: write a test
> > > > > > - If you are adding or refactoring code: run the tests
> > > > >
> > > > >
> > > > > http://wiki.apache.org/cordova/RunningTests isn't linked from
> > > > > http://wiki.apache.org/cordova/IssueWorkflow
> > > > > And the instructions in both sections are unusable.
> > > > >
> > > > > I'll try to improve both pages when I wake up.
> > > > >
> ---------------------------------------------------------------------
> > > > > This transmission (including any attachments) may contain
> > confidential
> > > > > information, privileged material (including material protected by
> the
> > > > > solicitor-client or other applicable privileges), or constitute
> > > > non-public
> > > > > information. Any use of this information by anyone other than the
> > > > intended
> > > > > recipient is prohibited. If you have received this transmission in
> > > error,
> > > > > please immediately reply to the sender and delete this information
> > from
> > > > > your system. Use, dissemination, distribution, or reproduction of
> > this
> > > > > transmission by unintended recipients is not authorized and may be
> > > > unlawful.
> > > > >
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message