cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Higgins <bhigg...@blackberry.com>
Subject Re: blackberry 10 migration
Date Mon, 06 May 2013 23:23:06 GMT
Ok, I'm about to merge from blackberry/blackberry10-rebase into
blackberry/blackberry10

Let me know when you have pushed into apache. There are some open pull
requests which I will re-target.


On Mon, May 6, 2013 at 7:07 PM, Jeffrey Heifetz <jheifetz@blackberry.com>wrote:

> What about plugman and cli?
>
> Sent from my BlackBerry 10 smartphone on the Rogers network.
> From: Lorin Beer
> Sent: Monday, May 6, 2013 7:04 PM
> To: dev
> Reply To: dev@cordova.apache.org
> Subject: Re: blackberry 10 migration
>
>
> ok, we'll pull the code from Blackberry/Blackberry-Cordova and
> Blackberry/Cordova-JS into branches in the apache repos. When the docs are
> ready, we'll merge them into master.
>
> On Mon, May 6, 2013 at 3:36 PM, Bryan Higgins <bhiggins@blackberry.com
> >wrote:
>
> > Hi Lorin,
> >
> > That's great. I think we should be able to get out a rough draft over the
> > next couple days.
> >
> >
> > On Mon, May 6, 2013 at 1:43 PM, Lorin Beer <lorin.beer.dev@gmail.com>
> > wrote:
> >
> > > Hi Bryan, a quick update:
> > >
> > > I'll be pulling the code in as soon as docs are in place. Let me know
> > when
> > > you can push a rough draft at us!
> > >
> > > - Lorin
> > >
> > >
> > > On Fri, May 3, 2013 at 9:43 AM, Lorin Beer <lorin.beer.dev@gmail.com>
> > > wrote:
> > >
> > > > sounds awesome! Brian is trying to set up a meetings with our teams
> > next
> > > > week after Max, so I think we are pushing for a post-Max migration
> > date,
> > > > late next week.
> > > >
> > > > thanks for the update Bryan,
> > > >
> > > > Lorin
> > > >
> > > >
> > > > On Fri, May 3, 2013 at 5:24 AM, Bryan Higgins <
> bhiggins@blackberry.com
> > > >wrote:
> > > >
> > > >> Hi Lorin,
> > > >>
> > > >> We will update to 2.7.0 today and I'm meeting with the docs people
> > this
> > > >> afternoon.
> > > >>
> > > >> If they don't have anything ready, I can bang out a draft while I'm
> > > flying
> > > >> out to Max on Sunday.
> > > >>
> > > >> Thanks,
> > > >> Bryan
> > > >>
> > > >>
> > > >> On Thu, May 2, 2013 at 5:45 PM, Lorin Beer <
> lorin.beer.dev@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Hi Bryan,
> > > >> >
> > > >> > any progress on the doc side of things? From my experience with
> the
> > > new
> > > >> > codebase, I shouldn't think that documenting the necessary
> workflows
> > > >> > (plugins, getting started, etc) should be too time consuming.
> > > >> > Currently docs and updating to 2.7.0 are the only blockers to
> > pulling
> > > >> the
> > > >> > blackerry/cordova-blackberry repo into Apache. I would really
like
> > to
> > > >> see
> > > >> > this happen this week or early next week.
> > > >> >
> > > >> > - Lorin
> > > >> >
> > > >> >
> > > >> > On Wed, May 1, 2013 at 12:23 PM, Lorin Beer <
> > lorin.beer.dev@gmail.com
> > > >> > >wrote:
> > > >> >
> > > >> > > thanks Bryan
> > > >> > >
> > > >> > > 1. great to hear, once docs are in place, we'll pull those
in
> > > >> alongside
> > > >> > > the core BB implementation
> > > >> > >
> > > >> > > 2. ok, I see. There was a little confusion on our end about
> this.
> > > What
> > > >> > I'd
> > > >> > > like to see is node not visible as an external dependency.
> > > >> > >
> > > >> > > 4. check to see why it's building projects with 2.4.0-rc1
> > > >> > >
> > > >> > > 5. saw that, this will be pulled in alongside docs and the
core
> BB
> > > >> repo
> > > >> > >
> > > >> > >
> > > >> > > On Wed, May 1, 2013 at 12:11 PM, Bryan Higgins <
> > > >> bryan@bryanhiggins.net
> > > >> > >wrote:
> > > >> > >
> > > >> > >> Thanks for following up Lorin.
> > > >> > >>
> > > >> > >> We're actively working on a bunch of things, some of
this
> > included.
> > > >> You
> > > >> > >> can
> > > >> > >> follow commits in the blackberry10 branch on our forks
to keep
> > tabs
> > > >> on
> > > >> > us.
> > > >> > >>
> > > >> > >> I'll go update the JIRA tickets, but here are the answers
to
> your
> > > >> > specific
> > > >> > >> questions:
> > > >> > >>
> > > >> > >> 1. Our docs team is working on these, but they haven't
yet
> pushed
> > > >> > anything
> > > >> > >> to the fork. I'll follow up.
> > > >> > >>
> > > >> > >> 2. We don't actually have node packaged in the repo.
For
> > WebWorks,
> > > >> it is
> > > >> > >> added in during the build process of the distributable.
I'm
> fine
> > > with
> > > >> > >> adding it and I also think it makes sense to call npm
install
> on
> > > >> > >> ./bin/create if the node_modules aren't present.
> > > >> > >>
> > > >> > >> 3. Agree, help message could be improved
> > > >> > >>
> > > >> > >> 4. We re-based the forks a week or so ago, but still
need to
> > bring
> > > in
> > > >> > >> hello
> > > >> > >> world and update versions.
> > > >> > >>
> > > >> > >> 5. We have a fork of cordova-js that introduces blackberry10
> as a
> > > >> > >> platform.
> > > >> > >>
> > > >> > >>
> > > >> > >>
> > > >> > >>
> > > >> > >> On Wed, May 1, 2013 at 2:37 PM, Lorin Beer <
> > > lorin.beer.dev@gmail.com
> > > >> >
> > > >> > >> wrote:
> > > >> > >>
> > > >> > >> > I want to keep the conversation going concerning
the imminent
> > > >> > migration
> > > >> > >> of
> > > >> > >> > BlackBerry's BB10 implementation to Apache Cordova,
replacing
> > the
> > > >> > >> existing
> > > >> > >> > implementation.
> > > >> > >> >
> > > >> > >> > The issues that need to be completed are being
tracked here:
> > > >> > >> > https://issues.apache.org/jira/browse/CB-3070
> > > >> > >> >
> > > >> > >> > With the file system implemented, the BB10 implementation
is
> > > only 3
> > > >> > >> tests
> > > >> > >> > behind the existing Cordova BB10 implementation,
and is
> stable
> > > >> enough
> > > >> > to
> > > >> > >> > accept.
> > > >> > >> > There are, however, a few minor obstacles:
> > > >> > >> >
> > > >> > >> > 1. documentation
> > > >> > >> > - BB10 plugin development
> > > >> > >> > - getting started guide
> > > >> > >> >
> > > >> > >> > both need to be updated to match the new implementation.
If
> > this
> > > >> work
> > > >> > is
> > > >> > >> > done, please point me to it, but I couldn't see
it in the
> > > >> > >> > Blackberry/cordova-docs fork
> > > >> > >> >
> > > >> > >> > 2. create script
> > > >> > >> > the create script for BB10 depends on node. This
is not an
> > issue,
> > > >> as I
> > > >> > >> > understand that node comes packaged with. However,
I would
> like
> > > to
> > > >> see
> > > >> > >> > package configuration to happen automatically (the
npm
> install
> > > >> step)
> > > >> > >> rather
> > > >> > >> > than explicitly.
> > > >> > >> >
> > > >> > >> > 3. project create scripts
> > > >> > >> > needs better help messages and documentation
> > > >> > >> >
> > > >> > >> > 4. 2.7.0 support
> > > >> > >> > build tools seem to use 2.4.0-rc1. This needs to
be brought
> up
> > to
> > > >> > 2.7.0
> > > >> > >> >
> > > >> > >> > 5. cordova-js
> > > >> > >> > it looks like BB10 uses it's own version of cordova.js,
we
> need
> > > to
> > > >> add
> > > >> > >> this
> > > >> > >> > to platforms in cordova-js
> > > >> > >> >
> > > >> > >> > Ken, Bryan and any of the BlackBerry folks, please
chime in
> to
> > > >> correct
> > > >> > >> any
> > > >> > >> > misunderstandings, point us to completed work,
or discuss the
> > > >> above.
> > > >> > >> >
> > > >> > >> > I would also encourage participation on the jira
issue
> > discussion
> > > >> > >> threads.
> > > >> > >> >
> > > >> > >> > - Lorin
> > > >> > >> >
> > > >> > >>
> > > >> > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
> ---------------------------------------------------------------------
> 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