I am wondering if it is getting close to the time we take the chrome
extension out of the project (or at least disable building of it).

The future of this project is in the hosted version.

I know there is some issues with jsDom building on windows. We only use
jsDom for testing and I am thinking there might be a better option out
there for running our tests in node.


On Wed, Oct 23, 2013 at 6:11 AM, Raymond Camden <[email protected]>wrote:

> So - on Windows, I was not able to run configure. Instead, I simply ran the
> commands inside. The first npm worked, the second, did not. Lots of errors.
> My VM is off at the moment, but I can share later. JR, did you run into
> issues there?
>
>
> On Tue, Oct 22, 2013 at 9:57 PM, JR <[email protected]> wrote:
>
> > Yes still required. Nothing special for windows except just running build
> > wont work since it tries to build the chrome extension first. Build
> hosted
> > only with jake build[hosted]
> > On Oct 22, 2013 10:44 PM, "Raymond Camden" <[email protected]>
> > wrote:
> >
> > > Is configure/jake/etc still required? I did see your other email to me
> -
> > > just wondering if there *is* special steps for Windows folks if it will
> > be
> > > documented.
> > >
> > >
> > > On Tue, Oct 22, 2013 at 9:40 PM, JR <[email protected]> wrote:
> > >
> > > > Since my pull was accepted hosted builds but not the extension.
> > > > On Oct 22, 2013 9:37 PM, "Raymond Camden" <[email protected]>
> > > wrote:
> > > >
> > > > > So dumb question - is it possible - and should it be documented -
> to
> > > run
> > > > > the build on Windows?
> > > > >
> > > > >
> > > > > On Mon, Oct 21, 2013 at 5:34 AM, Raymond Camden <
> > > [email protected]
> > > > > >wrote:
> > > > >
> > > > > > I'm going to test it on a Windows VM I've got and see how well it
> > > > works.
> > > > > >
> > > > > >
> > > > > > On Sun, Oct 20, 2013 at 9:51 PM, Gord Tanner <[email protected]>
> > > > wrote:
> > > > > >
> > > > > >> Yes,
> > > > > >>
> > > > > >> merged in here:
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-ripple.git;a=commitdiff;h=ff0deaddd1307b987883a1c90cf96ad3d407f231
> > > > > >>
> > > > > >>
> > > > > >> On Sun, Oct 20, 2013 at 9:44 PM, Raymond Camden <
> > > > > [email protected]
> > > > > >> >wrote:
> > > > > >>
> > > > > >> > I believe there was an issue with Windows - JRowny had a
> patch -
> > > was
> > > > > >> that
> > > > > >> > taken in?
> > > > > >> >
> > > > > >> >
> > > > > >> > On Sun, Oct 20, 2013 at 8:38 PM, Gord Tanner <
> [email protected]
> > >
> > > > > wrote:
> > > > > >> >
> > > > > >> > > Hey everyone,
> > > > > >> > >
> > > > > >> > > I am feeling that the Cordova 3.0 support branch is stable
> > > enough
> > > > so
> > > > > >> I am
> > > > > >> > > merging it into develop.
> > > > > >> > >
> > > > > >> > > We are probably getting close to being able to ship the npm
> > > > package
> > > > > >> with
> > > > > >> > > cordova 3.0 support.
> > > > > >> > >
> > > > > >> > > I was just wondering what we need to do to prep for a true
> > > apache
> > > > > >> > release?
> > > > > >> > >
> > > > > >> > > I know there was some licensing issues with blackberries
> > device
> > > > > skins.
> > > > > >> > >  Rather then figure out all that stuff I can just remove
> them
> > so
> > > > it
> > > > > >> isn't
> > > > > >> > > an issue.  At some point in the future someone can crop some
> > new
> > > > > skins
> > > > > >> > for
> > > > > >> > > all the devices anyways.
> > > > > >> > >
> > > > > >> > > Was it just the images that was holding up our releases?  I
> > > > wouldn't
> > > > > >> mind
> > > > > >> > > getting an official one out the door with Cordova 3.0
> support.
> > > > > >> > >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> ===========================================================================
> > > > > >> > Raymond Camden, Adobe Developer Evangelist
> > > > > >> >
> > > > > >> > Email : [email protected]
> > > > > >> > Blog : www.raymondcamden.com
> > > > > >> > Twitter: cfjedimaster
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > >
> > > >
> > >
> >
> ===========================================================================
> > > > > > Raymond Camden, Adobe Developer Evangelist
> > > > > >
> > > > > > Email : [email protected]
> > > > > > Blog : www.raymondcamden.com
> > > > > > Twitter: cfjedimaster
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > >
> > >
> >
> ===========================================================================
> > > > > Raymond Camden, Adobe Developer Evangelist
> > > > >
> > > > > Email : [email protected]
> > > > > Blog : www.raymondcamden.com
> > > > > Twitter: cfjedimaster
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > >
> >
> ===========================================================================
> > > Raymond Camden, Adobe Developer Evangelist
> > >
> > > Email : [email protected]
> > > Blog : www.raymondcamden.com
> > > Twitter: cfjedimaster
> > >
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Adobe Developer Evangelist
>
> Email : [email protected]
> Blog : www.raymondcamden.com
> Twitter: cfjedimaster
>

Reply via email to