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 <br...@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 <gtan...@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 <jso...@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. > > > > > > > > >
