Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.187 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Fri, 3 Feb 2012 10:46:13 -0800
Subject: Re: Work Items for 1.5.0 - unified JS
Thread-Topic: Work Items for 1.5.0 - unified JS
Thread-Index: Aczio+ojVMv8JOX4TuC1yBj/UDfUlA==
Message-ID: <CB516B68.3EC6%fil@adobe.com>
In-Reply-To: 
 <CAMT1KGNBxARwCcRXfzPw_+trjm5XKpcY+_KpZ2WRJbRm+FdZfA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Would something like 9AM PST for Weds 2/8 work?

On 12-02-02 2:38 PM, "Bryce Curtis" <curtis.bryce@gmail.com> wrote:

>Sooner is better - any day between Fri (2/3) and Wed (2/8) are fine - just
>not 2/9,10.
>
>Thanks.
>
>On Thu, Feb 2, 2012 at 4:35 PM, Filip Maj <fil@adobe.com> wrote:
>
>> I was going to wait until the meeting before assigning tasks to get
>> cordova-js in place but I think doing that after 2/16 is late.
>>
>> Should we start working on it ASAP and just have the meeting as a way to
>> get everyone on the same page, then?
>>
>> On 12-02-02 2:29 PM, "Bryce Curtis" <curtis.bryce@gmail.com> wrote:
>>
>> >I can't make 2/9 or 2/10.  Only week of 2/13.
>> >
>> >On Thu, Feb 2, 2012 at 4:19 PM, Filip Maj <fil@adobe.com> wrote:
>> >
>> >> Here are the meeting details, passwords for both call-in and connect
>> >> session should be:
>> >> 12345678
>> >>
>> >> Connect Session
>> >> ----
>> >>
>> >> Name:Cordova-JS Show-n-tell
>> >> Summary:Start Time:02/09/2012 9:00AM PST
>> >> Duration:01:00
>> >> URL:http://my.adobeconnect.com/cordovajs/
>> >>
>> >>
>> >> Call-In Phone Numbers
>> >> ----
>> >> Internal: 6-9900
>> >> Local: 408-536-9900
>> >> International: +1-408-536-9900
>> >> Toll-Free(US & Canada): 877-220-5439
>> >>
>> >>
>> >> Meeting ID: 387077
>> >> Meeting Password: 12345678
>> >>
>> >>
>> >> On 12-02-02 2:05 PM, "Filip Maj" <fil@adobe.com> wrote:
>> >>
>> >> >Just a heads up I will likely sched for 9am PST as I'll be in
>> >>Amsterdam.
>> >> >
>> >> >I'll set it up and send details shortly.
>> >> >
>> >> >On 12-02-02 12:40 PM, "Bryce Curtis" <curtis.bryce@gmail.com> wrote:
>> >> >
>> >> >>2/16 sounds good.
>> >> >>
>> >> >>On Thu, Feb 2, 2012 at 2:33 PM, Brian LeRoux <b@brian.io> wrote:
>> >> >>
>> >> >>> Thu works for me! Can't wait to see this mainlined. Will be good
>>to
>> >> >>> see how you picture the new dev workflow to, uhm, work.
>> >> >>>
>> >> >>>
>> >> >>> On Thu, Feb 2, 2012 at 10:08 AM, Shazron <shazron@gmail.com>
>>wrote:
>> >> >>> > Sounds good - set up a meeting invite for a time best for you,
>>we
>> >>can
>> >> >>> > go on Connect
>> >> >>> >
>> >> >>> > On Thu, Feb 2, 2012 at 9:59 AM, Filip Maj <fil@adobe.com>
>>wrote:
>> >> >>> >> Shaz why don't we plan for some mutual programming sessions
>> >>(online?
>> >> >>>In
>> >> >>> >> person?) for the week of the 13th?
>> >> >>> >>
>> >> >>> >> On 12-02-02 9:48 AM, "Shazron" <shazron@gmail.com> wrote:
>> >> >>> >>
>> >> >>> >>>Sounds good for me whenever you are available Fil (although
>>I'm
>> >>away
>> >> >>> >>>Feb 23 until early Mar)
>> >> >>> >>>
>> >> >>> >>>On Wed, Feb 1, 2012 at 3:14 PM, Filip Maj <fil@adobe.com>
>>wrote:
>> >> >>> >>>> I'm in transit early next week to Europe and presenting/at a
>> >> >>> conference
>> >> >>> >>>> mid-week. I can do late next-week though (Thursday?). Or the
>> >> >>>following
>> >> >>> >>>> week once im back in north america.
>> >> >>> >>>>
>> >> >>> >>>> On 12-02-01 2:58 PM, "Bryce Curtis" <curtis.bryce@gmail.com>
>> >> >>>wrote:
>> >> >>> >>>>
>> >> >>> >>>>>Having a session would be helpful.  Early next week (Mon/Tue
>> >> >>> >>>>>11PT/1CT/2ET)
>> >> >>> >>>>>would be good.
>> >> >>> >>>>>
>> >> >>> >>>>>On Wed, Feb 1, 2012 at 4:29 PM, Steven Gill
>> >> >>><stevengill97@gmail.com>
>> >> >>> >>>>>wrote:
>> >> >>> >>>>>
>> >> >>> >>>>>> +1 on connect session
>> >> >>> >>>>>>
>> >> >>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fil@adobe.com>
>> >> wrote:
>> >> >>> >>>>>>
>> >> >>> >>>>>> > The JS code base is pretty much there. Works on Android.
>> >>Works
>> >> >>> >>>>>>almost
>> >> >>> >>>>>> > completely on BB + PlayBook. I'll need help to get it
>> >>working
>> >> >>>on
>> >> >>> >>>>>>iOS +
>> >> >>> >>>>>> the
>> >> >>> >>>>>> > other platforms. It's here:
>> >> >>> http://github.com/callback/callback-js
>> >> >>> >>>>>> >
>> >> >>> >>>>>> > If there is enough interest, I am down for setting up a
>> >>public
>> >> >>> >>>>>>Connect
>> >> >>> >>>>>> > session where I can go over the implementations Gord
>>Tanner
>> >> >>>and I
>> >> >>> >>>>>>have
>> >> >>> >>>>>> been
>> >> >>> >>>>>> > working on so people can get a feel for how this stuff
>>is
>> >>laid
>> >> >>> out.
>> >> >>> >>>>>> >
>> >> >>> >>>>>> > Some general notes about changes that we will need for
>>all
>> >> >>>native
>> >> >>> >>>>>> > implementations:
>> >> >>> >>>>>> >
>> >> >>> >>>>>> >  *   Change all of the JavaScript references in the
>>native
>> >> >>> >>>>>> > implementations. No more global references in native. No
>> >>more
>> >> >>> random
>> >> >>> >>>>>> > "_cast" global methods that convert native return values
>> >>into
>> >> >>>JS
>> >> >>> >>>>>>objects
>> >> >>> >>>>>> or
>> >> >>> >>>>>> > whatnot - the JS implementation should be doing this
>> >>anyways.
>> >> >>> >>>>>> >  *   Make all plugin service names consistent
>> >> >>> >>>>>> >  *   Make all plugin action names consistent
>> >> >>> >>>>>> >  *   Normalize file:/// URIs across platforms for the
>>File
>> >> >>>API.
>> >> >>> I.e.
>> >> >>> >>>>>>iOS
>> >> >>> >>>>>> > uses file:///localhost/, BB uses just file:///, android
>> >>uses
>> >> >>> >>>>>>something
>> >> >>> >>>>>> > else, etc.
>> >> >>> >>>>>> >  *   Figure out (i.e. axe) what to do with
>> >>platform-specific
>> >> >>>APIs
>> >> >>> >>>>>> > (Android's Crypto, iOS SMS+Telephony)
>> >> >>> >>>>>> >  *   Normalize error objects returned from native across
>> >>all
>> >> >>> >>>>>>platforms
>> >> >>> >>>>>> >  *
>> >> >>> >>>>>> >
>> >> >>> >>>>>> > Platform-specific notes:
>> >> >>> >>>>>> >
>> >> >>> >>>>>> >  *   Android, I have a unified-js branch up on my fork
>> >>that we
>> >> >>> just
>> >> >>> >>>>>>need
>> >> >>> >>>>>> > to merge in:
>> >> >>> >>>>>> >
>> >> >>>=20
>>https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >> >>> >>>>>> >  *   BlackBerry, I have the same thing going on but it
>>is
>> >>at
>> >> >>>about
>> >> >>> >>>>>>80%:
>> >> >>> >>>>>> >
>> >> >>> >>>>>>
>> >> >>> >>>>>>
>> >> >>>
>> >>=20
>>https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/un
>> >> >>> >>>>>>if
>> >> >>> >>>>>>ied-js
>> >> >>> >>>>>> >  *   For all other platforms, I'd love to do some hack
>> >> >>>sessions
>> >> >>> with
>> >> >>> >>>>>>the
>> >> >>> >>>>>> > platform owner(s) to go over what is required. Looking
>>for
>> >> >>> >>>>>>volunteers
>> >> >>> >>>>>>:)
>> >> >>> >>>>>> >
>> >> >>> >>>>>> > Other things I'd like to get into the cordova-js project
>> >> >>>before
>> >> >>> 1.5:
>> >> >>> >>>>>> >
>> >> >>> >>>>>> >  *   move all unit-testy stuff from mobile-spec into the
>> >> >>> cordova-js
>> >> >>> >>>>>>unit
>> >> >>> >>>>>> > tests
>> >> >>> >>>>>> >  *   Once we have cordova-js working on platforms (the
>>big
>> >>3?
>> >> >>>BB
>> >> >>> >>>>>>Android
>> >> >>> >>>>>> > iOS?), we'll need to once-over the API docs again as
>>some
>> >> >>>stuff in
>> >> >>> >>>>>>there
>> >> >>> >>>>>> > will no longer be relevant (I.e. Platform-specific
>>quirks)
>> >> >>> >>>>>> >
>> >> >>> >>>>>> > I'm looking to get started on this right away. The
>>sooner I
>> >> >>>can
>> >> >>> get
>> >> >>> >>>>>>help
>> >> >>> >>>>>> > from platform maintainers in integrating cordova-js into
>> >>the
>> >> >>> project
>> >> >>> >>>>>>the
>> >> >>> >>>>>> > better.
>> >> >>> >>>>>> >
>> >> >>> >>>>>>
>> >> >>> >>>>
>> >> >>> >>
>> >> >>>
>> >> >
>> >>
>> >>
>>
>>