Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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: https://github.com/filmaj/incubator-cordova-android/tree/unified-js
 *   BlackBerry, I have the same thing going on but it is at about 80%: https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/unified-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.

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

Also it may help to look at the Ripple Codebase:
https://github.com/blackberry/Ripple-UI/

The overall architecture was inspired by Ripple and has also been
also loosely influencing the next generation implementation of the webworks
platform on BB10:
https://github.com/blackberry-webworks/BB10-WebWorks-Framework

On Tue, Feb 7, 2012 at 9:05 AM, Filip Maj <fi...@adobe.com> wrote:

> Good call Pat.
>
> The exact repo I'll be going over is located at
> https://github.com/callback/callback-js (still waiting on a git home at
> Apache, INFRA ticket filed).
>
> I've got a branch of the incubator-cordova-android repository with all
> changes necessary to get cordova-js integrated into the android
> implementation here:
>
> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>
> Using github's handy compare feature, you can compare it to the master
> branch here:
>
> https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
> d-js
>
>
> For the above "comparison" view, ignore most of the Media-related code.
> Essentially we need to stop referencing JavaScript globals from native.
> Examples of these sorts of changes:
>
> - firing nativeready:
> https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
> d-js#L12L207
> - firing pause/resume events from native:
> https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
> d-js#L15L850
> - invoking callback success/error handlers for different APIS:
> https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
> d-js#L17L103
>
> Other important things to highlight in Cordova-JS:
>
> - build/packager.js:
> https://github.com/callback/callback-js/blob/master/build/packager.js -
> this module handles reading and compiling the various .js files in the
> cordova-js repo together into cordova.<platform>.js files. When you run
> "jake" from the repo root, that invokes the "bundle" function from this
> module.
> - lib/platform: .js files in here define the global objects that will be
> dropped once phonegap is ready to boot. Most are platform-specific
> definitions and are quite small. There is one, called common.js, common to
> all platforms, that is the biggest. Basically all the globla namespaces ->
> JS module mappings are defined here.
> - lib/phonegap.js:
> https://github.com/callback/callback-js/blob/master/lib/phonegap.js - does
> the add/removeEventListener hijacking that is common to all platforms, and
> exposes callbackSuccess/error handlers to native.
> - lib/channel.js:
> https://github.com/callback/callback-js/blob/master/lib/channel.js - event
> emitter/listener that we use for all phonegap events such as nativeReady,
> deviceReady, etc.
> - lib/bootstrap.js:
> https://github.com/callback/callback-js/blob/master/lib/bootstrap.js -
> "boot" function defined here is what initializes phonegap. It'll run
> through the platform definitions (lib/platform) and drop the modules
> referenced in there into the appropriate name spaces in JS.
>
> That's more than enough for you guys to chew on I think :)
>
> Let me know if there's anything else I can provide!
>
> On 12-02-07 2:44 PM, "Patrick Mueller" <pm...@gmail.com> wrote:
>
> >On Tue, Feb 7, 2012 at 04:17, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Friendly reminder that I've set up the cordovajs show-n-tell for
> >>TOMORROW
> >> (Wednesday Feb 8th) for 9AM PST.
> >>
> >
> >Great!
> >
> >Could you post some links to relevant projects floating out there in the
> >ether?  I'd like to be able to see look over the code before the
> >show-n-tell.
> >
> >--
> >Patrick Mueller
> >http://muellerware.org
>
>


-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Thu, Feb 9, 2012 at 12:08, Filip Maj <fi...@adobe.com> wrote:

> On 12-02-08 4:14 PM, "Patrick Mueller" <pm...@gmail.com> wrote:
> >real 0m0.193s
> >user 0m0.160s
> >sys 0m0.037s
> >══════════════════════════
> >
> >Um.  Wowsa.
>
> Sorry, are the above numbers slow or fast? I can't tell by your response :)
>

Fast.  Fast!!!!  weinre build is currently taking ~5 seconds; this gives me
a target to shoot for!

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

On 12-02-08 4:14 PM, "Patrick Mueller" <pm...@gmail.com> wrote:

>Running 'jake', I figured I must have done something wrong, since it
>returned to the command-line immediately.  But sure enough, files got
>pooped into the /pkg directory, so ... I guess it worked.  Decided to
>instrument it (and remove the dalek - come on!) just to be sure:
>
>══════════════════════════
>10:06:14 ~/Projects/callback-js
>▶ time jake
>bundling: blackberry
>bundling: playbook
>bundling: ios
>bundling: wp7
>bundling: android
>
>real 0m0.193s
>user 0m0.160s
>sys 0m0.037s
>══════════════════════════
>
>Um.  Wowsa.  

Sorry, are the above numbers slow or fast? I can't tell by your response :)

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

Running 'jake', I figured I must have done something wrong, since it
returned to the command-line immediately.  But sure enough, files got
pooped into the /pkg directory, so ... I guess it worked.  Decided to
instrument it (and remove the dalek - come on!) just to be sure:

══════════════════════════
10:06:14 ~/Projects/callback-js
▶ time jake
bundling: blackberry
bundling: playbook
bundling: ios
bundling: wp7
bundling: android

real 0m0.193s
user 0m0.160s
sys 0m0.037s
══════════════════════════

Um.  Wowsa.  I added a .wr file [1] to the root, and ran 'wr' from the
command-line, and now it rebuilds whenever I change a file.

══════════════════════════
--stdoutcolor blue
--stderrcolor red

#-----------------------------------------------------
# command to run
#-----------------------------------------------------

time jake

#-----------------------------------------------------
# files/directories to watch
#-----------------------------------------------------

.wr
build
jakefile
lib
package.json
test
══════════════════════════

══════════════════════════
10:06:19 ~/Projects/callback-js
▶ wr
10:13:02 wr: watching 112 files, running 'time jake'
10:13:08 wr: running 'time jake'
bundling: blackberry
bundling: playbook
bundling: ios
bundling: wp7
bundling: android
        0.25 real         0.19 user         0.04 sys
10:13:08 wr: command succeeded
10:13:30 wr: running 'time jake'
bundling platform: blackberry
bundling platform: playbook
bundling platform: ios
bundling platform: wp7
bundling platform: android
        0.23 real         0.19 user         0.03 sys
10:13:30 wr: command succeeded
══════════════════════════

[1] https://github.com/pmuellr/wr

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Anis KADRI <an...@gmail.com>]

For Symbian (which is now Qt), I told the guys about the project and
they should have started looking into it by now. I will ping them
again about it.

No idea for webOS.

On Mon, Feb 13, 2012 at 2:30 PM, Filip Maj <fi...@adobe.com> wrote:
> Status update for everyone.
>
> - Looks like Simon has done a good chunk of work to eliminate native cruft
> on the Android implementation (moving stuff from native into JavaScript
> where possible). Thank you Simon! It is working and complete on Android -
> the first cordova platform to support cordova-js. That is awesome! Final
> step: it would be awesome if one of the Android platform "owners"
> (Joe/Simon) can take the unified-js branch of the native code from my fork
> (https://github.com/filmaj/incubator-cordova-android/tree/unified-js),
> rebase/merge as needed and run through the tests and make sure the latest
> changes such as the PhoneGap->Cordova name change didn't mess anything up.
> Then we can put the cordova-js seal of approval on Android :D
> - I am working out the kinks with WP7+cordova-js (and node.js) integration
> on Windows this week.
> - Shaz is working out name change to cordova stuff on native ios. Shaz and
> I have a remote hack session planned for mid-week to get the ball rolling
> with cordova-js integration. I have a todo list of needed changes for ios
> integration so hopefully that won't be too tough. I am going to try to get
> it running on the sim on my dev machine before then anyways.
> - The PhoneGap-to-Cordova name change on the BlackBerry implementation
> seems to have messed up cordova-js working on that platform. I made a few
> changes to get us back on track but it's still not working. Gord will take
> a look when he can.
> - Anis is setting up platform definitions for Bada (only v2.0? Both 1.0
> and 2.0?) in cordova-js this week. Bada 1.0 vs. 2.0 will be separate
> implementations anyways so we should treat them as separate platforms in
> cordova-js. He still needs to iron out the native-to-JS bridge on Bada 2.0
> though.
> - Also need to work out the kinks on PlayBook. We are still missing File
> API on PlayBook but we may be able to re-use BlackBerry Smartphone
> WebWorks code for that (not sure still need to investigate).
>
> What about webOS and Symbian? Are we gonna roll out cordova-js for those
> platforms too? My intuition is no until those platforms require updates...
>

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

Gord: WebInspector and BlackBerry OS 7 simulator to the rescue :-)

On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com> wrote:
> OMFG!
>
> You just saved my day!
>
> I have been looking for why blackberry wasn't firing device ready and that
> bad module ID was it!  I was circling around the channel code attempting to
> figure out why it wasn't joining after the device and network channels were
> fired.
>
> Gonna look into this and pull it in, looks good at first glance.
>
>
> Gord
>
> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com> wrote:
>
>> Ok, I've submitted a pull request with my changes.
>>
>> https://github.com/callback/callback-js/pull/17
>>
>> In my previous email, #3 was due to where I had inserted #2 (oops).
>> The changes are mostly phonegap -> cordova changes.  Additionally I
>> had to fix a module require in lib/platform/blackberry.js which was
>> specifying a bad module name.
>>
>> The only appearance of phonegap in common-js after my change is in the
>> iOS and WP7 plugins where they reference native code since I didn't
>> think those had been renamed yet.
>>
>> Eventually the BlackBerry native side should make use of require (as
>> shown in Fil's commit), but that will wait till common-js gets added
>> to apache source. For the time being a quick hack is to add the
>> following at the bottom of the generated js:
>>
>> var Cordova = require('cordova');
>>
>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com> wrote:
>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
>> > pull request yet because I'm still debugging something.  Here's
>> > summary of changes I've made:
>> >
>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>> > 2. Added a global define of "Cordova" as a temporary hack since native
>> > PluginResult.toSuccessCallbackString expects it to exist.
>> > 3. For some reason I had to make sure the cordova/utils module exists
>> > in cordova.js before the cordova/channel module, otherwise I was
>> > getting an error that the module didn't exist.
>> >
>> > With the above changes I was able to run some simple tests (verified
>> > network works).  I'm currently looking at proper fix for #2 and #3.
>> >
>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>> wrote:
>> >> I'm looking at https://github.com/callback/callback-js and I see a lot
>> >> of references to "phonegap" in the lib/plugins directory though it
>> >> seems like things one directory up (lib) has been changed.  Am I not
>> >> looking at an up to date project or should I send a pull request with
>> >> that name change too?
>> >>
>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>> wrote:
>> >>> I am on BlackBerry today.
>> >>>
>> >>> Currently showing:
>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>> >>>
>> >>> I will attempt to get it up and running again today.
>> >>>
>> >>> I also have the start of a node runner for callback-js tests here:
>> >>> https://github.com/gtanner/callback-js
>> >>>
>> >>> Gord
>> >>>
>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net>
>> wrote:
>> >>>
>> >>>> Can you please drop me a line once cordova-js is on the official
>> repos &
>> >>>> mirrored? I will then give integrating the new common-JS into
>> cordova-qt a
>> >>>> go!
>> >>>>
>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>> >>>>
>> >>>>  Update on unified JavaScript work in cordova for today:
>> >>>>>
>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>> which is a
>> >>>>> hurdle in making sure it supports the cross-platform cordova API.
>> Before
>> >>>>> we can move forward with cordova-js integration we really need to
>> figure
>> >>>>> that part of it out.
>> >>>>> - I will work rest of day in getting cordova-js into the apache git
>> repo
>> >>>>> and finishing up that work.
>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to
>> get
>> >>>>> iOS on track. Will have a better idea how that platform is looking
>> >>>>> tomorrow.
>> >>>>> - Bada 2.0 still needs a platform implementation before we can move
>> with
>> >>>>> cordova-js on it.
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> GOFG - Get On Fat Guy
>> >>>> http://www.gofg.at/ - powered by Cordova
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Gord Tanner
>> >>> Senior Developer / Code Poet
>> >>> tinyHippos Inc.
>> >>> @tinyhippos
>>
>
>
>
> --
> Gord Tanner
> Senior Developer / Code Poet
> tinyHippos Inc.
> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

As long as we don't git-submodule it... cause that hurts ;)

On Wed, Feb 15, 2012 at 12:15 PM, Filip Maj <fi...@adobe.com> wrote:

> I think it'd be a pain to submodule cordova-js into the platform repos.
>
> So far the general agreement is to "vendor" cordova-js in as a built
> script.
>
> It should only get out of sync if we let it :)
>
> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>
> >I need to do some more testing before I agree to move it to the apache
> >code.  Wanted to get the name change in completely first.  Right now
> >some of the api aren't working in my test app.
> >
> >This brings up a point though.  What will this look like once its
> >moved to apache.  I would assume we'll have a separate repo for
> >cordova-js, but do the individual platforms really need a copy of the
> >built js file?  From an end user perspective this could just be
> >handled at packaging time when we build the distributable binary.
> >Seems like including a built js from cordova-js would lead to it
> >getting out of sync.
> >
> >On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
> wrote:
> >> OMFG!
> >>
> >> You just saved my day!
> >>
> >> I have been looking for why blackberry wasn't firing device ready and
> >>that
> >> bad module ID was it!  I was circling around the channel code
> >>attempting to
> >> figure out why it wasn't joining after the device and network channels
> >>were
> >> fired.
> >>
> >> Gonna look into this and pull it in, looks good at first glance.
> >>
> >>
> >> Gord
> >>
> >> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
> >>wrote:
> >>
> >>> Ok, I've submitted a pull request with my changes.
> >>>
> >>> https://github.com/callback/callback-js/pull/17
> >>>
> >>> In my previous email, #3 was due to where I had inserted #2 (oops).
> >>> The changes are mostly phonegap -> cordova changes.  Additionally I
> >>> had to fix a module require in lib/platform/blackberry.js which was
> >>> specifying a bad module name.
> >>>
> >>> The only appearance of phonegap in common-js after my change is in the
> >>> iOS and WP7 plugins where they reference native code since I didn't
> >>> think those had been renamed yet.
> >>>
> >>> Eventually the BlackBerry native side should make use of require (as
> >>> shown in Fil's commit), but that will wait till common-js gets added
> >>> to apache source. For the time being a quick hack is to add the
> >>> following at the bottom of the generated js:
> >>>
> >>> var Cordova = require('cordova');
> >>>
> >>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
> >>>wrote:
> >>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
> >>> > pull request yet because I'm still debugging something.  Here's
> >>> > summary of changes I've made:
> >>> >
> >>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
> >>> > 2. Added a global define of "Cordova" as a temporary hack since
> >>>native
> >>> > PluginResult.toSuccessCallbackString expects it to exist.
> >>> > 3. For some reason I had to make sure the cordova/utils module exists
> >>> > in cordova.js before the cordova/channel module, otherwise I was
> >>> > getting an error that the module didn't exist.
> >>> >
> >>> > With the above changes I was able to run some simple tests (verified
> >>> > network works).  I'm currently looking at proper fix for #2 and #3.
> >>> >
> >>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
> >>> wrote:
> >>> >> I'm looking at https://github.com/callback/callback-js and I see a
> >>>lot
> >>> >> of references to "phonegap" in the lib/plugins directory though it
> >>> >> seems like things one directory up (lib) has been changed.  Am I not
> >>> >> looking at an up to date project or should I send a pull request
> >>>with
> >>> >> that name change too?
> >>> >>
> >>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
> >>> wrote:
> >>> >>> I am on BlackBerry today.
> >>> >>>
> >>> >>> Currently showing:
> >>> >>> Error: SyntaxError: Unable to parse JSON string alert.
> >>> >>>
> >>> >>> I will attempt to get it up and running again today.
> >>> >>>
> >>> >>> I also have the start of a node runner for callback-js tests here:
> >>> >>> https://github.com/gtanner/callback-js
> >>> >>>
> >>> >>> Gord
> >>> >>>
> >>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
> >>><vi...@users.sourceforge.net>
> >>> wrote:
> >>> >>>
> >>> >>>> Can you please drop me a line once cordova-js is on the official
> >>> repos &
> >>> >>>> mirrored? I will then give integrating the new common-JS into
> >>> cordova-qt a
> >>> >>>> go!
> >>> >>>>
> >>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
> >>> >>>>
> >>> >>>>  Update on unified JavaScript work in cordova for today:
> >>> >>>>>
> >>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
> >>> which is a
> >>> >>>>> hurdle in making sure it supports the cross-platform cordova API.
> >>> Before
> >>> >>>>> we can move forward with cordova-js integration we really need to
> >>> figure
> >>> >>>>> that part of it out.
> >>> >>>>> - I will work rest of day in getting cordova-js into the apache
> >>>git
> >>> repo
> >>> >>>>> and finishing up that work.
> >>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
> >>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
> >>>morning to
> >>> get
> >>> >>>>> iOS on track. Will have a better idea how that platform is
> >>>looking
> >>> >>>>> tomorrow.
> >>> >>>>> - Bada 2.0 still needs a platform implementation before we can
> >>>move
> >>> with
> >>> >>>>> cordova-js on it.
> >>> >>>>>
> >>> >>>>
> >>> >>>> --
> >>> >>>> GOFG - Get On Fat Guy
> >>> >>>> http://www.gofg.at/ - powered by Cordova
> >>> >>>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> --
> >>> >>> Gord Tanner
> >>> >>> Senior Developer / Code Poet
> >>> >>> tinyHippos Inc.
> >>> >>> @tinyhippos
> >>>
> >>
> >>
> >>
> >> --
> >> Gord Tanner
> >> Senior Developer / Code Poet
> >> tinyHippos Inc.
> >> @tinyhippos
>
>


-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Thanks for that! I'll take a look today

On 12-02-16 9:18 AM, "Drew Walters" <de...@gmail.com> wrote:

>Yes it does run but that error is pretty ugly and its not immediately
>obvious that it built successfully.
>
>I've submitted a pull request to add in button overriding and some app
>life cycle behavior for BlackBerry.  The life cycle is still not what
>it use to be so there is still more work to be done there.  I also
>fixed a bug in the builder code that wasn't properly handling clobber
>when the parent object doesn't define a path (ie. navigator.app was
>not getting injected under navigator).
>
>https://github.com/callback/callback-js/pull/21
>
>FYI, I'm out on vacation this afternoon and won't be back till Tuesday
>but wanted to get this code up there.
>
>On Wed, Feb 15, 2012 at 2:58 PM, Gord Tanner <go...@tinyhippos.com> wrote:
>> You should still be able to run jake and it will build (and have an
>>error
>> about no jsDom).
>>
>> Got rid of a bunch of unused modules (anyone know why jQuery was in
>>there?)
>> and thirdparty code.
>>
>> 
>>https://github.com/callback/callback-js/commit/bb6cd42e1b5a56c2cd9642e8ac
>>e386ffcc0b4ce3
>>
>>
>> On Wed, Feb 15, 2012 at 2:35 PM, Drew Walters <de...@gmail.com>
>>wrote:
>>
>>> Gord,
>>>
>>> Looks like jsDom adds a requirement for the system to have a compiler.
>>>  Since I don't (and maybe others) have XCode installed on my Mac for
>>> legal reasons, the configure script fails for me now.
>>>
>>> On Wed, Feb 15, 2012 at 12:41 PM, Filip Maj <fi...@adobe.com> wrote:
>>> > Awwwww yeauuhhh
>>> >
>>> > Thanks Gord :D
>>> >
>>> > On 12-02-15 10:31 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:
>>> >
>>> >>Quick note:
>>> >>
>>> >>I added a node runner for our unit tests that will run for every
>>>build:
>>> >>
>>> >>
>>> 
>>>https://github.com/callback/callback-js/blob/master/test/runner.js#L23-5
>>>8
>>> >>
>>> >>If you have already been developing cordova.js you will need to run
>>> >>./configure again to pull down jsDom to build.
>>> >>
>>> >>The intent is that these tests will test the javascript code (mocking
>>> >>interactions to native) and should be kept green.
>>> >>
>>> >>This is not a replacement for cordova-test but a place for us to
>>>quickly
>>> >>spec and test our javascript without the need to load or build into a
>>> >>simulator.
>>> >>
>>> >>to run the tests in node:
>>> >>
>>> >>jake
>>> >>or
>>> >>jake test
>>> >>
>>> >>to run the tests in the browser:
>>> >>jake btest
>>> >>
>>> >>Gord
>>> >>
>>> >>On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:
>>> >>
>>> >>> Ahh, so more of a packaging question. I'm not sure. I know Steve is
>>> >>> working on a packaging script so certainly integrating a cordova-js
>>> >>>build
>>> >>> into that makes sense.
>>> >>>
>>> >>> I think you're on the right track, Drew. We used to include
>>>phonegap.js
>>> >>> into the sample app packaged in each repo - maybe we can keep with
>>>that
>>> >>> same theme for cordova-js and just add some stuff into the README
>>> >>> regarding where to get/build the latest cordova-js.
>>> >>>
>>> >>> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
>>> >>>
>>> >>> >I think the way I stated my question is confusing.  Let me try
>>>again.
>>> >>> >Right now the incubator-cordova-blackberry-webworks repo contains
>>>both
>>> >>> >the JS and native code.  Some time soon I would anticipate a
>>> >>> >incubator-cordova-js repo.  At that time the JS files in the
>>>webworks
>>> >>> >repo should go away.
>>> >>> >
>>> >>> >It seems to me that the "vendor" in of a platform specific
>>>cordova.js
>>> >>> >should happen when we build the end user package (ie. the one
>>> >>> >currently at phonegap.com).  At development time, I'm always
>>>going to
>>> >>> >want the latest one out of incubator-cordova-js so I can just
>>>build
>>> >>> >that myself.  Unless of course there is some mechanism to
>>> >>> >automatically build incubator-cordova-js when it is updated and
>>>copy
>>> >>> >the built files to the platform repos.
>>> >>> >
>>> >>> >Am I wrong?
>>> >>> >
>>> >>> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
>>> >>> >> I think it'd be a pain to submodule cordova-js into the platform
>>> >>>repos.
>>> >>> >>
>>> >>> >> So far the general agreement is to "vendor" cordova-js in as a
>>>built
>>> >>> >> script.
>>> >>> >>
>>> >>> >> It should only get out of sync if we let it :)
>>> >>> >>
>>> >>> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>>> >>> >>
>>> >>> >>>I need to do some more testing before I agree to move it to the
>>> >>>apache
>>> >>> >>>code.  Wanted to get the name change in completely first.
>>>Right now
>>> >>> >>>some of the api aren't working in my test app.
>>> >>> >>>
>>> >>> >>>This brings up a point though.  What will this look like once
>>>its
>>> >>> >>>moved to apache.  I would assume we'll have a separate repo for
>>> >>> >>>cordova-js, but do the individual platforms really need a copy
>>>of
>>> the
>>> >>> >>>built js file?  From an end user perspective this could just be
>>> >>> >>>handled at packaging time when we build the distributable
>>>binary.
>>> >>> >>>Seems like including a built js from cordova-js would lead to it
>>> >>> >>>getting out of sync.
>>> >>> >>>
>>> >>> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner
>>><go...@tinyhippos.com>
>>> >>> >>>wrote:
>>> >>> >>>> OMFG!
>>> >>> >>>>
>>> >>> >>>> You just saved my day!
>>> >>> >>>>
>>> >>> >>>> I have been looking for why blackberry wasn't firing device
>>>ready
>>> >>>and
>>> >>> >>>>that
>>> >>> >>>> bad module ID was it!  I was circling around the channel code
>>> >>> >>>>attempting to
>>> >>> >>>> figure out why it wasn't joining after the device and network
>>> >>>channels
>>> >>> >>>>were
>>> >>> >>>> fired.
>>> >>> >>>>
>>> >>> >>>> Gonna look into this and pull it in, looks good at first
>>>glance.
>>> >>> >>>>
>>> >>> >>>>
>>> >>> >>>> Gord
>>> >>> >>>>
>>> >>> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <
>>> deedubbu@gmail.com>
>>> >>> >>>>wrote:
>>> >>> >>>>
>>> >>> >>>>> Ok, I've submitted a pull request with my changes.
>>> >>> >>>>>
>>> >>> >>>>> https://github.com/callback/callback-js/pull/17
>>> >>> >>>>>
>>> >>> >>>>> In my previous email, #3 was due to where I had inserted #2
>>> >>>(oops).
>>> >>> >>>>> The changes are mostly phonegap -> cordova changes.
>>>Additionally
>>> >>>I
>>> >>> >>>>> had to fix a module require in lib/platform/blackberry.js
>>>which
>>> >>>was
>>> >>> >>>>> specifying a bad module name.
>>> >>> >>>>>
>>> >>> >>>>> The only appearance of phonegap in common-js after my change
>>>is
>>> in
>>> >>> >>>>>the
>>> >>> >>>>> iOS and WP7 plugins where they reference native code since I
>>> >>>didn't
>>> >>> >>>>> think those had been renamed yet.
>>> >>> >>>>>
>>> >>> >>>>> Eventually the BlackBerry native side should make use of
>>>require
>>> >>>(as
>>> >>> >>>>> shown in Fil's commit), but that will wait till common-js
>>>gets
>>> >>>added
>>> >>> >>>>> to apache source. For the time being a quick hack is to add
>>>the
>>> >>> >>>>> following at the bottom of the generated js:
>>> >>> >>>>>
>>> >>> >>>>> var Cordova = require('cordova');
>>> >>> >>>>>
>>> >>> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <
>>> deedubbu@gmail.com>
>>> >>> >>>>>wrote:
>>> >>> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't
>>> >>>submitted
>>> >>> >>>>> > pull request yet because I'm still debugging something.
>>>Here's
>>> >>> >>>>> > summary of changes I've made:
>>> >>> >>>>> >
>>> >>> >>>>> > 1. Modify rest of files to use "cordova" instead of
>>>"phonegap".
>>> >>> >>>>> > 2. Added a global define of "Cordova" as a temporary hack
>>>since
>>> >>> >>>>>native
>>> >>> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>>> >>> >>>>> > 3. For some reason I had to make sure the cordova/utils
>>>module
>>> >>> >>>>>exists
>>> >>> >>>>> > in cordova.js before the cordova/channel module, otherwise
>>>I
>>> was
>>> >>> >>>>> > getting an error that the module didn't exist.
>>> >>> >>>>> >
>>> >>> >>>>> > With the above changes I was able to run some simple tests
>>> >>> >>>>>(verified
>>> >>> >>>>> > network works).  I'm currently looking at proper fix for
>>>#2 and
>>> >>>#3.
>>> >>> >>>>> >
>>> >>> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters
>>> >>><de...@gmail.com>
>>> >>> >>>>> wrote:
>>> >>> >>>>> >> I'm looking at https://github.com/callback/callback-js
>>>and I
>>> >>>see
>>> >>> a
>>> >>> >>>>>lot
>>> >>> >>>>> >> of references to "phonegap" in the lib/plugins directory
>>> >>>though it
>>> >>> >>>>> >> seems like things one directory up (lib) has been
>>>changed.  Am
>>> >>>I
>>> >>> >>>>>not
>>> >>> >>>>> >> looking at an up to date project or should I send a pull
>>> >>>request
>>> >>> >>>>>with
>>> >>> >>>>> >> that name change too?
>>> >>> >>>>> >>
>>> >>> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner
>>> >>><gord@tinyhippos.com
>>> >>> >
>>> >>> >>>>> wrote:
>>> >>> >>>>> >>> I am on BlackBerry today.
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> Currently showing:
>>> >>> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> I will attempt to get it up and running again today.
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> I also have the start of a node runner for callback-js
>>>tests
>>> >>> >>>>>here:
>>> >>> >>>>> >>> https://github.com/gtanner/callback-js
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> Gord
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>>> >>> >>>>><vi...@users.sourceforge.net>
>>> >>> >>>>> wrote:
>>> >>> >>>>> >>>
>>> >>> >>>>> >>>> Can you please drop me a line once cordova-js is on the
>>> >>>official
>>> >>> >>>>> repos &
>>> >>> >>>>> >>>> mirrored? I will then give integrating the new common-JS
>>> into
>>> >>> >>>>> cordova-qt a
>>> >>> >>>>> >>>> go!
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
>>> >>> >>>>> >>>>>
>>> >>> >>>>> >>>>> - looks like the WP7 implementation cannot run our
>>> >>>mobile-spec,
>>> >>> >>>>> which is a
>>> >>> >>>>> >>>>> hurdle in making sure it supports the cross-platform
>>> cordova
>>> >>> >>>>>API.
>>> >>> >>>>> Before
>>> >>> >>>>> >>>>> we can move forward with cordova-js integration we
>>>really
>>> >>>need
>>> >>> >>>>>to
>>> >>> >>>>> figure
>>> >>> >>>>> >>>>> that part of it out.
>>> >>> >>>>> >>>>> - I will work rest of day in getting cordova-js into
>>>the
>>> >>>apache
>>> >>> >>>>>git
>>> >>> >>>>> repo
>>> >>> >>>>> >>>>> and finishing up that work.
>>> >>> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you
>>> >>>available?
>>> >>> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for
>>>tomorrow
>>> >>> >>>>>morning to
>>> >>> >>>>> get
>>> >>> >>>>> >>>>> iOS on track. Will have a better idea how that
>>>platform is
>>> >>> >>>>>looking
>>> >>> >>>>> >>>>> tomorrow.
>>> >>> >>>>> >>>>> - Bada 2.0 still needs a platform implementation
>>>before we
>>> >>>can
>>> >>> >>>>>move
>>> >>> >>>>> with
>>> >>> >>>>> >>>>> cordova-js on it.
>>> >>> >>>>> >>>>>
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>> --
>>> >>> >>>>> >>>> GOFG - Get On Fat Guy
>>> >>> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>
>>> >>> >>>>> >>>
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> --
>>> >>> >>>>> >>> Gord Tanner
>>> >>> >>>>> >>> Senior Developer / Code Poet
>>> >>> >>>>> >>> tinyHippos Inc.
>>> >>> >>>>> >>> @tinyhippos
>>> >>> >>>>>
>>> >>> >>>>
>>> >>> >>>>
>>> >>> >>>>
>>> >>> >>>> --
>>> >>> >>>> Gord Tanner
>>> >>> >>>> Senior Developer / Code Poet
>>> >>> >>>> tinyHippos Inc.
>>> >>> >>>> @tinyhippos
>>> >>> >>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >>--
>>> >>Gord Tanner
>>> >>Senior Developer / Code Poet
>>> >>tinyHippos Inc.
>>> >>@tinyhippos
>>> >
>>>
>>
>>
>>
>> --
>> Gord Tanner
>> Senior Developer / Code Poet
>> tinyHippos Inc.
>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Nice job Joe, that is rad! So stoked to see it working well across ICS and
Gingerbread.

On 12-02-17 4:34 PM, "Joe Bowser" <bo...@gmail.com> wrote:

>Hey
>
>I got this down to 26 failed tests on ICS after overriding FileError.
> There seems to be issues with the DirectoryReader as well, but at least
>it's only 5 failures more than Gingerbread.  I pushed it up to the
>repository.
>
>Joe
>
>On Fri, Feb 17, 2012 at 3:45 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Awesome Bryce that is great! Super stoked to see it in there finally.
>>
>> There were more bugs that came up in Android 4.0+. Looks like some of
>>the
>> File API objects exist "natively" in ICS's WebView. The "common"
>>platform
>> definition (under lib/platform/common.js) specifies most of the objects
>>we
>> need to exist in global scope for the Cordova API to work - but - the
>>way
>> we drop the common objects into global scope is we don't overwrite those
>> objects if they already exist in global scope. With ICS implementing
>>some
>> of them (like DirectoryEntry!) we need to either:
>>
>> A) test out the native implementations in ICS and see if they're
>> functional, or
>> B) add overrides in lib/platform/android.js for the objects affected.
>>The
>> platform-specific js definitions *always* clobber whatever exists so
>>it's
>> one way of just forcing out polyfills into the JS env (see 'device' and
>> how that is defined in android's platform .js file).
>>
>> On 12-02-17 3:38 PM, "Bryce Curtis" <cu...@gmail.com> wrote:
>>
>> >Android is running on common-js!
>> >
>> >Native side has been updated with merge from Fil.
>> >JS side was built from callback/callback-js and saved in assets/js.
>> >
>> >Now it's time to test and work through bugs.  (Including command line
>> >scripts)
>> >Running on Droid 2.2.3, I see 21 failed tests.
>> >
>> >Any word on when cordova-js repository on apache will be created?
>>Would
>> >be
>> >good to get it there asap.
>> >
>> >
>> >On Fri, Feb 17, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >> Thanks Bryce!
>> >>
>> >> On 12-02-17 11:59 AM, "Bryce Curtis" <cu...@gmail.com> wrote:
>> >>
>> >> >I'll take a look at it.
>> >> >
>> >> >On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
>> >> ><si...@gmail.com>wrote:
>> >> >
>> >> >> I'm off on vacation, in fact I'm already supposed to be gone,
>>until
>> >> >> Tuesday. On Tuesday I'll be giving a presentation at a local
>>collage.
>> >> >> Wednesday is meetings so I wouldn't be able to look at it until
>>next
>> >> >> Thursday.
>> >> >>
>> >> >> Simon Mac Donald
>> >> >> http://hi.im/simonmacdonald
>> >> >>
>> >> >>
>> >> >> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >>
>> >> >> > Hey all,
>> >> >> >
>> >> >> > Android is ready to integrate. Currently about 15 mobile spec
>>tests
>> >> >>are
>> >> >> > failing - better than the 23 or so that are failing with the
>> >>current
>> >> >> > android implementation :)
>> >> >> >
>> >> >> > Things we need to do:
>> >> >> >
>> >> >> > - merge in my "unified-js" branch of the android implmentation:
>> >> >> >
>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >> >> > - axe all javascript related stuff from the android repo: from
>> >>build
>> >> >> > scripts, .js files, etc.
>> >> >> > - use latest cordova-js, run a build, grab the android JS, and
>>add
>> >> >>that
>> >> >> to
>> >> >> > the android repo.
>> >> >> >
>> >> >> > Can someone from Android land (Simon, Joe) do the above steps,
>> >>please?
>> >> >> >
>> >> >> > Next I'm hopping on iOS as we are behind in getting that
>> >> >>implementation
>> >> >> up
>> >> >> > to speed with cordova-js. BlackBerry still needs t some help
>>too.
>> >> >> >
>> >> >> > Inching ever closer...
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> >>
>>
>>

Re: Work Items for 1.5.0 - unified JS

[Joe Bowser <bo...@gmail.com>]

Hey

I got this down to 26 failed tests on ICS after overriding FileError.
 There seems to be issues with the DirectoryReader as well, but at least
it's only 5 failures more than Gingerbread.  I pushed it up to the
repository.

Joe

On Fri, Feb 17, 2012 at 3:45 PM, Filip Maj <fi...@adobe.com> wrote:

> Awesome Bryce that is great! Super stoked to see it in there finally.
>
> There were more bugs that came up in Android 4.0+. Looks like some of the
> File API objects exist "natively" in ICS's WebView. The "common" platform
> definition (under lib/platform/common.js) specifies most of the objects we
> need to exist in global scope for the Cordova API to work - but - the way
> we drop the common objects into global scope is we don't overwrite those
> objects if they already exist in global scope. With ICS implementing some
> of them (like DirectoryEntry!) we need to either:
>
> A) test out the native implementations in ICS and see if they're
> functional, or
> B) add overrides in lib/platform/android.js for the objects affected. The
> platform-specific js definitions *always* clobber whatever exists so it's
> one way of just forcing out polyfills into the JS env (see 'device' and
> how that is defined in android's platform .js file).
>
> On 12-02-17 3:38 PM, "Bryce Curtis" <cu...@gmail.com> wrote:
>
> >Android is running on common-js!
> >
> >Native side has been updated with merge from Fil.
> >JS side was built from callback/callback-js and saved in assets/js.
> >
> >Now it's time to test and work through bugs.  (Including command line
> >scripts)
> >Running on Droid 2.2.3, I see 21 failed tests.
> >
> >Any word on when cordova-js repository on apache will be created?  Would
> >be
> >good to get it there asap.
> >
> >
> >On Fri, Feb 17, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Thanks Bryce!
> >>
> >> On 12-02-17 11:59 AM, "Bryce Curtis" <cu...@gmail.com> wrote:
> >>
> >> >I'll take a look at it.
> >> >
> >> >On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
> >> ><si...@gmail.com>wrote:
> >> >
> >> >> I'm off on vacation, in fact I'm already supposed to be gone, until
> >> >> Tuesday. On Tuesday I'll be giving a presentation at a local collage.
> >> >> Wednesday is meetings so I wouldn't be able to look at it until next
> >> >> Thursday.
> >> >>
> >> >> Simon Mac Donald
> >> >> http://hi.im/simonmacdonald
> >> >>
> >> >>
> >> >> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>
> >> >> > Hey all,
> >> >> >
> >> >> > Android is ready to integrate. Currently about 15 mobile spec tests
> >> >>are
> >> >> > failing - better than the 23 or so that are failing with the
> >>current
> >> >> > android implementation :)
> >> >> >
> >> >> > Things we need to do:
> >> >> >
> >> >> > - merge in my "unified-js" branch of the android implmentation:
> >> >> >
> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >> >> > - axe all javascript related stuff from the android repo: from
> >>build
> >> >> > scripts, .js files, etc.
> >> >> > - use latest cordova-js, run a build, grab the android JS, and add
> >> >>that
> >> >> to
> >> >> > the android repo.
> >> >> >
> >> >> > Can someone from Android land (Simon, Joe) do the above steps,
> >>please?
> >> >> >
> >> >> > Next I'm hopping on iOS as we are behind in getting that
> >> >>implementation
> >> >> up
> >> >> > to speed with cordova-js. BlackBerry still needs t some help too.
> >> >> >
> >> >> > Inching ever closer...
> >> >> >
> >> >> >
> >> >>
> >>
> >>
>
>

Re: Work Items for 1.5.0 - unified JS

[Joe Bowser <bo...@gmail.com>]

I'm currently looking at the ICS issues now.  I'll switch to the master
branch and pull the latest.

On Fri, Feb 17, 2012 at 3:45 PM, Filip Maj <fi...@adobe.com> wrote:

> Awesome Bryce that is great! Super stoked to see it in there finally.
>
> There were more bugs that came up in Android 4.0+. Looks like some of the
> File API objects exist "natively" in ICS's WebView. The "common" platform
> definition (under lib/platform/common.js) specifies most of the objects we
> need to exist in global scope for the Cordova API to work - but - the way
> we drop the common objects into global scope is we don't overwrite those
> objects if they already exist in global scope. With ICS implementing some
> of them (like DirectoryEntry!) we need to either:
>
> A) test out the native implementations in ICS and see if they're
> functional, or
> B) add overrides in lib/platform/android.js for the objects affected. The
> platform-specific js definitions *always* clobber whatever exists so it's
> one way of just forcing out polyfills into the JS env (see 'device' and
> how that is defined in android's platform .js file).
>
> On 12-02-17 3:38 PM, "Bryce Curtis" <cu...@gmail.com> wrote:
>
> >Android is running on common-js!
> >
> >Native side has been updated with merge from Fil.
> >JS side was built from callback/callback-js and saved in assets/js.
> >
> >Now it's time to test and work through bugs.  (Including command line
> >scripts)
> >Running on Droid 2.2.3, I see 21 failed tests.
> >
> >Any word on when cordova-js repository on apache will be created?  Would
> >be
> >good to get it there asap.
> >
> >
> >On Fri, Feb 17, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Thanks Bryce!
> >>
> >> On 12-02-17 11:59 AM, "Bryce Curtis" <cu...@gmail.com> wrote:
> >>
> >> >I'll take a look at it.
> >> >
> >> >On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
> >> ><si...@gmail.com>wrote:
> >> >
> >> >> I'm off on vacation, in fact I'm already supposed to be gone, until
> >> >> Tuesday. On Tuesday I'll be giving a presentation at a local collage.
> >> >> Wednesday is meetings so I wouldn't be able to look at it until next
> >> >> Thursday.
> >> >>
> >> >> Simon Mac Donald
> >> >> http://hi.im/simonmacdonald
> >> >>
> >> >>
> >> >> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>
> >> >> > Hey all,
> >> >> >
> >> >> > Android is ready to integrate. Currently about 15 mobile spec tests
> >> >>are
> >> >> > failing - better than the 23 or so that are failing with the
> >>current
> >> >> > android implementation :)
> >> >> >
> >> >> > Things we need to do:
> >> >> >
> >> >> > - merge in my "unified-js" branch of the android implmentation:
> >> >> >
> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >> >> > - axe all javascript related stuff from the android repo: from
> >>build
> >> >> > scripts, .js files, etc.
> >> >> > - use latest cordova-js, run a build, grab the android JS, and add
> >> >>that
> >> >> to
> >> >> > the android repo.
> >> >> >
> >> >> > Can someone from Android land (Simon, Joe) do the above steps,
> >>please?
> >> >> >
> >> >> > Next I'm hopping on iOS as we are behind in getting that
> >> >>implementation
> >> >> up
> >> >> > to speed with cordova-js. BlackBerry still needs t some help too.
> >> >> >
> >> >> > Inching ever closer...
> >> >> >
> >> >> >
> >> >>
> >>
> >>
>
>

Re: Work Items for 1.5.0 - unified JS

[Anis KADRI <an...@gmail.com>]

Hi Jukka,

I added my public key to svn but cannot ssh into git-wip-us.apache.org

How can I join the infrastructure and infrastructure-dev mailing lists
? I joined the #asfinfra IRC channel.

On Fri, Feb 17, 2012 at 4:59 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Sat, Feb 18, 2012 at 12:52 AM, Filip Maj <fi...@adobe.com> wrote:
>> I filed it early last week:
>> https://issues.apache.org/jira/browse/INFRA-4399
>
> Ah, thanks for the pointer! That unfortunately fell off my radar as I
> usually only keep closer track of issues in the "Git" component. I'll
> take care of the it in a moment.
>
>> And yes I am more than willing to help. Also, Steve (around here
>> somewhere) has volunteered as well. Command us, Jukka!
>
> Excellent! The first step (if you haven't already done so) is to join
> the infrastructure@ and infrastructure-dev@ mailing lists [1].
> Especially the first list can be a bit noisy at times, as it deals
> with the day-to-day issues of running all of the ASF infrastructure,
> so there's no need to pay close attention to everything. But it's good
> to keep at least an occasional eye on what's going on there. And for
> more background on working with ASF infra, see [2].
>
> As a more practical thing to get you accounts on the git-wip-us
> server, you'll need to add your public ssh keys to the svn folder at
> [3]. As Apache committers you should have read and commit access to
> that folder. You should also check out the sources at [4] for hints on
> how the server is set up.
>
> [1] http://www.apache.org/dev/infra-mail.html
> [2] http://www.apache.org/dev/infra-volunteer.html
> [3] https://svn.apache.org/repos/infra/infrastructure/trunk/ssh_keys/people/
> [4] https://git-wip-us.apache.org/repos/infra/asfgit-admin.git
>
> BR,
>
> Jukka Zitting

Re: Work Items for 1.5.0 - unified JS

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Sat, Feb 18, 2012 at 12:52 AM, Filip Maj <fi...@adobe.com> wrote:
> I filed it early last week:
> https://issues.apache.org/jira/browse/INFRA-4399

Ah, thanks for the pointer! That unfortunately fell off my radar as I
usually only keep closer track of issues in the "Git" component. I'll
take care of the it in a moment.

> And yes I am more than willing to help. Also, Steve (around here
> somewhere) has volunteered as well. Command us, Jukka!

Excellent! The first step (if you haven't already done so) is to join
the infrastructure@ and infrastructure-dev@ mailing lists [1].
Especially the first list can be a bit noisy at times, as it deals
with the day-to-day issues of running all of the ASF infrastructure,
so there's no need to pay close attention to everything. But it's good
to keep at least an occasional eye on what's going on there. And for
more background on working with ASF infra, see [2].

As a more practical thing to get you accounts on the git-wip-us
server, you'll need to add your public ssh keys to the svn folder at
[3]. As Apache committers you should have read and commit access to
that folder. You should also check out the sources at [4] for hints on
how the server is set up.

[1] http://www.apache.org/dev/infra-mail.html
[2] http://www.apache.org/dev/infra-volunteer.html
[3] https://svn.apache.org/repos/infra/infrastructure/trunk/ssh_keys/people/
[4] https://git-wip-us.apache.org/repos/infra/asfgit-admin.git

BR,

Jukka Zitting

Re: Work Items for 1.5.0 - unified JS

[Anis KADRI <an...@gmail.com>]

Hi Jukka,

I'd love to help out with that !

Anis

On Fri, Feb 17, 2012 at 3:49 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Sat, Feb 18, 2012 at 12:38 AM, Bryce Curtis <cu...@gmail.com> wrote:
>> Any word on when cordova-js repository on apache will be created?  Would be
>> good to get it there asap.
>
> Can you file an INFRA ticket for that?
>
> PS. Did one/some of you want to participate in administering
> git-wip-us? I can help get you started so that you can take care of
> things like this (setting up new repos, etc.) without having to wait
> until I or someone else from the ASF infra team has time.
>
> BR,
>
> Jukka Zitting

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

I filed it early last week:
https://issues.apache.org/jira/browse/INFRA-4399

And yes I am more than willing to help. Also, Steve (around here
somewhere) has volunteered as well. Command us, Jukka!

On 12-02-17 3:49 PM, "Jukka Zitting" <ju...@gmail.com> wrote:

>Hi,
>
>On Sat, Feb 18, 2012 at 12:38 AM, Bryce Curtis <cu...@gmail.com>
>wrote:
>> Any word on when cordova-js repository on apache will be created?
>>Would be
>> good to get it there asap.
>
>Can you file an INFRA ticket for that?
>
>PS. Did one/some of you want to participate in administering
>git-wip-us? I can help get you started so that you can take care of
>things like this (setting up new repos, etc.) without having to wait
>until I or someone else from the ASF infra team has time.
>
>BR,
>
>Jukka Zitting

Re: Work Items for 1.5.0 - unified JS

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Sat, Feb 18, 2012 at 12:38 AM, Bryce Curtis <cu...@gmail.com> wrote:
> Any word on when cordova-js repository on apache will be created?  Would be
> good to get it there asap.

Can you file an INFRA ticket for that?

PS. Did one/some of you want to participate in administering
git-wip-us? I can help get you started so that you can take care of
things like this (setting up new repos, etc.) without having to wait
until I or someone else from the ASF infra team has time.

BR,

Jukka Zitting

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Awesome Bryce that is great! Super stoked to see it in there finally.

There were more bugs that came up in Android 4.0+. Looks like some of the
File API objects exist "natively" in ICS's WebView. The "common" platform
definition (under lib/platform/common.js) specifies most of the objects we
need to exist in global scope for the Cordova API to work - but - the way
we drop the common objects into global scope is we don't overwrite those
objects if they already exist in global scope. With ICS implementing some
of them (like DirectoryEntry!) we need to either:

A) test out the native implementations in ICS and see if they're
functional, or
B) add overrides in lib/platform/android.js for the objects affected. The
platform-specific js definitions *always* clobber whatever exists so it's
one way of just forcing out polyfills into the JS env (see 'device' and
how that is defined in android's platform .js file).

On 12-02-17 3:38 PM, "Bryce Curtis" <cu...@gmail.com> wrote:

>Android is running on common-js!
>
>Native side has been updated with merge from Fil.
>JS side was built from callback/callback-js and saved in assets/js.
>
>Now it's time to test and work through bugs.  (Including command line
>scripts)
>Running on Droid 2.2.3, I see 21 failed tests.
>
>Any word on when cordova-js repository on apache will be created?  Would
>be
>good to get it there asap.
>
>
>On Fri, Feb 17, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Thanks Bryce!
>>
>> On 12-02-17 11:59 AM, "Bryce Curtis" <cu...@gmail.com> wrote:
>>
>> >I'll take a look at it.
>> >
>> >On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
>> ><si...@gmail.com>wrote:
>> >
>> >> I'm off on vacation, in fact I'm already supposed to be gone, until
>> >> Tuesday. On Tuesday I'll be giving a presentation at a local collage.
>> >> Wednesday is meetings so I wouldn't be able to look at it until next
>> >> Thursday.
>> >>
>> >> Simon Mac Donald
>> >> http://hi.im/simonmacdonald
>> >>
>> >>
>> >> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >> > Hey all,
>> >> >
>> >> > Android is ready to integrate. Currently about 15 mobile spec tests
>> >>are
>> >> > failing - better than the 23 or so that are failing with the
>>current
>> >> > android implementation :)
>> >> >
>> >> > Things we need to do:
>> >> >
>> >> > - merge in my "unified-js" branch of the android implmentation:
>> >> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >> > - axe all javascript related stuff from the android repo: from
>>build
>> >> > scripts, .js files, etc.
>> >> > - use latest cordova-js, run a build, grab the android JS, and add
>> >>that
>> >> to
>> >> > the android repo.
>> >> >
>> >> > Can someone from Android land (Simon, Joe) do the above steps,
>>please?
>> >> >
>> >> > Next I'm hopping on iOS as we are behind in getting that
>> >>implementation
>> >> up
>> >> > to speed with cordova-js. BlackBerry still needs t some help too.
>> >> >
>> >> > Inching ever closer...
>> >> >
>> >> >
>> >>
>>
>>

Re: Work Items for 1.5.0 - unified JS

[Bryce Curtis <cu...@gmail.com>]

Android is running on common-js!

Native side has been updated with merge from Fil.
JS side was built from callback/callback-js and saved in assets/js.

Now it's time to test and work through bugs.  (Including command line
scripts)
Running on Droid 2.2.3, I see 21 failed tests.

Any word on when cordova-js repository on apache will be created?  Would be
good to get it there asap.


On Fri, Feb 17, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:

> Thanks Bryce!
>
> On 12-02-17 11:59 AM, "Bryce Curtis" <cu...@gmail.com> wrote:
>
> >I'll take a look at it.
> >
> >On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
> ><si...@gmail.com>wrote:
> >
> >> I'm off on vacation, in fact I'm already supposed to be gone, until
> >> Tuesday. On Tuesday I'll be giving a presentation at a local collage.
> >> Wednesday is meetings so I wouldn't be able to look at it until next
> >> Thursday.
> >>
> >> Simon Mac Donald
> >> http://hi.im/simonmacdonald
> >>
> >>
> >> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
> >>
> >> > Hey all,
> >> >
> >> > Android is ready to integrate. Currently about 15 mobile spec tests
> >>are
> >> > failing - better than the 23 or so that are failing with the current
> >> > android implementation :)
> >> >
> >> > Things we need to do:
> >> >
> >> > - merge in my "unified-js" branch of the android implmentation:
> >> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >> > - axe all javascript related stuff from the android repo: from build
> >> > scripts, .js files, etc.
> >> > - use latest cordova-js, run a build, grab the android JS, and add
> >>that
> >> to
> >> > the android repo.
> >> >
> >> > Can someone from Android land (Simon, Joe) do the above steps, please?
> >> >
> >> > Next I'm hopping on iOS as we are behind in getting that
> >>implementation
> >> up
> >> > to speed with cordova-js. BlackBerry still needs t some help too.
> >> >
> >> > Inching ever closer...
> >> >
> >> >
> >>
>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Thanks Bryce!

On 12-02-17 11:59 AM, "Bryce Curtis" <cu...@gmail.com> wrote:

>I'll take a look at it.
>
>On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
><si...@gmail.com>wrote:
>
>> I'm off on vacation, in fact I'm already supposed to be gone, until
>> Tuesday. On Tuesday I'll be giving a presentation at a local collage.
>> Wednesday is meetings so I wouldn't be able to look at it until next
>> Thursday.
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>> > Hey all,
>> >
>> > Android is ready to integrate. Currently about 15 mobile spec tests
>>are
>> > failing - better than the 23 or so that are failing with the current
>> > android implementation :)
>> >
>> > Things we need to do:
>> >
>> > - merge in my "unified-js" branch of the android implmentation:
>> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> > - axe all javascript related stuff from the android repo: from build
>> > scripts, .js files, etc.
>> > - use latest cordova-js, run a build, grab the android JS, and add
>>that
>> to
>> > the android repo.
>> >
>> > Can someone from Android land (Simon, Joe) do the above steps, please?
>> >
>> > Next I'm hopping on iOS as we are behind in getting that
>>implementation
>> up
>> > to speed with cordova-js. BlackBerry still needs t some help too.
>> >
>> > Inching ever closer...
>> >
>> >
>>

Re: Work Items for 1.5.0 - unified JS

[Bryce Curtis <cu...@gmail.com>]

I'll take a look at it.

On Fri, Feb 17, 2012 at 1:55 PM, Simon MacDonald
<si...@gmail.com>wrote:

> I'm off on vacation, in fact I'm already supposed to be gone, until
> Tuesday. On Tuesday I'll be giving a presentation at a local collage.
> Wednesday is meetings so I wouldn't be able to look at it until next
> Thursday.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
> On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
>
> > Hey all,
> >
> > Android is ready to integrate. Currently about 15 mobile spec tests are
> > failing - better than the 23 or so that are failing with the current
> > android implementation :)
> >
> > Things we need to do:
> >
> > - merge in my "unified-js" branch of the android implmentation:
> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> > - axe all javascript related stuff from the android repo: from build
> > scripts, .js files, etc.
> > - use latest cordova-js, run a build, grab the android JS, and add that
> to
> > the android repo.
> >
> > Can someone from Android land (Simon, Joe) do the above steps, please?
> >
> > Next I'm hopping on iOS as we are behind in getting that implementation
> up
> > to speed with cordova-js. BlackBerry still needs t some help too.
> >
> > Inching ever closer...
> >
> >
>

Re: Work Items for 1.5.0 - unified JS

[Simon MacDonald <si...@gmail.com>]

I'm off on vacation, in fact I'm already supposed to be gone, until
Tuesday. On Tuesday I'll be giving a presentation at a local collage.
Wednesday is meetings so I wouldn't be able to look at it until next
Thursday.

Simon Mac Donald
http://hi.im/simonmacdonald


On Fri, Feb 17, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:

> Hey all,
>
> Android is ready to integrate. Currently about 15 mobile spec tests are
> failing - better than the 23 or so that are failing with the current
> android implementation :)
>
> Things we need to do:
>
> - merge in my "unified-js" branch of the android implmentation:
> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> - axe all javascript related stuff from the android repo: from build
> scripts, .js files, etc.
> - use latest cordova-js, run a build, grab the android JS, and add that to
> the android repo.
>
> Can someone from Android land (Simon, Joe) do the above steps, please?
>
> Next I'm hopping on iOS as we are behind in getting that implementation up
> to speed with cordova-js. BlackBerry still needs t some help too.
>
> Inching ever closer...
>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Hey all,

Android is ready to integrate. Currently about 15 mobile spec tests are
failing - better than the 23 or so that are failing with the current
android implementation :)

Things we need to do:

- merge in my "unified-js" branch of the android implmentation:
https://github.com/filmaj/incubator-cordova-android/tree/unified-js
- axe all javascript related stuff from the android repo: from build
scripts, .js files, etc.
- use latest cordova-js, run a build, grab the android JS, and add that to
the android repo.

Can someone from Android land (Simon, Joe) do the above steps, please?

Next I'm hopping on iOS as we are behind in getting that implementation up
to speed with cordova-js. BlackBerry still needs t some help too.

Inching ever closer...

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Looks good, I'v emerged it in :)

On 12-02-16 9:18 AM, "Drew Walters" <de...@gmail.com> wrote:

>Yes it does run but that error is pretty ugly and its not immediately
>obvious that it built successfully.
>
>I've submitted a pull request to add in button overriding and some app
>life cycle behavior for BlackBerry.  The life cycle is still not what
>it use to be so there is still more work to be done there.  I also
>fixed a bug in the builder code that wasn't properly handling clobber
>when the parent object doesn't define a path (ie. navigator.app was
>not getting injected under navigator).
>
>https://github.com/callback/callback-js/pull/21
>
>FYI, I'm out on vacation this afternoon and won't be back till Tuesday
>but wanted to get this code up there.
>
>On Wed, Feb 15, 2012 at 2:58 PM, Gord Tanner <go...@tinyhippos.com> wrote:
>> You should still be able to run jake and it will build (and have an
>>error
>> about no jsDom).
>>
>> Got rid of a bunch of unused modules (anyone know why jQuery was in
>>there?)
>> and thirdparty code.
>>
>> 
>>https://github.com/callback/callback-js/commit/bb6cd42e1b5a56c2cd9642e8ac
>>e386ffcc0b4ce3
>>
>>
>> On Wed, Feb 15, 2012 at 2:35 PM, Drew Walters <de...@gmail.com>
>>wrote:
>>
>>> Gord,
>>>
>>> Looks like jsDom adds a requirement for the system to have a compiler.
>>>  Since I don't (and maybe others) have XCode installed on my Mac for
>>> legal reasons, the configure script fails for me now.
>>>
>>> On Wed, Feb 15, 2012 at 12:41 PM, Filip Maj <fi...@adobe.com> wrote:
>>> > Awwwww yeauuhhh
>>> >
>>> > Thanks Gord :D
>>> >
>>> > On 12-02-15 10:31 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:
>>> >
>>> >>Quick note:
>>> >>
>>> >>I added a node runner for our unit tests that will run for every
>>>build:
>>> >>
>>> >>
>>> 
>>>https://github.com/callback/callback-js/blob/master/test/runner.js#L23-5
>>>8
>>> >>
>>> >>If you have already been developing cordova.js you will need to run
>>> >>./configure again to pull down jsDom to build.
>>> >>
>>> >>The intent is that these tests will test the javascript code (mocking
>>> >>interactions to native) and should be kept green.
>>> >>
>>> >>This is not a replacement for cordova-test but a place for us to
>>>quickly
>>> >>spec and test our javascript without the need to load or build into a
>>> >>simulator.
>>> >>
>>> >>to run the tests in node:
>>> >>
>>> >>jake
>>> >>or
>>> >>jake test
>>> >>
>>> >>to run the tests in the browser:
>>> >>jake btest
>>> >>
>>> >>Gord
>>> >>
>>> >>On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:
>>> >>
>>> >>> Ahh, so more of a packaging question. I'm not sure. I know Steve is
>>> >>> working on a packaging script so certainly integrating a cordova-js
>>> >>>build
>>> >>> into that makes sense.
>>> >>>
>>> >>> I think you're on the right track, Drew. We used to include
>>>phonegap.js
>>> >>> into the sample app packaged in each repo - maybe we can keep with
>>>that
>>> >>> same theme for cordova-js and just add some stuff into the README
>>> >>> regarding where to get/build the latest cordova-js.
>>> >>>
>>> >>> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
>>> >>>
>>> >>> >I think the way I stated my question is confusing.  Let me try
>>>again.
>>> >>> >Right now the incubator-cordova-blackberry-webworks repo contains
>>>both
>>> >>> >the JS and native code.  Some time soon I would anticipate a
>>> >>> >incubator-cordova-js repo.  At that time the JS files in the
>>>webworks
>>> >>> >repo should go away.
>>> >>> >
>>> >>> >It seems to me that the "vendor" in of a platform specific
>>>cordova.js
>>> >>> >should happen when we build the end user package (ie. the one
>>> >>> >currently at phonegap.com).  At development time, I'm always
>>>going to
>>> >>> >want the latest one out of incubator-cordova-js so I can just
>>>build
>>> >>> >that myself.  Unless of course there is some mechanism to
>>> >>> >automatically build incubator-cordova-js when it is updated and
>>>copy
>>> >>> >the built files to the platform repos.
>>> >>> >
>>> >>> >Am I wrong?
>>> >>> >
>>> >>> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
>>> >>> >> I think it'd be a pain to submodule cordova-js into the platform
>>> >>>repos.
>>> >>> >>
>>> >>> >> So far the general agreement is to "vendor" cordova-js in as a
>>>built
>>> >>> >> script.
>>> >>> >>
>>> >>> >> It should only get out of sync if we let it :)
>>> >>> >>
>>> >>> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>>> >>> >>
>>> >>> >>>I need to do some more testing before I agree to move it to the
>>> >>>apache
>>> >>> >>>code.  Wanted to get the name change in completely first.
>>>Right now
>>> >>> >>>some of the api aren't working in my test app.
>>> >>> >>>
>>> >>> >>>This brings up a point though.  What will this look like once
>>>its
>>> >>> >>>moved to apache.  I would assume we'll have a separate repo for
>>> >>> >>>cordova-js, but do the individual platforms really need a copy
>>>of
>>> the
>>> >>> >>>built js file?  From an end user perspective this could just be
>>> >>> >>>handled at packaging time when we build the distributable
>>>binary.
>>> >>> >>>Seems like including a built js from cordova-js would lead to it
>>> >>> >>>getting out of sync.
>>> >>> >>>
>>> >>> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner
>>><go...@tinyhippos.com>
>>> >>> >>>wrote:
>>> >>> >>>> OMFG!
>>> >>> >>>>
>>> >>> >>>> You just saved my day!
>>> >>> >>>>
>>> >>> >>>> I have been looking for why blackberry wasn't firing device
>>>ready
>>> >>>and
>>> >>> >>>>that
>>> >>> >>>> bad module ID was it!  I was circling around the channel code
>>> >>> >>>>attempting to
>>> >>> >>>> figure out why it wasn't joining after the device and network
>>> >>>channels
>>> >>> >>>>were
>>> >>> >>>> fired.
>>> >>> >>>>
>>> >>> >>>> Gonna look into this and pull it in, looks good at first
>>>glance.
>>> >>> >>>>
>>> >>> >>>>
>>> >>> >>>> Gord
>>> >>> >>>>
>>> >>> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <
>>> deedubbu@gmail.com>
>>> >>> >>>>wrote:
>>> >>> >>>>
>>> >>> >>>>> Ok, I've submitted a pull request with my changes.
>>> >>> >>>>>
>>> >>> >>>>> https://github.com/callback/callback-js/pull/17
>>> >>> >>>>>
>>> >>> >>>>> In my previous email, #3 was due to where I had inserted #2
>>> >>>(oops).
>>> >>> >>>>> The changes are mostly phonegap -> cordova changes.
>>>Additionally
>>> >>>I
>>> >>> >>>>> had to fix a module require in lib/platform/blackberry.js
>>>which
>>> >>>was
>>> >>> >>>>> specifying a bad module name.
>>> >>> >>>>>
>>> >>> >>>>> The only appearance of phonegap in common-js after my change
>>>is
>>> in
>>> >>> >>>>>the
>>> >>> >>>>> iOS and WP7 plugins where they reference native code since I
>>> >>>didn't
>>> >>> >>>>> think those had been renamed yet.
>>> >>> >>>>>
>>> >>> >>>>> Eventually the BlackBerry native side should make use of
>>>require
>>> >>>(as
>>> >>> >>>>> shown in Fil's commit), but that will wait till common-js
>>>gets
>>> >>>added
>>> >>> >>>>> to apache source. For the time being a quick hack is to add
>>>the
>>> >>> >>>>> following at the bottom of the generated js:
>>> >>> >>>>>
>>> >>> >>>>> var Cordova = require('cordova');
>>> >>> >>>>>
>>> >>> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <
>>> deedubbu@gmail.com>
>>> >>> >>>>>wrote:
>>> >>> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't
>>> >>>submitted
>>> >>> >>>>> > pull request yet because I'm still debugging something.
>>>Here's
>>> >>> >>>>> > summary of changes I've made:
>>> >>> >>>>> >
>>> >>> >>>>> > 1. Modify rest of files to use "cordova" instead of
>>>"phonegap".
>>> >>> >>>>> > 2. Added a global define of "Cordova" as a temporary hack
>>>since
>>> >>> >>>>>native
>>> >>> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>>> >>> >>>>> > 3. For some reason I had to make sure the cordova/utils
>>>module
>>> >>> >>>>>exists
>>> >>> >>>>> > in cordova.js before the cordova/channel module, otherwise
>>>I
>>> was
>>> >>> >>>>> > getting an error that the module didn't exist.
>>> >>> >>>>> >
>>> >>> >>>>> > With the above changes I was able to run some simple tests
>>> >>> >>>>>(verified
>>> >>> >>>>> > network works).  I'm currently looking at proper fix for
>>>#2 and
>>> >>>#3.
>>> >>> >>>>> >
>>> >>> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters
>>> >>><de...@gmail.com>
>>> >>> >>>>> wrote:
>>> >>> >>>>> >> I'm looking at https://github.com/callback/callback-js
>>>and I
>>> >>>see
>>> >>> a
>>> >>> >>>>>lot
>>> >>> >>>>> >> of references to "phonegap" in the lib/plugins directory
>>> >>>though it
>>> >>> >>>>> >> seems like things one directory up (lib) has been
>>>changed.  Am
>>> >>>I
>>> >>> >>>>>not
>>> >>> >>>>> >> looking at an up to date project or should I send a pull
>>> >>>request
>>> >>> >>>>>with
>>> >>> >>>>> >> that name change too?
>>> >>> >>>>> >>
>>> >>> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner
>>> >>><gord@tinyhippos.com
>>> >>> >
>>> >>> >>>>> wrote:
>>> >>> >>>>> >>> I am on BlackBerry today.
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> Currently showing:
>>> >>> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> I will attempt to get it up and running again today.
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> I also have the start of a node runner for callback-js
>>>tests
>>> >>> >>>>>here:
>>> >>> >>>>> >>> https://github.com/gtanner/callback-js
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> Gord
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>>> >>> >>>>><vi...@users.sourceforge.net>
>>> >>> >>>>> wrote:
>>> >>> >>>>> >>>
>>> >>> >>>>> >>>> Can you please drop me a line once cordova-js is on the
>>> >>>official
>>> >>> >>>>> repos &
>>> >>> >>>>> >>>> mirrored? I will then give integrating the new common-JS
>>> into
>>> >>> >>>>> cordova-qt a
>>> >>> >>>>> >>>> go!
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
>>> >>> >>>>> >>>>>
>>> >>> >>>>> >>>>> - looks like the WP7 implementation cannot run our
>>> >>>mobile-spec,
>>> >>> >>>>> which is a
>>> >>> >>>>> >>>>> hurdle in making sure it supports the cross-platform
>>> cordova
>>> >>> >>>>>API.
>>> >>> >>>>> Before
>>> >>> >>>>> >>>>> we can move forward with cordova-js integration we
>>>really
>>> >>>need
>>> >>> >>>>>to
>>> >>> >>>>> figure
>>> >>> >>>>> >>>>> that part of it out.
>>> >>> >>>>> >>>>> - I will work rest of day in getting cordova-js into
>>>the
>>> >>>apache
>>> >>> >>>>>git
>>> >>> >>>>> repo
>>> >>> >>>>> >>>>> and finishing up that work.
>>> >>> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you
>>> >>>available?
>>> >>> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for
>>>tomorrow
>>> >>> >>>>>morning to
>>> >>> >>>>> get
>>> >>> >>>>> >>>>> iOS on track. Will have a better idea how that
>>>platform is
>>> >>> >>>>>looking
>>> >>> >>>>> >>>>> tomorrow.
>>> >>> >>>>> >>>>> - Bada 2.0 still needs a platform implementation
>>>before we
>>> >>>can
>>> >>> >>>>>move
>>> >>> >>>>> with
>>> >>> >>>>> >>>>> cordova-js on it.
>>> >>> >>>>> >>>>>
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>> --
>>> >>> >>>>> >>>> GOFG - Get On Fat Guy
>>> >>> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
>>> >>> >>>>> >>>>
>>> >>> >>>>> >>>
>>> >>> >>>>> >>>
>>> >>> >>>>> >>>
>>> >>> >>>>> >>> --
>>> >>> >>>>> >>> Gord Tanner
>>> >>> >>>>> >>> Senior Developer / Code Poet
>>> >>> >>>>> >>> tinyHippos Inc.
>>> >>> >>>>> >>> @tinyhippos
>>> >>> >>>>>
>>> >>> >>>>
>>> >>> >>>>
>>> >>> >>>>
>>> >>> >>>> --
>>> >>> >>>> Gord Tanner
>>> >>> >>>> Senior Developer / Code Poet
>>> >>> >>>> tinyHippos Inc.
>>> >>> >>>> @tinyhippos
>>> >>> >>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >>--
>>> >>Gord Tanner
>>> >>Senior Developer / Code Poet
>>> >>tinyHippos Inc.
>>> >>@tinyhippos
>>> >
>>>
>>
>>
>>
>> --
>> Gord Tanner
>> Senior Developer / Code Poet
>> tinyHippos Inc.
>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

Yes it does run but that error is pretty ugly and its not immediately
obvious that it built successfully.

I've submitted a pull request to add in button overriding and some app
life cycle behavior for BlackBerry.  The life cycle is still not what
it use to be so there is still more work to be done there.  I also
fixed a bug in the builder code that wasn't properly handling clobber
when the parent object doesn't define a path (ie. navigator.app was
not getting injected under navigator).

https://github.com/callback/callback-js/pull/21

FYI, I'm out on vacation this afternoon and won't be back till Tuesday
but wanted to get this code up there.

On Wed, Feb 15, 2012 at 2:58 PM, Gord Tanner <go...@tinyhippos.com> wrote:
> You should still be able to run jake and it will build (and have an error
> about no jsDom).
>
> Got rid of a bunch of unused modules (anyone know why jQuery was in there?)
> and thirdparty code.
>
> https://github.com/callback/callback-js/commit/bb6cd42e1b5a56c2cd9642e8ace386ffcc0b4ce3
>
>
> On Wed, Feb 15, 2012 at 2:35 PM, Drew Walters <de...@gmail.com> wrote:
>
>> Gord,
>>
>> Looks like jsDom adds a requirement for the system to have a compiler.
>>  Since I don't (and maybe others) have XCode installed on my Mac for
>> legal reasons, the configure script fails for me now.
>>
>> On Wed, Feb 15, 2012 at 12:41 PM, Filip Maj <fi...@adobe.com> wrote:
>> > Awwwww yeauuhhh
>> >
>> > Thanks Gord :D
>> >
>> > On 12-02-15 10:31 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:
>> >
>> >>Quick note:
>> >>
>> >>I added a node runner for our unit tests that will run for every build:
>> >>
>> >>
>> https://github.com/callback/callback-js/blob/master/test/runner.js#L23-58
>> >>
>> >>If you have already been developing cordova.js you will need to run
>> >>./configure again to pull down jsDom to build.
>> >>
>> >>The intent is that these tests will test the javascript code (mocking
>> >>interactions to native) and should be kept green.
>> >>
>> >>This is not a replacement for cordova-test but a place for us to quickly
>> >>spec and test our javascript without the need to load or build into a
>> >>simulator.
>> >>
>> >>to run the tests in node:
>> >>
>> >>jake
>> >>or
>> >>jake test
>> >>
>> >>to run the tests in the browser:
>> >>jake btest
>> >>
>> >>Gord
>> >>
>> >>On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >>> Ahh, so more of a packaging question. I'm not sure. I know Steve is
>> >>> working on a packaging script so certainly integrating a cordova-js
>> >>>build
>> >>> into that makes sense.
>> >>>
>> >>> I think you're on the right track, Drew. We used to include phonegap.js
>> >>> into the sample app packaged in each repo - maybe we can keep with that
>> >>> same theme for cordova-js and just add some stuff into the README
>> >>> regarding where to get/build the latest cordova-js.
>> >>>
>> >>> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
>> >>>
>> >>> >I think the way I stated my question is confusing.  Let me try again.
>> >>> >Right now the incubator-cordova-blackberry-webworks repo contains both
>> >>> >the JS and native code.  Some time soon I would anticipate a
>> >>> >incubator-cordova-js repo.  At that time the JS files in the webworks
>> >>> >repo should go away.
>> >>> >
>> >>> >It seems to me that the "vendor" in of a platform specific cordova.js
>> >>> >should happen when we build the end user package (ie. the one
>> >>> >currently at phonegap.com).  At development time, I'm always going to
>> >>> >want the latest one out of incubator-cordova-js so I can just build
>> >>> >that myself.  Unless of course there is some mechanism to
>> >>> >automatically build incubator-cordova-js when it is updated and copy
>> >>> >the built files to the platform repos.
>> >>> >
>> >>> >Am I wrong?
>> >>> >
>> >>> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
>> >>> >> I think it'd be a pain to submodule cordova-js into the platform
>> >>>repos.
>> >>> >>
>> >>> >> So far the general agreement is to "vendor" cordova-js in as a built
>> >>> >> script.
>> >>> >>
>> >>> >> It should only get out of sync if we let it :)
>> >>> >>
>> >>> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>> >>> >>
>> >>> >>>I need to do some more testing before I agree to move it to the
>> >>>apache
>> >>> >>>code.  Wanted to get the name change in completely first.  Right now
>> >>> >>>some of the api aren't working in my test app.
>> >>> >>>
>> >>> >>>This brings up a point though.  What will this look like once its
>> >>> >>>moved to apache.  I would assume we'll have a separate repo for
>> >>> >>>cordova-js, but do the individual platforms really need a copy of
>> the
>> >>> >>>built js file?  From an end user perspective this could just be
>> >>> >>>handled at packaging time when we build the distributable binary.
>> >>> >>>Seems like including a built js from cordova-js would lead to it
>> >>> >>>getting out of sync.
>> >>> >>>
>> >>> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
>> >>> >>>wrote:
>> >>> >>>> OMFG!
>> >>> >>>>
>> >>> >>>> You just saved my day!
>> >>> >>>>
>> >>> >>>> I have been looking for why blackberry wasn't firing device ready
>> >>>and
>> >>> >>>>that
>> >>> >>>> bad module ID was it!  I was circling around the channel code
>> >>> >>>>attempting to
>> >>> >>>> figure out why it wasn't joining after the device and network
>> >>>channels
>> >>> >>>>were
>> >>> >>>> fired.
>> >>> >>>>
>> >>> >>>> Gonna look into this and pull it in, looks good at first glance.
>> >>> >>>>
>> >>> >>>>
>> >>> >>>> Gord
>> >>> >>>>
>> >>> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <
>> deedubbu@gmail.com>
>> >>> >>>>wrote:
>> >>> >>>>
>> >>> >>>>> Ok, I've submitted a pull request with my changes.
>> >>> >>>>>
>> >>> >>>>> https://github.com/callback/callback-js/pull/17
>> >>> >>>>>
>> >>> >>>>> In my previous email, #3 was due to where I had inserted #2
>> >>>(oops).
>> >>> >>>>> The changes are mostly phonegap -> cordova changes.  Additionally
>> >>>I
>> >>> >>>>> had to fix a module require in lib/platform/blackberry.js which
>> >>>was
>> >>> >>>>> specifying a bad module name.
>> >>> >>>>>
>> >>> >>>>> The only appearance of phonegap in common-js after my change is
>> in
>> >>> >>>>>the
>> >>> >>>>> iOS and WP7 plugins where they reference native code since I
>> >>>didn't
>> >>> >>>>> think those had been renamed yet.
>> >>> >>>>>
>> >>> >>>>> Eventually the BlackBerry native side should make use of require
>> >>>(as
>> >>> >>>>> shown in Fil's commit), but that will wait till common-js gets
>> >>>added
>> >>> >>>>> to apache source. For the time being a quick hack is to add the
>> >>> >>>>> following at the bottom of the generated js:
>> >>> >>>>>
>> >>> >>>>> var Cordova = require('cordova');
>> >>> >>>>>
>> >>> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <
>> deedubbu@gmail.com>
>> >>> >>>>>wrote:
>> >>> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't
>> >>>submitted
>> >>> >>>>> > pull request yet because I'm still debugging something.  Here's
>> >>> >>>>> > summary of changes I've made:
>> >>> >>>>> >
>> >>> >>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>> >>> >>>>> > 2. Added a global define of "Cordova" as a temporary hack since
>> >>> >>>>>native
>> >>> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>> >>> >>>>> > 3. For some reason I had to make sure the cordova/utils module
>> >>> >>>>>exists
>> >>> >>>>> > in cordova.js before the cordova/channel module, otherwise I
>> was
>> >>> >>>>> > getting an error that the module didn't exist.
>> >>> >>>>> >
>> >>> >>>>> > With the above changes I was able to run some simple tests
>> >>> >>>>>(verified
>> >>> >>>>> > network works).  I'm currently looking at proper fix for #2 and
>> >>>#3.
>> >>> >>>>> >
>> >>> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters
>> >>><de...@gmail.com>
>> >>> >>>>> wrote:
>> >>> >>>>> >> I'm looking at https://github.com/callback/callback-js and I
>> >>>see
>> >>> a
>> >>> >>>>>lot
>> >>> >>>>> >> of references to "phonegap" in the lib/plugins directory
>> >>>though it
>> >>> >>>>> >> seems like things one directory up (lib) has been changed.  Am
>> >>>I
>> >>> >>>>>not
>> >>> >>>>> >> looking at an up to date project or should I send a pull
>> >>>request
>> >>> >>>>>with
>> >>> >>>>> >> that name change too?
>> >>> >>>>> >>
>> >>> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner
>> >>><gord@tinyhippos.com
>> >>> >
>> >>> >>>>> wrote:
>> >>> >>>>> >>> I am on BlackBerry today.
>> >>> >>>>> >>>
>> >>> >>>>> >>> Currently showing:
>> >>> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>> >>> >>>>> >>>
>> >>> >>>>> >>> I will attempt to get it up and running again today.
>> >>> >>>>> >>>
>> >>> >>>>> >>> I also have the start of a node runner for callback-js tests
>> >>> >>>>>here:
>> >>> >>>>> >>> https://github.com/gtanner/callback-js
>> >>> >>>>> >>>
>> >>> >>>>> >>> Gord
>> >>> >>>>> >>>
>> >>> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>> >>> >>>>><vi...@users.sourceforge.net>
>> >>> >>>>> wrote:
>> >>> >>>>> >>>
>> >>> >>>>> >>>> Can you please drop me a line once cordova-js is on the
>> >>>official
>> >>> >>>>> repos &
>> >>> >>>>> >>>> mirrored? I will then give integrating the new common-JS
>> into
>> >>> >>>>> cordova-qt a
>> >>> >>>>> >>>> go!
>> >>> >>>>> >>>>
>> >>> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>> >>> >>>>> >>>>
>> >>> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
>> >>> >>>>> >>>>>
>> >>> >>>>> >>>>> - looks like the WP7 implementation cannot run our
>> >>>mobile-spec,
>> >>> >>>>> which is a
>> >>> >>>>> >>>>> hurdle in making sure it supports the cross-platform
>> cordova
>> >>> >>>>>API.
>> >>> >>>>> Before
>> >>> >>>>> >>>>> we can move forward with cordova-js integration we really
>> >>>need
>> >>> >>>>>to
>> >>> >>>>> figure
>> >>> >>>>> >>>>> that part of it out.
>> >>> >>>>> >>>>> - I will work rest of day in getting cordova-js into the
>> >>>apache
>> >>> >>>>>git
>> >>> >>>>> repo
>> >>> >>>>> >>>>> and finishing up that work.
>> >>> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you
>> >>>available?
>> >>> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
>> >>> >>>>>morning to
>> >>> >>>>> get
>> >>> >>>>> >>>>> iOS on track. Will have a better idea how that platform is
>> >>> >>>>>looking
>> >>> >>>>> >>>>> tomorrow.
>> >>> >>>>> >>>>> - Bada 2.0 still needs a platform implementation before we
>> >>>can
>> >>> >>>>>move
>> >>> >>>>> with
>> >>> >>>>> >>>>> cordova-js on it.
>> >>> >>>>> >>>>>
>> >>> >>>>> >>>>
>> >>> >>>>> >>>> --
>> >>> >>>>> >>>> GOFG - Get On Fat Guy
>> >>> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
>> >>> >>>>> >>>>
>> >>> >>>>> >>>
>> >>> >>>>> >>>
>> >>> >>>>> >>>
>> >>> >>>>> >>> --
>> >>> >>>>> >>> Gord Tanner
>> >>> >>>>> >>> Senior Developer / Code Poet
>> >>> >>>>> >>> tinyHippos Inc.
>> >>> >>>>> >>> @tinyhippos
>> >>> >>>>>
>> >>> >>>>
>> >>> >>>>
>> >>> >>>>
>> >>> >>>> --
>> >>> >>>> Gord Tanner
>> >>> >>>> Senior Developer / Code Poet
>> >>> >>>> tinyHippos Inc.
>> >>> >>>> @tinyhippos
>> >>> >>
>> >>>
>> >>>
>> >>
>> >>
>> >>--
>> >>Gord Tanner
>> >>Senior Developer / Code Poet
>> >>tinyHippos Inc.
>> >>@tinyhippos
>> >
>>
>
>
>
> --
> Gord Tanner
> Senior Developer / Code Poet
> tinyHippos Inc.
> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

You should still be able to run jake and it will build (and have an error
about no jsDom).

Got rid of a bunch of unused modules (anyone know why jQuery was in there?)
and thirdparty code.

https://github.com/callback/callback-js/commit/bb6cd42e1b5a56c2cd9642e8ace386ffcc0b4ce3


On Wed, Feb 15, 2012 at 2:35 PM, Drew Walters <de...@gmail.com> wrote:

> Gord,
>
> Looks like jsDom adds a requirement for the system to have a compiler.
>  Since I don't (and maybe others) have XCode installed on my Mac for
> legal reasons, the configure script fails for me now.
>
> On Wed, Feb 15, 2012 at 12:41 PM, Filip Maj <fi...@adobe.com> wrote:
> > Awwwww yeauuhhh
> >
> > Thanks Gord :D
> >
> > On 12-02-15 10:31 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:
> >
> >>Quick note:
> >>
> >>I added a node runner for our unit tests that will run for every build:
> >>
> >>
> https://github.com/callback/callback-js/blob/master/test/runner.js#L23-58
> >>
> >>If you have already been developing cordova.js you will need to run
> >>./configure again to pull down jsDom to build.
> >>
> >>The intent is that these tests will test the javascript code (mocking
> >>interactions to native) and should be kept green.
> >>
> >>This is not a replacement for cordova-test but a place for us to quickly
> >>spec and test our javascript without the need to load or build into a
> >>simulator.
> >>
> >>to run the tests in node:
> >>
> >>jake
> >>or
> >>jake test
> >>
> >>to run the tests in the browser:
> >>jake btest
> >>
> >>Gord
> >>
> >>On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:
> >>
> >>> Ahh, so more of a packaging question. I'm not sure. I know Steve is
> >>> working on a packaging script so certainly integrating a cordova-js
> >>>build
> >>> into that makes sense.
> >>>
> >>> I think you're on the right track, Drew. We used to include phonegap.js
> >>> into the sample app packaged in each repo - maybe we can keep with that
> >>> same theme for cordova-js and just add some stuff into the README
> >>> regarding where to get/build the latest cordova-js.
> >>>
> >>> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
> >>>
> >>> >I think the way I stated my question is confusing.  Let me try again.
> >>> >Right now the incubator-cordova-blackberry-webworks repo contains both
> >>> >the JS and native code.  Some time soon I would anticipate a
> >>> >incubator-cordova-js repo.  At that time the JS files in the webworks
> >>> >repo should go away.
> >>> >
> >>> >It seems to me that the "vendor" in of a platform specific cordova.js
> >>> >should happen when we build the end user package (ie. the one
> >>> >currently at phonegap.com).  At development time, I'm always going to
> >>> >want the latest one out of incubator-cordova-js so I can just build
> >>> >that myself.  Unless of course there is some mechanism to
> >>> >automatically build incubator-cordova-js when it is updated and copy
> >>> >the built files to the platform repos.
> >>> >
> >>> >Am I wrong?
> >>> >
> >>> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
> >>> >> I think it'd be a pain to submodule cordova-js into the platform
> >>>repos.
> >>> >>
> >>> >> So far the general agreement is to "vendor" cordova-js in as a built
> >>> >> script.
> >>> >>
> >>> >> It should only get out of sync if we let it :)
> >>> >>
> >>> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
> >>> >>
> >>> >>>I need to do some more testing before I agree to move it to the
> >>>apache
> >>> >>>code.  Wanted to get the name change in completely first.  Right now
> >>> >>>some of the api aren't working in my test app.
> >>> >>>
> >>> >>>This brings up a point though.  What will this look like once its
> >>> >>>moved to apache.  I would assume we'll have a separate repo for
> >>> >>>cordova-js, but do the individual platforms really need a copy of
> the
> >>> >>>built js file?  From an end user perspective this could just be
> >>> >>>handled at packaging time when we build the distributable binary.
> >>> >>>Seems like including a built js from cordova-js would lead to it
> >>> >>>getting out of sync.
> >>> >>>
> >>> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
> >>> >>>wrote:
> >>> >>>> OMFG!
> >>> >>>>
> >>> >>>> You just saved my day!
> >>> >>>>
> >>> >>>> I have been looking for why blackberry wasn't firing device ready
> >>>and
> >>> >>>>that
> >>> >>>> bad module ID was it!  I was circling around the channel code
> >>> >>>>attempting to
> >>> >>>> figure out why it wasn't joining after the device and network
> >>>channels
> >>> >>>>were
> >>> >>>> fired.
> >>> >>>>
> >>> >>>> Gonna look into this and pull it in, looks good at first glance.
> >>> >>>>
> >>> >>>>
> >>> >>>> Gord
> >>> >>>>
> >>> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <
> deedubbu@gmail.com>
> >>> >>>>wrote:
> >>> >>>>
> >>> >>>>> Ok, I've submitted a pull request with my changes.
> >>> >>>>>
> >>> >>>>> https://github.com/callback/callback-js/pull/17
> >>> >>>>>
> >>> >>>>> In my previous email, #3 was due to where I had inserted #2
> >>>(oops).
> >>> >>>>> The changes are mostly phonegap -> cordova changes.  Additionally
> >>>I
> >>> >>>>> had to fix a module require in lib/platform/blackberry.js which
> >>>was
> >>> >>>>> specifying a bad module name.
> >>> >>>>>
> >>> >>>>> The only appearance of phonegap in common-js after my change is
> in
> >>> >>>>>the
> >>> >>>>> iOS and WP7 plugins where they reference native code since I
> >>>didn't
> >>> >>>>> think those had been renamed yet.
> >>> >>>>>
> >>> >>>>> Eventually the BlackBerry native side should make use of require
> >>>(as
> >>> >>>>> shown in Fil's commit), but that will wait till common-js gets
> >>>added
> >>> >>>>> to apache source. For the time being a quick hack is to add the
> >>> >>>>> following at the bottom of the generated js:
> >>> >>>>>
> >>> >>>>> var Cordova = require('cordova');
> >>> >>>>>
> >>> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <
> deedubbu@gmail.com>
> >>> >>>>>wrote:
> >>> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't
> >>>submitted
> >>> >>>>> > pull request yet because I'm still debugging something.  Here's
> >>> >>>>> > summary of changes I've made:
> >>> >>>>> >
> >>> >>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
> >>> >>>>> > 2. Added a global define of "Cordova" as a temporary hack since
> >>> >>>>>native
> >>> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
> >>> >>>>> > 3. For some reason I had to make sure the cordova/utils module
> >>> >>>>>exists
> >>> >>>>> > in cordova.js before the cordova/channel module, otherwise I
> was
> >>> >>>>> > getting an error that the module didn't exist.
> >>> >>>>> >
> >>> >>>>> > With the above changes I was able to run some simple tests
> >>> >>>>>(verified
> >>> >>>>> > network works).  I'm currently looking at proper fix for #2 and
> >>>#3.
> >>> >>>>> >
> >>> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters
> >>><de...@gmail.com>
> >>> >>>>> wrote:
> >>> >>>>> >> I'm looking at https://github.com/callback/callback-js and I
> >>>see
> >>> a
> >>> >>>>>lot
> >>> >>>>> >> of references to "phonegap" in the lib/plugins directory
> >>>though it
> >>> >>>>> >> seems like things one directory up (lib) has been changed.  Am
> >>>I
> >>> >>>>>not
> >>> >>>>> >> looking at an up to date project or should I send a pull
> >>>request
> >>> >>>>>with
> >>> >>>>> >> that name change too?
> >>> >>>>> >>
> >>> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner
> >>><gord@tinyhippos.com
> >>> >
> >>> >>>>> wrote:
> >>> >>>>> >>> I am on BlackBerry today.
> >>> >>>>> >>>
> >>> >>>>> >>> Currently showing:
> >>> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
> >>> >>>>> >>>
> >>> >>>>> >>> I will attempt to get it up and running again today.
> >>> >>>>> >>>
> >>> >>>>> >>> I also have the start of a node runner for callback-js tests
> >>> >>>>>here:
> >>> >>>>> >>> https://github.com/gtanner/callback-js
> >>> >>>>> >>>
> >>> >>>>> >>> Gord
> >>> >>>>> >>>
> >>> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
> >>> >>>>><vi...@users.sourceforge.net>
> >>> >>>>> wrote:
> >>> >>>>> >>>
> >>> >>>>> >>>> Can you please drop me a line once cordova-js is on the
> >>>official
> >>> >>>>> repos &
> >>> >>>>> >>>> mirrored? I will then give integrating the new common-JS
> into
> >>> >>>>> cordova-qt a
> >>> >>>>> >>>> go!
> >>> >>>>> >>>>
> >>> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
> >>> >>>>> >>>>
> >>> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
> >>> >>>>> >>>>>
> >>> >>>>> >>>>> - looks like the WP7 implementation cannot run our
> >>>mobile-spec,
> >>> >>>>> which is a
> >>> >>>>> >>>>> hurdle in making sure it supports the cross-platform
> cordova
> >>> >>>>>API.
> >>> >>>>> Before
> >>> >>>>> >>>>> we can move forward with cordova-js integration we really
> >>>need
> >>> >>>>>to
> >>> >>>>> figure
> >>> >>>>> >>>>> that part of it out.
> >>> >>>>> >>>>> - I will work rest of day in getting cordova-js into the
> >>>apache
> >>> >>>>>git
> >>> >>>>> repo
> >>> >>>>> >>>>> and finishing up that work.
> >>> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you
> >>>available?
> >>> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
> >>> >>>>>morning to
> >>> >>>>> get
> >>> >>>>> >>>>> iOS on track. Will have a better idea how that platform is
> >>> >>>>>looking
> >>> >>>>> >>>>> tomorrow.
> >>> >>>>> >>>>> - Bada 2.0 still needs a platform implementation before we
> >>>can
> >>> >>>>>move
> >>> >>>>> with
> >>> >>>>> >>>>> cordova-js on it.
> >>> >>>>> >>>>>
> >>> >>>>> >>>>
> >>> >>>>> >>>> --
> >>> >>>>> >>>> GOFG - Get On Fat Guy
> >>> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
> >>> >>>>> >>>>
> >>> >>>>> >>>
> >>> >>>>> >>>
> >>> >>>>> >>>
> >>> >>>>> >>> --
> >>> >>>>> >>> Gord Tanner
> >>> >>>>> >>> Senior Developer / Code Poet
> >>> >>>>> >>> tinyHippos Inc.
> >>> >>>>> >>> @tinyhippos
> >>> >>>>>
> >>> >>>>
> >>> >>>>
> >>> >>>>
> >>> >>>> --
> >>> >>>> Gord Tanner
> >>> >>>> Senior Developer / Code Poet
> >>> >>>> tinyHippos Inc.
> >>> >>>> @tinyhippos
> >>> >>
> >>>
> >>>
> >>
> >>
> >>--
> >>Gord Tanner
> >>Senior Developer / Code Poet
> >>tinyHippos Inc.
> >>@tinyhippos
> >
>



-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

Gord,

Looks like jsDom adds a requirement for the system to have a compiler.
 Since I don't (and maybe others) have XCode installed on my Mac for
legal reasons, the configure script fails for me now.

On Wed, Feb 15, 2012 at 12:41 PM, Filip Maj <fi...@adobe.com> wrote:
> Awwwww yeauuhhh
>
> Thanks Gord :D
>
> On 12-02-15 10:31 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:
>
>>Quick note:
>>
>>I added a node runner for our unit tests that will run for every build:
>>
>>https://github.com/callback/callback-js/blob/master/test/runner.js#L23-58
>>
>>If you have already been developing cordova.js you will need to run
>>./configure again to pull down jsDom to build.
>>
>>The intent is that these tests will test the javascript code (mocking
>>interactions to native) and should be kept green.
>>
>>This is not a replacement for cordova-test but a place for us to quickly
>>spec and test our javascript without the need to load or build into a
>>simulator.
>>
>>to run the tests in node:
>>
>>jake
>>or
>>jake test
>>
>>to run the tests in the browser:
>>jake btest
>>
>>Gord
>>
>>On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>>> Ahh, so more of a packaging question. I'm not sure. I know Steve is
>>> working on a packaging script so certainly integrating a cordova-js
>>>build
>>> into that makes sense.
>>>
>>> I think you're on the right track, Drew. We used to include phonegap.js
>>> into the sample app packaged in each repo - maybe we can keep with that
>>> same theme for cordova-js and just add some stuff into the README
>>> regarding where to get/build the latest cordova-js.
>>>
>>> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
>>>
>>> >I think the way I stated my question is confusing.  Let me try again.
>>> >Right now the incubator-cordova-blackberry-webworks repo contains both
>>> >the JS and native code.  Some time soon I would anticipate a
>>> >incubator-cordova-js repo.  At that time the JS files in the webworks
>>> >repo should go away.
>>> >
>>> >It seems to me that the "vendor" in of a platform specific cordova.js
>>> >should happen when we build the end user package (ie. the one
>>> >currently at phonegap.com).  At development time, I'm always going to
>>> >want the latest one out of incubator-cordova-js so I can just build
>>> >that myself.  Unless of course there is some mechanism to
>>> >automatically build incubator-cordova-js when it is updated and copy
>>> >the built files to the platform repos.
>>> >
>>> >Am I wrong?
>>> >
>>> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
>>> >> I think it'd be a pain to submodule cordova-js into the platform
>>>repos.
>>> >>
>>> >> So far the general agreement is to "vendor" cordova-js in as a built
>>> >> script.
>>> >>
>>> >> It should only get out of sync if we let it :)
>>> >>
>>> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>>> >>
>>> >>>I need to do some more testing before I agree to move it to the
>>>apache
>>> >>>code.  Wanted to get the name change in completely first.  Right now
>>> >>>some of the api aren't working in my test app.
>>> >>>
>>> >>>This brings up a point though.  What will this look like once its
>>> >>>moved to apache.  I would assume we'll have a separate repo for
>>> >>>cordova-js, but do the individual platforms really need a copy of the
>>> >>>built js file?  From an end user perspective this could just be
>>> >>>handled at packaging time when we build the distributable binary.
>>> >>>Seems like including a built js from cordova-js would lead to it
>>> >>>getting out of sync.
>>> >>>
>>> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
>>> >>>wrote:
>>> >>>> OMFG!
>>> >>>>
>>> >>>> You just saved my day!
>>> >>>>
>>> >>>> I have been looking for why blackberry wasn't firing device ready
>>>and
>>> >>>>that
>>> >>>> bad module ID was it!  I was circling around the channel code
>>> >>>>attempting to
>>> >>>> figure out why it wasn't joining after the device and network
>>>channels
>>> >>>>were
>>> >>>> fired.
>>> >>>>
>>> >>>> Gonna look into this and pull it in, looks good at first glance.
>>> >>>>
>>> >>>>
>>> >>>> Gord
>>> >>>>
>>> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
>>> >>>>wrote:
>>> >>>>
>>> >>>>> Ok, I've submitted a pull request with my changes.
>>> >>>>>
>>> >>>>> https://github.com/callback/callback-js/pull/17
>>> >>>>>
>>> >>>>> In my previous email, #3 was due to where I had inserted #2
>>>(oops).
>>> >>>>> The changes are mostly phonegap -> cordova changes.  Additionally
>>>I
>>> >>>>> had to fix a module require in lib/platform/blackberry.js which
>>>was
>>> >>>>> specifying a bad module name.
>>> >>>>>
>>> >>>>> The only appearance of phonegap in common-js after my change is in
>>> >>>>>the
>>> >>>>> iOS and WP7 plugins where they reference native code since I
>>>didn't
>>> >>>>> think those had been renamed yet.
>>> >>>>>
>>> >>>>> Eventually the BlackBerry native side should make use of require
>>>(as
>>> >>>>> shown in Fil's commit), but that will wait till common-js gets
>>>added
>>> >>>>> to apache source. For the time being a quick hack is to add the
>>> >>>>> following at the bottom of the generated js:
>>> >>>>>
>>> >>>>> var Cordova = require('cordova');
>>> >>>>>
>>> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
>>> >>>>>wrote:
>>> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't
>>>submitted
>>> >>>>> > pull request yet because I'm still debugging something.  Here's
>>> >>>>> > summary of changes I've made:
>>> >>>>> >
>>> >>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>>> >>>>> > 2. Added a global define of "Cordova" as a temporary hack since
>>> >>>>>native
>>> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>>> >>>>> > 3. For some reason I had to make sure the cordova/utils module
>>> >>>>>exists
>>> >>>>> > in cordova.js before the cordova/channel module, otherwise I was
>>> >>>>> > getting an error that the module didn't exist.
>>> >>>>> >
>>> >>>>> > With the above changes I was able to run some simple tests
>>> >>>>>(verified
>>> >>>>> > network works).  I'm currently looking at proper fix for #2 and
>>>#3.
>>> >>>>> >
>>> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters
>>><de...@gmail.com>
>>> >>>>> wrote:
>>> >>>>> >> I'm looking at https://github.com/callback/callback-js and I
>>>see
>>> a
>>> >>>>>lot
>>> >>>>> >> of references to "phonegap" in the lib/plugins directory
>>>though it
>>> >>>>> >> seems like things one directory up (lib) has been changed.  Am
>>>I
>>> >>>>>not
>>> >>>>> >> looking at an up to date project or should I send a pull
>>>request
>>> >>>>>with
>>> >>>>> >> that name change too?
>>> >>>>> >>
>>> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner
>>><gord@tinyhippos.com
>>> >
>>> >>>>> wrote:
>>> >>>>> >>> I am on BlackBerry today.
>>> >>>>> >>>
>>> >>>>> >>> Currently showing:
>>> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>>> >>>>> >>>
>>> >>>>> >>> I will attempt to get it up and running again today.
>>> >>>>> >>>
>>> >>>>> >>> I also have the start of a node runner for callback-js tests
>>> >>>>>here:
>>> >>>>> >>> https://github.com/gtanner/callback-js
>>> >>>>> >>>
>>> >>>>> >>> Gord
>>> >>>>> >>>
>>> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>>> >>>>><vi...@users.sourceforge.net>
>>> >>>>> wrote:
>>> >>>>> >>>
>>> >>>>> >>>> Can you please drop me a line once cordova-js is on the
>>>official
>>> >>>>> repos &
>>> >>>>> >>>> mirrored? I will then give integrating the new common-JS into
>>> >>>>> cordova-qt a
>>> >>>>> >>>> go!
>>> >>>>> >>>>
>>> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>> >>>>> >>>>
>>> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
>>> >>>>> >>>>>
>>> >>>>> >>>>> - looks like the WP7 implementation cannot run our
>>>mobile-spec,
>>> >>>>> which is a
>>> >>>>> >>>>> hurdle in making sure it supports the cross-platform cordova
>>> >>>>>API.
>>> >>>>> Before
>>> >>>>> >>>>> we can move forward with cordova-js integration we really
>>>need
>>> >>>>>to
>>> >>>>> figure
>>> >>>>> >>>>> that part of it out.
>>> >>>>> >>>>> - I will work rest of day in getting cordova-js into the
>>>apache
>>> >>>>>git
>>> >>>>> repo
>>> >>>>> >>>>> and finishing up that work.
>>> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you
>>>available?
>>> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
>>> >>>>>morning to
>>> >>>>> get
>>> >>>>> >>>>> iOS on track. Will have a better idea how that platform is
>>> >>>>>looking
>>> >>>>> >>>>> tomorrow.
>>> >>>>> >>>>> - Bada 2.0 still needs a platform implementation before we
>>>can
>>> >>>>>move
>>> >>>>> with
>>> >>>>> >>>>> cordova-js on it.
>>> >>>>> >>>>>
>>> >>>>> >>>>
>>> >>>>> >>>> --
>>> >>>>> >>>> GOFG - Get On Fat Guy
>>> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
>>> >>>>> >>>>
>>> >>>>> >>>
>>> >>>>> >>>
>>> >>>>> >>>
>>> >>>>> >>> --
>>> >>>>> >>> Gord Tanner
>>> >>>>> >>> Senior Developer / Code Poet
>>> >>>>> >>> tinyHippos Inc.
>>> >>>>> >>> @tinyhippos
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> Gord Tanner
>>> >>>> Senior Developer / Code Poet
>>> >>>> tinyHippos Inc.
>>> >>>> @tinyhippos
>>> >>
>>>
>>>
>>
>>
>>--
>>Gord Tanner
>>Senior Developer / Code Poet
>>tinyHippos Inc.
>>@tinyhippos
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Awwwww yeauuhhh

Thanks Gord :D

On 12-02-15 10:31 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:

>Quick note:
>
>I added a node runner for our unit tests that will run for every build:
>
>https://github.com/callback/callback-js/blob/master/test/runner.js#L23-58
>
>If you have already been developing cordova.js you will need to run
>./configure again to pull down jsDom to build.
>
>The intent is that these tests will test the javascript code (mocking
>interactions to native) and should be kept green.
>
>This is not a replacement for cordova-test but a place for us to quickly
>spec and test our javascript without the need to load or build into a
>simulator.
>
>to run the tests in node:
>
>jake
>or
>jake test
>
>to run the tests in the browser:
>jake btest
>
>Gord
>
>On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Ahh, so more of a packaging question. I'm not sure. I know Steve is
>> working on a packaging script so certainly integrating a cordova-js
>>build
>> into that makes sense.
>>
>> I think you're on the right track, Drew. We used to include phonegap.js
>> into the sample app packaged in each repo - maybe we can keep with that
>> same theme for cordova-js and just add some stuff into the README
>> regarding where to get/build the latest cordova-js.
>>
>> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
>>
>> >I think the way I stated my question is confusing.  Let me try again.
>> >Right now the incubator-cordova-blackberry-webworks repo contains both
>> >the JS and native code.  Some time soon I would anticipate a
>> >incubator-cordova-js repo.  At that time the JS files in the webworks
>> >repo should go away.
>> >
>> >It seems to me that the "vendor" in of a platform specific cordova.js
>> >should happen when we build the end user package (ie. the one
>> >currently at phonegap.com).  At development time, I'm always going to
>> >want the latest one out of incubator-cordova-js so I can just build
>> >that myself.  Unless of course there is some mechanism to
>> >automatically build incubator-cordova-js when it is updated and copy
>> >the built files to the platform repos.
>> >
>> >Am I wrong?
>> >
>> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
>> >> I think it'd be a pain to submodule cordova-js into the platform
>>repos.
>> >>
>> >> So far the general agreement is to "vendor" cordova-js in as a built
>> >> script.
>> >>
>> >> It should only get out of sync if we let it :)
>> >>
>> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>> >>
>> >>>I need to do some more testing before I agree to move it to the
>>apache
>> >>>code.  Wanted to get the name change in completely first.  Right now
>> >>>some of the api aren't working in my test app.
>> >>>
>> >>>This brings up a point though.  What will this look like once its
>> >>>moved to apache.  I would assume we'll have a separate repo for
>> >>>cordova-js, but do the individual platforms really need a copy of the
>> >>>built js file?  From an end user perspective this could just be
>> >>>handled at packaging time when we build the distributable binary.
>> >>>Seems like including a built js from cordova-js would lead to it
>> >>>getting out of sync.
>> >>>
>> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
>> >>>wrote:
>> >>>> OMFG!
>> >>>>
>> >>>> You just saved my day!
>> >>>>
>> >>>> I have been looking for why blackberry wasn't firing device ready
>>and
>> >>>>that
>> >>>> bad module ID was it!  I was circling around the channel code
>> >>>>attempting to
>> >>>> figure out why it wasn't joining after the device and network
>>channels
>> >>>>were
>> >>>> fired.
>> >>>>
>> >>>> Gonna look into this and pull it in, looks good at first glance.
>> >>>>
>> >>>>
>> >>>> Gord
>> >>>>
>> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
>> >>>>wrote:
>> >>>>
>> >>>>> Ok, I've submitted a pull request with my changes.
>> >>>>>
>> >>>>> https://github.com/callback/callback-js/pull/17
>> >>>>>
>> >>>>> In my previous email, #3 was due to where I had inserted #2
>>(oops).
>> >>>>> The changes are mostly phonegap -> cordova changes.  Additionally
>>I
>> >>>>> had to fix a module require in lib/platform/blackberry.js which
>>was
>> >>>>> specifying a bad module name.
>> >>>>>
>> >>>>> The only appearance of phonegap in common-js after my change is in
>> >>>>>the
>> >>>>> iOS and WP7 plugins where they reference native code since I
>>didn't
>> >>>>> think those had been renamed yet.
>> >>>>>
>> >>>>> Eventually the BlackBerry native side should make use of require
>>(as
>> >>>>> shown in Fil's commit), but that will wait till common-js gets
>>added
>> >>>>> to apache source. For the time being a quick hack is to add the
>> >>>>> following at the bottom of the generated js:
>> >>>>>
>> >>>>> var Cordova = require('cordova');
>> >>>>>
>> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
>> >>>>>wrote:
>> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't
>>submitted
>> >>>>> > pull request yet because I'm still debugging something.  Here's
>> >>>>> > summary of changes I've made:
>> >>>>> >
>> >>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>> >>>>> > 2. Added a global define of "Cordova" as a temporary hack since
>> >>>>>native
>> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>> >>>>> > 3. For some reason I had to make sure the cordova/utils module
>> >>>>>exists
>> >>>>> > in cordova.js before the cordova/channel module, otherwise I was
>> >>>>> > getting an error that the module didn't exist.
>> >>>>> >
>> >>>>> > With the above changes I was able to run some simple tests
>> >>>>>(verified
>> >>>>> > network works).  I'm currently looking at proper fix for #2 and
>>#3.
>> >>>>> >
>> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters
>><de...@gmail.com>
>> >>>>> wrote:
>> >>>>> >> I'm looking at https://github.com/callback/callback-js and I
>>see
>> a
>> >>>>>lot
>> >>>>> >> of references to "phonegap" in the lib/plugins directory
>>though it
>> >>>>> >> seems like things one directory up (lib) has been changed.  Am
>>I
>> >>>>>not
>> >>>>> >> looking at an up to date project or should I send a pull
>>request
>> >>>>>with
>> >>>>> >> that name change too?
>> >>>>> >>
>> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner
>><gord@tinyhippos.com
>> >
>> >>>>> wrote:
>> >>>>> >>> I am on BlackBerry today.
>> >>>>> >>>
>> >>>>> >>> Currently showing:
>> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>> >>>>> >>>
>> >>>>> >>> I will attempt to get it up and running again today.
>> >>>>> >>>
>> >>>>> >>> I also have the start of a node runner for callback-js tests
>> >>>>>here:
>> >>>>> >>> https://github.com/gtanner/callback-js
>> >>>>> >>>
>> >>>>> >>> Gord
>> >>>>> >>>
>> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>> >>>>><vi...@users.sourceforge.net>
>> >>>>> wrote:
>> >>>>> >>>
>> >>>>> >>>> Can you please drop me a line once cordova-js is on the
>>official
>> >>>>> repos &
>> >>>>> >>>> mirrored? I will then give integrating the new common-JS into
>> >>>>> cordova-qt a
>> >>>>> >>>> go!
>> >>>>> >>>>
>> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>> >>>>> >>>>
>> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
>> >>>>> >>>>>
>> >>>>> >>>>> - looks like the WP7 implementation cannot run our
>>mobile-spec,
>> >>>>> which is a
>> >>>>> >>>>> hurdle in making sure it supports the cross-platform cordova
>> >>>>>API.
>> >>>>> Before
>> >>>>> >>>>> we can move forward with cordova-js integration we really
>>need
>> >>>>>to
>> >>>>> figure
>> >>>>> >>>>> that part of it out.
>> >>>>> >>>>> - I will work rest of day in getting cordova-js into the
>>apache
>> >>>>>git
>> >>>>> repo
>> >>>>> >>>>> and finishing up that work.
>> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you
>>available?
>> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
>> >>>>>morning to
>> >>>>> get
>> >>>>> >>>>> iOS on track. Will have a better idea how that platform is
>> >>>>>looking
>> >>>>> >>>>> tomorrow.
>> >>>>> >>>>> - Bada 2.0 still needs a platform implementation before we
>>can
>> >>>>>move
>> >>>>> with
>> >>>>> >>>>> cordova-js on it.
>> >>>>> >>>>>
>> >>>>> >>>>
>> >>>>> >>>> --
>> >>>>> >>>> GOFG - Get On Fat Guy
>> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
>> >>>>> >>>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>> --
>> >>>>> >>> Gord Tanner
>> >>>>> >>> Senior Developer / Code Poet
>> >>>>> >>> tinyHippos Inc.
>> >>>>> >>> @tinyhippos
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Gord Tanner
>> >>>> Senior Developer / Code Poet
>> >>>> tinyHippos Inc.
>> >>>> @tinyhippos
>> >>
>>
>>
>
>
>--
>Gord Tanner
>Senior Developer / Code Poet
>tinyHippos Inc.
>@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

Quick note:

I added a node runner for our unit tests that will run for every build:

https://github.com/callback/callback-js/blob/master/test/runner.js#L23-58

If you have already been developing cordova.js you will need to run
./configure again to pull down jsDom to build.

The intent is that these tests will test the javascript code (mocking
interactions to native) and should be kept green.

This is not a replacement for cordova-test but a place for us to quickly
spec and test our javascript without the need to load or build into a
simulator.

to run the tests in node:

jake
or
jake test

to run the tests in the browser:
jake btest

Gord

On Wed, Feb 15, 2012 at 1:21 PM, Filip Maj <fi...@adobe.com> wrote:

> Ahh, so more of a packaging question. I'm not sure. I know Steve is
> working on a packaging script so certainly integrating a cordova-js build
> into that makes sense.
>
> I think you're on the right track, Drew. We used to include phonegap.js
> into the sample app packaged in each repo - maybe we can keep with that
> same theme for cordova-js and just add some stuff into the README
> regarding where to get/build the latest cordova-js.
>
> On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:
>
> >I think the way I stated my question is confusing.  Let me try again.
> >Right now the incubator-cordova-blackberry-webworks repo contains both
> >the JS and native code.  Some time soon I would anticipate a
> >incubator-cordova-js repo.  At that time the JS files in the webworks
> >repo should go away.
> >
> >It seems to me that the "vendor" in of a platform specific cordova.js
> >should happen when we build the end user package (ie. the one
> >currently at phonegap.com).  At development time, I'm always going to
> >want the latest one out of incubator-cordova-js so I can just build
> >that myself.  Unless of course there is some mechanism to
> >automatically build incubator-cordova-js when it is updated and copy
> >the built files to the platform repos.
> >
> >Am I wrong?
> >
> >On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
> >> I think it'd be a pain to submodule cordova-js into the platform repos.
> >>
> >> So far the general agreement is to "vendor" cordova-js in as a built
> >> script.
> >>
> >> It should only get out of sync if we let it :)
> >>
> >> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
> >>
> >>>I need to do some more testing before I agree to move it to the apache
> >>>code.  Wanted to get the name change in completely first.  Right now
> >>>some of the api aren't working in my test app.
> >>>
> >>>This brings up a point though.  What will this look like once its
> >>>moved to apache.  I would assume we'll have a separate repo for
> >>>cordova-js, but do the individual platforms really need a copy of the
> >>>built js file?  From an end user perspective this could just be
> >>>handled at packaging time when we build the distributable binary.
> >>>Seems like including a built js from cordova-js would lead to it
> >>>getting out of sync.
> >>>
> >>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
> >>>wrote:
> >>>> OMFG!
> >>>>
> >>>> You just saved my day!
> >>>>
> >>>> I have been looking for why blackberry wasn't firing device ready and
> >>>>that
> >>>> bad module ID was it!  I was circling around the channel code
> >>>>attempting to
> >>>> figure out why it wasn't joining after the device and network channels
> >>>>were
> >>>> fired.
> >>>>
> >>>> Gonna look into this and pull it in, looks good at first glance.
> >>>>
> >>>>
> >>>> Gord
> >>>>
> >>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
> >>>>wrote:
> >>>>
> >>>>> Ok, I've submitted a pull request with my changes.
> >>>>>
> >>>>> https://github.com/callback/callback-js/pull/17
> >>>>>
> >>>>> In my previous email, #3 was due to where I had inserted #2 (oops).
> >>>>> The changes are mostly phonegap -> cordova changes.  Additionally I
> >>>>> had to fix a module require in lib/platform/blackberry.js which was
> >>>>> specifying a bad module name.
> >>>>>
> >>>>> The only appearance of phonegap in common-js after my change is in
> >>>>>the
> >>>>> iOS and WP7 plugins where they reference native code since I didn't
> >>>>> think those had been renamed yet.
> >>>>>
> >>>>> Eventually the BlackBerry native side should make use of require (as
> >>>>> shown in Fil's commit), but that will wait till common-js gets added
> >>>>> to apache source. For the time being a quick hack is to add the
> >>>>> following at the bottom of the generated js:
> >>>>>
> >>>>> var Cordova = require('cordova');
> >>>>>
> >>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
> >>>>>wrote:
> >>>>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
> >>>>> > pull request yet because I'm still debugging something.  Here's
> >>>>> > summary of changes I've made:
> >>>>> >
> >>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
> >>>>> > 2. Added a global define of "Cordova" as a temporary hack since
> >>>>>native
> >>>>> > PluginResult.toSuccessCallbackString expects it to exist.
> >>>>> > 3. For some reason I had to make sure the cordova/utils module
> >>>>>exists
> >>>>> > in cordova.js before the cordova/channel module, otherwise I was
> >>>>> > getting an error that the module didn't exist.
> >>>>> >
> >>>>> > With the above changes I was able to run some simple tests
> >>>>>(verified
> >>>>> > network works).  I'm currently looking at proper fix for #2 and #3.
> >>>>> >
> >>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
> >>>>> wrote:
> >>>>> >> I'm looking at https://github.com/callback/callback-js and I see
> a
> >>>>>lot
> >>>>> >> of references to "phonegap" in the lib/plugins directory though it
> >>>>> >> seems like things one directory up (lib) has been changed.  Am I
> >>>>>not
> >>>>> >> looking at an up to date project or should I send a pull request
> >>>>>with
> >>>>> >> that name change too?
> >>>>> >>
> >>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <gord@tinyhippos.com
> >
> >>>>> wrote:
> >>>>> >>> I am on BlackBerry today.
> >>>>> >>>
> >>>>> >>> Currently showing:
> >>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
> >>>>> >>>
> >>>>> >>> I will attempt to get it up and running again today.
> >>>>> >>>
> >>>>> >>> I also have the start of a node runner for callback-js tests
> >>>>>here:
> >>>>> >>> https://github.com/gtanner/callback-js
> >>>>> >>>
> >>>>> >>> Gord
> >>>>> >>>
> >>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
> >>>>><vi...@users.sourceforge.net>
> >>>>> wrote:
> >>>>> >>>
> >>>>> >>>> Can you please drop me a line once cordova-js is on the official
> >>>>> repos &
> >>>>> >>>> mirrored? I will then give integrating the new common-JS into
> >>>>> cordova-qt a
> >>>>> >>>> go!
> >>>>> >>>>
> >>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
> >>>>> >>>>
> >>>>> >>>>  Update on unified JavaScript work in cordova for today:
> >>>>> >>>>>
> >>>>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
> >>>>> which is a
> >>>>> >>>>> hurdle in making sure it supports the cross-platform cordova
> >>>>>API.
> >>>>> Before
> >>>>> >>>>> we can move forward with cordova-js integration we really need
> >>>>>to
> >>>>> figure
> >>>>> >>>>> that part of it out.
> >>>>> >>>>> - I will work rest of day in getting cordova-js into the apache
> >>>>>git
> >>>>> repo
> >>>>> >>>>> and finishing up that work.
> >>>>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
> >>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
> >>>>>morning to
> >>>>> get
> >>>>> >>>>> iOS on track. Will have a better idea how that platform is
> >>>>>looking
> >>>>> >>>>> tomorrow.
> >>>>> >>>>> - Bada 2.0 still needs a platform implementation before we can
> >>>>>move
> >>>>> with
> >>>>> >>>>> cordova-js on it.
> >>>>> >>>>>
> >>>>> >>>>
> >>>>> >>>> --
> >>>>> >>>> GOFG - Get On Fat Guy
> >>>>> >>>> http://www.gofg.at/ - powered by Cordova
> >>>>> >>>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> --
> >>>>> >>> Gord Tanner
> >>>>> >>> Senior Developer / Code Poet
> >>>>> >>> tinyHippos Inc.
> >>>>> >>> @tinyhippos
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Gord Tanner
> >>>> Senior Developer / Code Poet
> >>>> tinyHippos Inc.
> >>>> @tinyhippos
> >>
>
>


-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Ahh, so more of a packaging question. I'm not sure. I know Steve is
working on a packaging script so certainly integrating a cordova-js build
into that makes sense.

I think you're on the right track, Drew. We used to include phonegap.js
into the sample app packaged in each repo - maybe we can keep with that
same theme for cordova-js and just add some stuff into the README
regarding where to get/build the latest cordova-js.

On 12-02-15 9:28 AM, "Drew Walters" <de...@gmail.com> wrote:

>I think the way I stated my question is confusing.  Let me try again.
>Right now the incubator-cordova-blackberry-webworks repo contains both
>the JS and native code.  Some time soon I would anticipate a
>incubator-cordova-js repo.  At that time the JS files in the webworks
>repo should go away.
>
>It seems to me that the "vendor" in of a platform specific cordova.js
>should happen when we build the end user package (ie. the one
>currently at phonegap.com).  At development time, I'm always going to
>want the latest one out of incubator-cordova-js so I can just build
>that myself.  Unless of course there is some mechanism to
>automatically build incubator-cordova-js when it is updated and copy
>the built files to the platform repos.
>
>Am I wrong?
>
>On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
>> I think it'd be a pain to submodule cordova-js into the platform repos.
>>
>> So far the general agreement is to "vendor" cordova-js in as a built
>> script.
>>
>> It should only get out of sync if we let it :)
>>
>> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>>
>>>I need to do some more testing before I agree to move it to the apache
>>>code.  Wanted to get the name change in completely first.  Right now
>>>some of the api aren't working in my test app.
>>>
>>>This brings up a point though.  What will this look like once its
>>>moved to apache.  I would assume we'll have a separate repo for
>>>cordova-js, but do the individual platforms really need a copy of the
>>>built js file?  From an end user perspective this could just be
>>>handled at packaging time when we build the distributable binary.
>>>Seems like including a built js from cordova-js would lead to it
>>>getting out of sync.
>>>
>>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com>
>>>wrote:
>>>> OMFG!
>>>>
>>>> You just saved my day!
>>>>
>>>> I have been looking for why blackberry wasn't firing device ready and
>>>>that
>>>> bad module ID was it!  I was circling around the channel code
>>>>attempting to
>>>> figure out why it wasn't joining after the device and network channels
>>>>were
>>>> fired.
>>>>
>>>> Gonna look into this and pull it in, looks good at first glance.
>>>>
>>>>
>>>> Gord
>>>>
>>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
>>>>wrote:
>>>>
>>>>> Ok, I've submitted a pull request with my changes.
>>>>>
>>>>> https://github.com/callback/callback-js/pull/17
>>>>>
>>>>> In my previous email, #3 was due to where I had inserted #2 (oops).
>>>>> The changes are mostly phonegap -> cordova changes.  Additionally I
>>>>> had to fix a module require in lib/platform/blackberry.js which was
>>>>> specifying a bad module name.
>>>>>
>>>>> The only appearance of phonegap in common-js after my change is in
>>>>>the
>>>>> iOS and WP7 plugins where they reference native code since I didn't
>>>>> think those had been renamed yet.
>>>>>
>>>>> Eventually the BlackBerry native side should make use of require (as
>>>>> shown in Fil's commit), but that will wait till common-js gets added
>>>>> to apache source. For the time being a quick hack is to add the
>>>>> following at the bottom of the generated js:
>>>>>
>>>>> var Cordova = require('cordova');
>>>>>
>>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
>>>>>wrote:
>>>>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
>>>>> > pull request yet because I'm still debugging something.  Here's
>>>>> > summary of changes I've made:
>>>>> >
>>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>>>>> > 2. Added a global define of "Cordova" as a temporary hack since
>>>>>native
>>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>>>>> > 3. For some reason I had to make sure the cordova/utils module
>>>>>exists
>>>>> > in cordova.js before the cordova/channel module, otherwise I was
>>>>> > getting an error that the module didn't exist.
>>>>> >
>>>>> > With the above changes I was able to run some simple tests
>>>>>(verified
>>>>> > network works).  I'm currently looking at proper fix for #2 and #3.
>>>>> >
>>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>>>>> wrote:
>>>>> >> I'm looking at https://github.com/callback/callback-js and I see a
>>>>>lot
>>>>> >> of references to "phonegap" in the lib/plugins directory though it
>>>>> >> seems like things one directory up (lib) has been changed.  Am I
>>>>>not
>>>>> >> looking at an up to date project or should I send a pull request
>>>>>with
>>>>> >> that name change too?
>>>>> >>
>>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>>>>> wrote:
>>>>> >>> I am on BlackBerry today.
>>>>> >>>
>>>>> >>> Currently showing:
>>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>>>>> >>>
>>>>> >>> I will attempt to get it up and running again today.
>>>>> >>>
>>>>> >>> I also have the start of a node runner for callback-js tests
>>>>>here:
>>>>> >>> https://github.com/gtanner/callback-js
>>>>> >>>
>>>>> >>> Gord
>>>>> >>>
>>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>>>>><vi...@users.sourceforge.net>
>>>>> wrote:
>>>>> >>>
>>>>> >>>> Can you please drop me a line once cordova-js is on the official
>>>>> repos &
>>>>> >>>> mirrored? I will then give integrating the new common-JS into
>>>>> cordova-qt a
>>>>> >>>> go!
>>>>> >>>>
>>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>>>> >>>>
>>>>> >>>>  Update on unified JavaScript work in cordova for today:
>>>>> >>>>>
>>>>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>>>>> which is a
>>>>> >>>>> hurdle in making sure it supports the cross-platform cordova
>>>>>API.
>>>>> Before
>>>>> >>>>> we can move forward with cordova-js integration we really need
>>>>>to
>>>>> figure
>>>>> >>>>> that part of it out.
>>>>> >>>>> - I will work rest of day in getting cordova-js into the apache
>>>>>git
>>>>> repo
>>>>> >>>>> and finishing up that work.
>>>>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
>>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
>>>>>morning to
>>>>> get
>>>>> >>>>> iOS on track. Will have a better idea how that platform is
>>>>>looking
>>>>> >>>>> tomorrow.
>>>>> >>>>> - Bada 2.0 still needs a platform implementation before we can
>>>>>move
>>>>> with
>>>>> >>>>> cordova-js on it.
>>>>> >>>>>
>>>>> >>>>
>>>>> >>>> --
>>>>> >>>> GOFG - Get On Fat Guy
>>>>> >>>> http://www.gofg.at/ - powered by Cordova
>>>>> >>>>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> --
>>>>> >>> Gord Tanner
>>>>> >>> Senior Developer / Code Poet
>>>>> >>> tinyHippos Inc.
>>>>> >>> @tinyhippos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Gord Tanner
>>>> Senior Developer / Code Poet
>>>> tinyHippos Inc.
>>>> @tinyhippos
>>

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

I think the way I stated my question is confusing.  Let me try again.
Right now the incubator-cordova-blackberry-webworks repo contains both
the JS and native code.  Some time soon I would anticipate a
incubator-cordova-js repo.  At that time the JS files in the webworks
repo should go away.

It seems to me that the "vendor" in of a platform specific cordova.js
should happen when we build the end user package (ie. the one
currently at phonegap.com).  At development time, I'm always going to
want the latest one out of incubator-cordova-js so I can just build
that myself.  Unless of course there is some mechanism to
automatically build incubator-cordova-js when it is updated and copy
the built files to the platform repos.

Am I wrong?

On Wed, Feb 15, 2012 at 11:15 AM, Filip Maj <fi...@adobe.com> wrote:
> I think it'd be a pain to submodule cordova-js into the platform repos.
>
> So far the general agreement is to "vendor" cordova-js in as a built
> script.
>
> It should only get out of sync if we let it :)
>
> On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:
>
>>I need to do some more testing before I agree to move it to the apache
>>code.  Wanted to get the name change in completely first.  Right now
>>some of the api aren't working in my test app.
>>
>>This brings up a point though.  What will this look like once its
>>moved to apache.  I would assume we'll have a separate repo for
>>cordova-js, but do the individual platforms really need a copy of the
>>built js file?  From an end user perspective this could just be
>>handled at packaging time when we build the distributable binary.
>>Seems like including a built js from cordova-js would lead to it
>>getting out of sync.
>>
>>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com> wrote:
>>> OMFG!
>>>
>>> You just saved my day!
>>>
>>> I have been looking for why blackberry wasn't firing device ready and
>>>that
>>> bad module ID was it!  I was circling around the channel code
>>>attempting to
>>> figure out why it wasn't joining after the device and network channels
>>>were
>>> fired.
>>>
>>> Gonna look into this and pull it in, looks good at first glance.
>>>
>>>
>>> Gord
>>>
>>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
>>>wrote:
>>>
>>>> Ok, I've submitted a pull request with my changes.
>>>>
>>>> https://github.com/callback/callback-js/pull/17
>>>>
>>>> In my previous email, #3 was due to where I had inserted #2 (oops).
>>>> The changes are mostly phonegap -> cordova changes.  Additionally I
>>>> had to fix a module require in lib/platform/blackberry.js which was
>>>> specifying a bad module name.
>>>>
>>>> The only appearance of phonegap in common-js after my change is in the
>>>> iOS and WP7 plugins where they reference native code since I didn't
>>>> think those had been renamed yet.
>>>>
>>>> Eventually the BlackBerry native side should make use of require (as
>>>> shown in Fil's commit), but that will wait till common-js gets added
>>>> to apache source. For the time being a quick hack is to add the
>>>> following at the bottom of the generated js:
>>>>
>>>> var Cordova = require('cordova');
>>>>
>>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
>>>>wrote:
>>>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
>>>> > pull request yet because I'm still debugging something.  Here's
>>>> > summary of changes I've made:
>>>> >
>>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>>>> > 2. Added a global define of "Cordova" as a temporary hack since
>>>>native
>>>> > PluginResult.toSuccessCallbackString expects it to exist.
>>>> > 3. For some reason I had to make sure the cordova/utils module exists
>>>> > in cordova.js before the cordova/channel module, otherwise I was
>>>> > getting an error that the module didn't exist.
>>>> >
>>>> > With the above changes I was able to run some simple tests (verified
>>>> > network works).  I'm currently looking at proper fix for #2 and #3.
>>>> >
>>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>>>> wrote:
>>>> >> I'm looking at https://github.com/callback/callback-js and I see a
>>>>lot
>>>> >> of references to "phonegap" in the lib/plugins directory though it
>>>> >> seems like things one directory up (lib) has been changed.  Am I not
>>>> >> looking at an up to date project or should I send a pull request
>>>>with
>>>> >> that name change too?
>>>> >>
>>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>>>> wrote:
>>>> >>> I am on BlackBerry today.
>>>> >>>
>>>> >>> Currently showing:
>>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>>>> >>>
>>>> >>> I will attempt to get it up and running again today.
>>>> >>>
>>>> >>> I also have the start of a node runner for callback-js tests here:
>>>> >>> https://github.com/gtanner/callback-js
>>>> >>>
>>>> >>> Gord
>>>> >>>
>>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>>>><vi...@users.sourceforge.net>
>>>> wrote:
>>>> >>>
>>>> >>>> Can you please drop me a line once cordova-js is on the official
>>>> repos &
>>>> >>>> mirrored? I will then give integrating the new common-JS into
>>>> cordova-qt a
>>>> >>>> go!
>>>> >>>>
>>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>>> >>>>
>>>> >>>>  Update on unified JavaScript work in cordova for today:
>>>> >>>>>
>>>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>>>> which is a
>>>> >>>>> hurdle in making sure it supports the cross-platform cordova API.
>>>> Before
>>>> >>>>> we can move forward with cordova-js integration we really need to
>>>> figure
>>>> >>>>> that part of it out.
>>>> >>>>> - I will work rest of day in getting cordova-js into the apache
>>>>git
>>>> repo
>>>> >>>>> and finishing up that work.
>>>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
>>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
>>>>morning to
>>>> get
>>>> >>>>> iOS on track. Will have a better idea how that platform is
>>>>looking
>>>> >>>>> tomorrow.
>>>> >>>>> - Bada 2.0 still needs a platform implementation before we can
>>>>move
>>>> with
>>>> >>>>> cordova-js on it.
>>>> >>>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>> GOFG - Get On Fat Guy
>>>> >>>> http://www.gofg.at/ - powered by Cordova
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Gord Tanner
>>>> >>> Senior Developer / Code Poet
>>>> >>> tinyHippos Inc.
>>>> >>> @tinyhippos
>>>>
>>>
>>>
>>>
>>> --
>>> Gord Tanner
>>> Senior Developer / Code Poet
>>> tinyHippos Inc.
>>> @tinyhippos
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

I think it'd be a pain to submodule cordova-js into the platform repos.

So far the general agreement is to "vendor" cordova-js in as a built
script.

It should only get out of sync if we let it :)

On 12-02-15 9:11 AM, "Drew Walters" <de...@gmail.com> wrote:

>I need to do some more testing before I agree to move it to the apache
>code.  Wanted to get the name change in completely first.  Right now
>some of the api aren't working in my test app.
>
>This brings up a point though.  What will this look like once its
>moved to apache.  I would assume we'll have a separate repo for
>cordova-js, but do the individual platforms really need a copy of the
>built js file?  From an end user perspective this could just be
>handled at packaging time when we build the distributable binary.
>Seems like including a built js from cordova-js would lead to it
>getting out of sync.
>
>On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com> wrote:
>> OMFG!
>>
>> You just saved my day!
>>
>> I have been looking for why blackberry wasn't firing device ready and
>>that
>> bad module ID was it!  I was circling around the channel code
>>attempting to
>> figure out why it wasn't joining after the device and network channels
>>were
>> fired.
>>
>> Gonna look into this and pull it in, looks good at first glance.
>>
>>
>> Gord
>>
>> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com>
>>wrote:
>>
>>> Ok, I've submitted a pull request with my changes.
>>>
>>> https://github.com/callback/callback-js/pull/17
>>>
>>> In my previous email, #3 was due to where I had inserted #2 (oops).
>>> The changes are mostly phonegap -> cordova changes.  Additionally I
>>> had to fix a module require in lib/platform/blackberry.js which was
>>> specifying a bad module name.
>>>
>>> The only appearance of phonegap in common-js after my change is in the
>>> iOS and WP7 plugins where they reference native code since I didn't
>>> think those had been renamed yet.
>>>
>>> Eventually the BlackBerry native side should make use of require (as
>>> shown in Fil's commit), but that will wait till common-js gets added
>>> to apache source. For the time being a quick hack is to add the
>>> following at the bottom of the generated js:
>>>
>>> var Cordova = require('cordova');
>>>
>>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
>>>wrote:
>>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
>>> > pull request yet because I'm still debugging something.  Here's
>>> > summary of changes I've made:
>>> >
>>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>>> > 2. Added a global define of "Cordova" as a temporary hack since
>>>native
>>> > PluginResult.toSuccessCallbackString expects it to exist.
>>> > 3. For some reason I had to make sure the cordova/utils module exists
>>> > in cordova.js before the cordova/channel module, otherwise I was
>>> > getting an error that the module didn't exist.
>>> >
>>> > With the above changes I was able to run some simple tests (verified
>>> > network works).  I'm currently looking at proper fix for #2 and #3.
>>> >
>>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>>> wrote:
>>> >> I'm looking at https://github.com/callback/callback-js and I see a
>>>lot
>>> >> of references to "phonegap" in the lib/plugins directory though it
>>> >> seems like things one directory up (lib) has been changed.  Am I not
>>> >> looking at an up to date project or should I send a pull request
>>>with
>>> >> that name change too?
>>> >>
>>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>>> wrote:
>>> >>> I am on BlackBerry today.
>>> >>>
>>> >>> Currently showing:
>>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>>> >>>
>>> >>> I will attempt to get it up and running again today.
>>> >>>
>>> >>> I also have the start of a node runner for callback-js tests here:
>>> >>> https://github.com/gtanner/callback-js
>>> >>>
>>> >>> Gord
>>> >>>
>>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras
>>><vi...@users.sourceforge.net>
>>> wrote:
>>> >>>
>>> >>>> Can you please drop me a line once cordova-js is on the official
>>> repos &
>>> >>>> mirrored? I will then give integrating the new common-JS into
>>> cordova-qt a
>>> >>>> go!
>>> >>>>
>>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>> >>>>
>>> >>>>  Update on unified JavaScript work in cordova for today:
>>> >>>>>
>>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>>> which is a
>>> >>>>> hurdle in making sure it supports the cross-platform cordova API.
>>> Before
>>> >>>>> we can move forward with cordova-js integration we really need to
>>> figure
>>> >>>>> that part of it out.
>>> >>>>> - I will work rest of day in getting cordova-js into the apache
>>>git
>>> repo
>>> >>>>> and finishing up that work.
>>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
>>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow
>>>morning to
>>> get
>>> >>>>> iOS on track. Will have a better idea how that platform is
>>>looking
>>> >>>>> tomorrow.
>>> >>>>> - Bada 2.0 still needs a platform implementation before we can
>>>move
>>> with
>>> >>>>> cordova-js on it.
>>> >>>>>
>>> >>>>
>>> >>>> --
>>> >>>> GOFG - Get On Fat Guy
>>> >>>> http://www.gofg.at/ - powered by Cordova
>>> >>>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Gord Tanner
>>> >>> Senior Developer / Code Poet
>>> >>> tinyHippos Inc.
>>> >>> @tinyhippos
>>>
>>
>>
>>
>> --
>> Gord Tanner
>> Senior Developer / Code Poet
>> tinyHippos Inc.
>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

I need to do some more testing before I agree to move it to the apache
code.  Wanted to get the name change in completely first.  Right now
some of the api aren't working in my test app.

This brings up a point though.  What will this look like once its
moved to apache.  I would assume we'll have a separate repo for
cordova-js, but do the individual platforms really need a copy of the
built js file?  From an end user perspective this could just be
handled at packaging time when we build the distributable binary.
Seems like including a built js from cordova-js would lead to it
getting out of sync.

On Wed, Feb 15, 2012 at 11:03 AM, Gord Tanner <go...@tinyhippos.com> wrote:
> OMFG!
>
> You just saved my day!
>
> I have been looking for why blackberry wasn't firing device ready and that
> bad module ID was it!  I was circling around the channel code attempting to
> figure out why it wasn't joining after the device and network channels were
> fired.
>
> Gonna look into this and pull it in, looks good at first glance.
>
>
> Gord
>
> On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com> wrote:
>
>> Ok, I've submitted a pull request with my changes.
>>
>> https://github.com/callback/callback-js/pull/17
>>
>> In my previous email, #3 was due to where I had inserted #2 (oops).
>> The changes are mostly phonegap -> cordova changes.  Additionally I
>> had to fix a module require in lib/platform/blackberry.js which was
>> specifying a bad module name.
>>
>> The only appearance of phonegap in common-js after my change is in the
>> iOS and WP7 plugins where they reference native code since I didn't
>> think those had been renamed yet.
>>
>> Eventually the BlackBerry native side should make use of require (as
>> shown in Fil's commit), but that will wait till common-js gets added
>> to apache source. For the time being a quick hack is to add the
>> following at the bottom of the generated js:
>>
>> var Cordova = require('cordova');
>>
>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com> wrote:
>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
>> > pull request yet because I'm still debugging something.  Here's
>> > summary of changes I've made:
>> >
>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>> > 2. Added a global define of "Cordova" as a temporary hack since native
>> > PluginResult.toSuccessCallbackString expects it to exist.
>> > 3. For some reason I had to make sure the cordova/utils module exists
>> > in cordova.js before the cordova/channel module, otherwise I was
>> > getting an error that the module didn't exist.
>> >
>> > With the above changes I was able to run some simple tests (verified
>> > network works).  I'm currently looking at proper fix for #2 and #3.
>> >
>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>> wrote:
>> >> I'm looking at https://github.com/callback/callback-js and I see a lot
>> >> of references to "phonegap" in the lib/plugins directory though it
>> >> seems like things one directory up (lib) has been changed.  Am I not
>> >> looking at an up to date project or should I send a pull request with
>> >> that name change too?
>> >>
>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>> wrote:
>> >>> I am on BlackBerry today.
>> >>>
>> >>> Currently showing:
>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>> >>>
>> >>> I will attempt to get it up and running again today.
>> >>>
>> >>> I also have the start of a node runner for callback-js tests here:
>> >>> https://github.com/gtanner/callback-js
>> >>>
>> >>> Gord
>> >>>
>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net>
>> wrote:
>> >>>
>> >>>> Can you please drop me a line once cordova-js is on the official
>> repos &
>> >>>> mirrored? I will then give integrating the new common-JS into
>> cordova-qt a
>> >>>> go!
>> >>>>
>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>> >>>>
>> >>>>  Update on unified JavaScript work in cordova for today:
>> >>>>>
>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>> which is a
>> >>>>> hurdle in making sure it supports the cross-platform cordova API.
>> Before
>> >>>>> we can move forward with cordova-js integration we really need to
>> figure
>> >>>>> that part of it out.
>> >>>>> - I will work rest of day in getting cordova-js into the apache git
>> repo
>> >>>>> and finishing up that work.
>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to
>> get
>> >>>>> iOS on track. Will have a better idea how that platform is looking
>> >>>>> tomorrow.
>> >>>>> - Bada 2.0 still needs a platform implementation before we can move
>> with
>> >>>>> cordova-js on it.
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> GOFG - Get On Fat Guy
>> >>>> http://www.gofg.at/ - powered by Cordova
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Gord Tanner
>> >>> Senior Developer / Code Poet
>> >>> tinyHippos Inc.
>> >>> @tinyhippos
>>
>
>
>
> --
> Gord Tanner
> Senior Developer / Code Poet
> tinyHippos Inc.
> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Stoked guys, thanks for all your hard work!

On 12-02-15 9:03 AM, "Gord Tanner" <go...@tinyhippos.com> wrote:

>OMFG!
>
>You just saved my day!
>
>I have been looking for why blackberry wasn't firing device ready and that
>bad module ID was it!  I was circling around the channel code attempting
>to
>figure out why it wasn't joining after the device and network channels
>were
>fired.
>
>Gonna look into this and pull it in, looks good at first glance.
>
>
>Gord
>
>On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com> wrote:
>
>> Ok, I've submitted a pull request with my changes.
>>
>> https://github.com/callback/callback-js/pull/17
>>
>> In my previous email, #3 was due to where I had inserted #2 (oops).
>> The changes are mostly phonegap -> cordova changes.  Additionally I
>> had to fix a module require in lib/platform/blackberry.js which was
>> specifying a bad module name.
>>
>> The only appearance of phonegap in common-js after my change is in the
>> iOS and WP7 plugins where they reference native code since I didn't
>> think those had been renamed yet.
>>
>> Eventually the BlackBerry native side should make use of require (as
>> shown in Fil's commit), but that will wait till common-js gets added
>> to apache source. For the time being a quick hack is to add the
>> following at the bottom of the generated js:
>>
>> var Cordova = require('cordova');
>>
>> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com>
>>wrote:
>> > So I've got callback-js "working" in my sandbox.  Haven't submitted
>> > pull request yet because I'm still debugging something.  Here's
>> > summary of changes I've made:
>> >
>> > 1. Modify rest of files to use "cordova" instead of "phonegap".
>> > 2. Added a global define of "Cordova" as a temporary hack since native
>> > PluginResult.toSuccessCallbackString expects it to exist.
>> > 3. For some reason I had to make sure the cordova/utils module exists
>> > in cordova.js before the cordova/channel module, otherwise I was
>> > getting an error that the module didn't exist.
>> >
>> > With the above changes I was able to run some simple tests (verified
>> > network works).  I'm currently looking at proper fix for #2 and #3.
>> >
>> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>> wrote:
>> >> I'm looking at https://github.com/callback/callback-js and I see a
>>lot
>> >> of references to "phonegap" in the lib/plugins directory though it
>> >> seems like things one directory up (lib) has been changed.  Am I not
>> >> looking at an up to date project or should I send a pull request with
>> >> that name change too?
>> >>
>> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>> wrote:
>> >>> I am on BlackBerry today.
>> >>>
>> >>> Currently showing:
>> >>> Error: SyntaxError: Unable to parse JSON string alert.
>> >>>
>> >>> I will attempt to get it up and running again today.
>> >>>
>> >>> I also have the start of a node runner for callback-js tests here:
>> >>> https://github.com/gtanner/callback-js
>> >>>
>> >>> Gord
>> >>>
>> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net>
>> wrote:
>> >>>
>> >>>> Can you please drop me a line once cordova-js is on the official
>> repos &
>> >>>> mirrored? I will then give integrating the new common-JS into
>> cordova-qt a
>> >>>> go!
>> >>>>
>> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>> >>>>
>> >>>>  Update on unified JavaScript work in cordova for today:
>> >>>>>
>> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>> which is a
>> >>>>> hurdle in making sure it supports the cross-platform cordova API.
>> Before
>> >>>>> we can move forward with cordova-js integration we really need to
>> figure
>> >>>>> that part of it out.
>> >>>>> - I will work rest of day in getting cordova-js into the apache
>>git
>> repo
>> >>>>> and finishing up that work.
>> >>>>> - BlackBerry still needs work and testing - Tim, you available?
>> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning
>>to
>> get
>> >>>>> iOS on track. Will have a better idea how that platform is looking
>> >>>>> tomorrow.
>> >>>>> - Bada 2.0 still needs a platform implementation before we can
>>move
>> with
>> >>>>> cordova-js on it.
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> GOFG - Get On Fat Guy
>> >>>> http://www.gofg.at/ - powered by Cordova
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Gord Tanner
>> >>> Senior Developer / Code Poet
>> >>> tinyHippos Inc.
>> >>> @tinyhippos
>>
>
>
>
>-- 
>Gord Tanner
>Senior Developer / Code Poet
>tinyHippos Inc.
>@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

OMFG!

You just saved my day!

I have been looking for why blackberry wasn't firing device ready and that
bad module ID was it!  I was circling around the channel code attempting to
figure out why it wasn't joining after the device and network channels were
fired.

Gonna look into this and pull it in, looks good at first glance.


Gord

On Wed, Feb 15, 2012 at 11:53 AM, Drew Walters <de...@gmail.com> wrote:

> Ok, I've submitted a pull request with my changes.
>
> https://github.com/callback/callback-js/pull/17
>
> In my previous email, #3 was due to where I had inserted #2 (oops).
> The changes are mostly phonegap -> cordova changes.  Additionally I
> had to fix a module require in lib/platform/blackberry.js which was
> specifying a bad module name.
>
> The only appearance of phonegap in common-js after my change is in the
> iOS and WP7 plugins where they reference native code since I didn't
> think those had been renamed yet.
>
> Eventually the BlackBerry native side should make use of require (as
> shown in Fil's commit), but that will wait till common-js gets added
> to apache source. For the time being a quick hack is to add the
> following at the bottom of the generated js:
>
> var Cordova = require('cordova');
>
> On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com> wrote:
> > So I've got callback-js "working" in my sandbox.  Haven't submitted
> > pull request yet because I'm still debugging something.  Here's
> > summary of changes I've made:
> >
> > 1. Modify rest of files to use "cordova" instead of "phonegap".
> > 2. Added a global define of "Cordova" as a temporary hack since native
> > PluginResult.toSuccessCallbackString expects it to exist.
> > 3. For some reason I had to make sure the cordova/utils module exists
> > in cordova.js before the cordova/channel module, otherwise I was
> > getting an error that the module didn't exist.
> >
> > With the above changes I was able to run some simple tests (verified
> > network works).  I'm currently looking at proper fix for #2 and #3.
> >
> > On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
> wrote:
> >> I'm looking at https://github.com/callback/callback-js and I see a lot
> >> of references to "phonegap" in the lib/plugins directory though it
> >> seems like things one directory up (lib) has been changed.  Am I not
> >> looking at an up to date project or should I send a pull request with
> >> that name change too?
> >>
> >> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
> wrote:
> >>> I am on BlackBerry today.
> >>>
> >>> Currently showing:
> >>> Error: SyntaxError: Unable to parse JSON string alert.
> >>>
> >>> I will attempt to get it up and running again today.
> >>>
> >>> I also have the start of a node runner for callback-js tests here:
> >>> https://github.com/gtanner/callback-js
> >>>
> >>> Gord
> >>>
> >>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net>
> wrote:
> >>>
> >>>> Can you please drop me a line once cordova-js is on the official
> repos &
> >>>> mirrored? I will then give integrating the new common-JS into
> cordova-qt a
> >>>> go!
> >>>>
> >>>> Am 2012-02-15 00:09, schrieb Filip Maj:
> >>>>
> >>>>  Update on unified JavaScript work in cordova for today:
> >>>>>
> >>>>> - looks like the WP7 implementation cannot run our mobile-spec,
> which is a
> >>>>> hurdle in making sure it supports the cross-platform cordova API.
> Before
> >>>>> we can move forward with cordova-js integration we really need to
> figure
> >>>>> that part of it out.
> >>>>> - I will work rest of day in getting cordova-js into the apache git
> repo
> >>>>> and finishing up that work.
> >>>>> - BlackBerry still needs work and testing - Tim, you available?
> >>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to
> get
> >>>>> iOS on track. Will have a better idea how that platform is looking
> >>>>> tomorrow.
> >>>>> - Bada 2.0 still needs a platform implementation before we can move
> with
> >>>>> cordova-js on it.
> >>>>>
> >>>>
> >>>> --
> >>>> GOFG - Get On Fat Guy
> >>>> http://www.gofg.at/ - powered by Cordova
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Gord Tanner
> >>> Senior Developer / Code Poet
> >>> tinyHippos Inc.
> >>> @tinyhippos
>



-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

If it's passing tests, let's add the new cordova.js file to the
incubator-cordova-blackberry-webworks repo and change over the native JS
calls to use require. Then we're done with BB! Tim should be helping out
with this too (as soon as he gets a physical device on hand). But I think
we're pretty much there, eh Drew?

On 12-02-15 8:53 AM, "Drew Walters" <de...@gmail.com> wrote:

>Ok, I've submitted a pull request with my changes.
>
>https://github.com/callback/callback-js/pull/17
>
>In my previous email, #3 was due to where I had inserted #2 (oops).
>The changes are mostly phonegap -> cordova changes.  Additionally I
>had to fix a module require in lib/platform/blackberry.js which was
>specifying a bad module name.
>
>The only appearance of phonegap in common-js after my change is in the
>iOS and WP7 plugins where they reference native code since I didn't
>think those had been renamed yet.
>
>Eventually the BlackBerry native side should make use of require (as
>shown in Fil's commit), but that will wait till common-js gets added
>to apache source. For the time being a quick hack is to add the
>following at the bottom of the generated js:
>
>var Cordova = require('cordova');
>
>On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com> wrote:
>> So I've got callback-js "working" in my sandbox.  Haven't submitted
>> pull request yet because I'm still debugging something.  Here's
>> summary of changes I've made:
>>
>> 1. Modify rest of files to use "cordova" instead of "phonegap".
>> 2. Added a global define of "Cordova" as a temporary hack since native
>> PluginResult.toSuccessCallbackString expects it to exist.
>> 3. For some reason I had to make sure the cordova/utils module exists
>> in cordova.js before the cordova/channel module, otherwise I was
>> getting an error that the module didn't exist.
>>
>> With the above changes I was able to run some simple tests (verified
>> network works).  I'm currently looking at proper fix for #2 and #3.
>>
>> On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com>
>>wrote:
>>> I'm looking at https://github.com/callback/callback-js and I see a lot
>>> of references to "phonegap" in the lib/plugins directory though it
>>> seems like things one directory up (lib) has been changed.  Am I not
>>> looking at an up to date project or should I send a pull request with
>>> that name change too?
>>>
>>> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>>>wrote:
>>>> I am on BlackBerry today.
>>>>
>>>> Currently showing:
>>>> Error: SyntaxError: Unable to parse JSON string alert.
>>>>
>>>> I will attempt to get it up and running again today.
>>>>
>>>> I also have the start of a node runner for callback-js tests here:
>>>> https://github.com/gtanner/callback-js
>>>>
>>>> Gord
>>>>
>>>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net>
>>>>wrote:
>>>>
>>>>> Can you please drop me a line once cordova-js is on the official
>>>>>repos &
>>>>> mirrored? I will then give integrating the new common-JS into
>>>>>cordova-qt a
>>>>> go!
>>>>>
>>>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>>>>
>>>>>  Update on unified JavaScript work in cordova for today:
>>>>>>
>>>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>>>>>>which is a
>>>>>> hurdle in making sure it supports the cross-platform cordova API.
>>>>>>Before
>>>>>> we can move forward with cordova-js integration we really need to
>>>>>>figure
>>>>>> that part of it out.
>>>>>> - I will work rest of day in getting cordova-js into the apache git
>>>>>>repo
>>>>>> and finishing up that work.
>>>>>> - BlackBerry still needs work and testing - Tim, you available?
>>>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning
>>>>>>to get
>>>>>> iOS on track. Will have a better idea how that platform is looking
>>>>>> tomorrow.
>>>>>> - Bada 2.0 still needs a platform implementation before we can move
>>>>>>with
>>>>>> cordova-js on it.
>>>>>>
>>>>>
>>>>> --
>>>>> GOFG - Get On Fat Guy
>>>>> http://www.gofg.at/ - powered by Cordova
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Gord Tanner
>>>> Senior Developer / Code Poet
>>>> tinyHippos Inc.
>>>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

Ok, I've submitted a pull request with my changes.

https://github.com/callback/callback-js/pull/17

In my previous email, #3 was due to where I had inserted #2 (oops).
The changes are mostly phonegap -> cordova changes.  Additionally I
had to fix a module require in lib/platform/blackberry.js which was
specifying a bad module name.

The only appearance of phonegap in common-js after my change is in the
iOS and WP7 plugins where they reference native code since I didn't
think those had been renamed yet.

Eventually the BlackBerry native side should make use of require (as
shown in Fil's commit), but that will wait till common-js gets added
to apache source. For the time being a quick hack is to add the
following at the bottom of the generated js:

var Cordova = require('cordova');

On Wed, Feb 15, 2012 at 9:23 AM, Drew Walters <de...@gmail.com> wrote:
> So I've got callback-js "working" in my sandbox.  Haven't submitted
> pull request yet because I'm still debugging something.  Here's
> summary of changes I've made:
>
> 1. Modify rest of files to use "cordova" instead of "phonegap".
> 2. Added a global define of "Cordova" as a temporary hack since native
> PluginResult.toSuccessCallbackString expects it to exist.
> 3. For some reason I had to make sure the cordova/utils module exists
> in cordova.js before the cordova/channel module, otherwise I was
> getting an error that the module didn't exist.
>
> With the above changes I was able to run some simple tests (verified
> network works).  I'm currently looking at proper fix for #2 and #3.
>
> On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com> wrote:
>> I'm looking at https://github.com/callback/callback-js and I see a lot
>> of references to "phonegap" in the lib/plugins directory though it
>> seems like things one directory up (lib) has been changed.  Am I not
>> looking at an up to date project or should I send a pull request with
>> that name change too?
>>
>> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com> wrote:
>>> I am on BlackBerry today.
>>>
>>> Currently showing:
>>> Error: SyntaxError: Unable to parse JSON string alert.
>>>
>>> I will attempt to get it up and running again today.
>>>
>>> I also have the start of a node runner for callback-js tests here:
>>> https://github.com/gtanner/callback-js
>>>
>>> Gord
>>>
>>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net> wrote:
>>>
>>>> Can you please drop me a line once cordova-js is on the official repos &
>>>> mirrored? I will then give integrating the new common-JS into cordova-qt a
>>>> go!
>>>>
>>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>>>
>>>>  Update on unified JavaScript work in cordova for today:
>>>>>
>>>>> - looks like the WP7 implementation cannot run our mobile-spec, which is a
>>>>> hurdle in making sure it supports the cross-platform cordova API. Before
>>>>> we can move forward with cordova-js integration we really need to figure
>>>>> that part of it out.
>>>>> - I will work rest of day in getting cordova-js into the apache git repo
>>>>> and finishing up that work.
>>>>> - BlackBerry still needs work and testing - Tim, you available?
>>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to get
>>>>> iOS on track. Will have a better idea how that platform is looking
>>>>> tomorrow.
>>>>> - Bada 2.0 still needs a platform implementation before we can move with
>>>>> cordova-js on it.
>>>>>
>>>>
>>>> --
>>>> GOFG - Get On Fat Guy
>>>> http://www.gofg.at/ - powered by Cordova
>>>>
>>>
>>>
>>>
>>> --
>>> Gord Tanner
>>> Senior Developer / Code Poet
>>> tinyHippos Inc.
>>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Hey guys,

I switched over about half of the module string Ids from phonegap over to
cordova last night but passed out before I could get to all of them :P

Drew, thanks for your efforts! For #2, see this commit:

https://github.com/filmaj/incubator-cordova-blackberry-webworks/commit/63ec
7bb7f2c8a5eced0b79465fc5af9a7c69f602


Of course you'll need to change the 'phonegap' strings to cordova but that
should get you most of the way there. The idea is you shouldn't have to
invoke any globals from native - just require() a module and off you go.

Interesting about #3... But switching the order should be fine. Looking
forward to your pull request once that is done!

On 12-02-15 7:23 AM, "Drew Walters" <de...@gmail.com> wrote:

>So I've got callback-js "working" in my sandbox.  Haven't submitted
>pull request yet because I'm still debugging something.  Here's
>summary of changes I've made:
>
>1. Modify rest of files to use "cordova" instead of "phonegap".
>2. Added a global define of "Cordova" as a temporary hack since native
>PluginResult.toSuccessCallbackString expects it to exist.
>3. For some reason I had to make sure the cordova/utils module exists
>in cordova.js before the cordova/channel module, otherwise I was
>getting an error that the module didn't exist.
>
>With the above changes I was able to run some simple tests (verified
>network works).  I'm currently looking at proper fix for #2 and #3.
>
>On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com> wrote:
>> I'm looking at https://github.com/callback/callback-js and I see a lot
>> of references to "phonegap" in the lib/plugins directory though it
>> seems like things one directory up (lib) has been changed.  Am I not
>> looking at an up to date project or should I send a pull request with
>> that name change too?
>>
>> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com>
>>wrote:
>>> I am on BlackBerry today.
>>>
>>> Currently showing:
>>> Error: SyntaxError: Unable to parse JSON string alert.
>>>
>>> I will attempt to get it up and running again today.
>>>
>>> I also have the start of a node runner for callback-js tests here:
>>> https://github.com/gtanner/callback-js
>>>
>>> Gord
>>>
>>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net>
>>>wrote:
>>>
>>>> Can you please drop me a line once cordova-js is on the official
>>>>repos &
>>>> mirrored? I will then give integrating the new common-JS into
>>>>cordova-qt a
>>>> go!
>>>>
>>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>>>
>>>>  Update on unified JavaScript work in cordova for today:
>>>>>
>>>>> - looks like the WP7 implementation cannot run our mobile-spec,
>>>>>which is a
>>>>> hurdle in making sure it supports the cross-platform cordova API.
>>>>>Before
>>>>> we can move forward with cordova-js integration we really need to
>>>>>figure
>>>>> that part of it out.
>>>>> - I will work rest of day in getting cordova-js into the apache git
>>>>>repo
>>>>> and finishing up that work.
>>>>> - BlackBerry still needs work and testing - Tim, you available?
>>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to
>>>>>get
>>>>> iOS on track. Will have a better idea how that platform is looking
>>>>> tomorrow.
>>>>> - Bada 2.0 still needs a platform implementation before we can move
>>>>>with
>>>>> cordova-js on it.
>>>>>
>>>>
>>>> --
>>>> GOFG - Get On Fat Guy
>>>> http://www.gofg.at/ - powered by Cordova
>>>>
>>>
>>>
>>>
>>> --
>>> Gord Tanner
>>> Senior Developer / Code Poet
>>> tinyHippos Inc.
>>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

So I've got callback-js "working" in my sandbox.  Haven't submitted
pull request yet because I'm still debugging something.  Here's
summary of changes I've made:

1. Modify rest of files to use "cordova" instead of "phonegap".
2. Added a global define of "Cordova" as a temporary hack since native
PluginResult.toSuccessCallbackString expects it to exist.
3. For some reason I had to make sure the cordova/utils module exists
in cordova.js before the cordova/channel module, otherwise I was
getting an error that the module didn't exist.

With the above changes I was able to run some simple tests (verified
network works).  I'm currently looking at proper fix for #2 and #3.

On Wed, Feb 15, 2012 at 8:21 AM, Drew Walters <de...@gmail.com> wrote:
> I'm looking at https://github.com/callback/callback-js and I see a lot
> of references to "phonegap" in the lib/plugins directory though it
> seems like things one directory up (lib) has been changed.  Am I not
> looking at an up to date project or should I send a pull request with
> that name change too?
>
> On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com> wrote:
>> I am on BlackBerry today.
>>
>> Currently showing:
>> Error: SyntaxError: Unable to parse JSON string alert.
>>
>> I will attempt to get it up and running again today.
>>
>> I also have the start of a node runner for callback-js tests here:
>> https://github.com/gtanner/callback-js
>>
>> Gord
>>
>> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net> wrote:
>>
>>> Can you please drop me a line once cordova-js is on the official repos &
>>> mirrored? I will then give integrating the new common-JS into cordova-qt a
>>> go!
>>>
>>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>>
>>>  Update on unified JavaScript work in cordova for today:
>>>>
>>>> - looks like the WP7 implementation cannot run our mobile-spec, which is a
>>>> hurdle in making sure it supports the cross-platform cordova API. Before
>>>> we can move forward with cordova-js integration we really need to figure
>>>> that part of it out.
>>>> - I will work rest of day in getting cordova-js into the apache git repo
>>>> and finishing up that work.
>>>> - BlackBerry still needs work and testing - Tim, you available?
>>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to get
>>>> iOS on track. Will have a better idea how that platform is looking
>>>> tomorrow.
>>>> - Bada 2.0 still needs a platform implementation before we can move with
>>>> cordova-js on it.
>>>>
>>>
>>> --
>>> GOFG - Get On Fat Guy
>>> http://www.gofg.at/ - powered by Cordova
>>>
>>
>>
>>
>> --
>> Gord Tanner
>> Senior Developer / Code Poet
>> tinyHippos Inc.
>> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Drew Walters <de...@gmail.com>]

I'm looking at https://github.com/callback/callback-js and I see a lot
of references to "phonegap" in the lib/plugins directory though it
seems like things one directory up (lib) has been changed.  Am I not
looking at an up to date project or should I send a pull request with
that name change too?

On Wed, Feb 15, 2012 at 8:17 AM, Gord Tanner <go...@tinyhippos.com> wrote:
> I am on BlackBerry today.
>
> Currently showing:
> Error: SyntaxError: Unable to parse JSON string alert.
>
> I will attempt to get it up and running again today.
>
> I also have the start of a node runner for callback-js tests here:
> https://github.com/gtanner/callback-js
>
> Gord
>
> On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net> wrote:
>
>> Can you please drop me a line once cordova-js is on the official repos &
>> mirrored? I will then give integrating the new common-JS into cordova-qt a
>> go!
>>
>> Am 2012-02-15 00:09, schrieb Filip Maj:
>>
>>  Update on unified JavaScript work in cordova for today:
>>>
>>> - looks like the WP7 implementation cannot run our mobile-spec, which is a
>>> hurdle in making sure it supports the cross-platform cordova API. Before
>>> we can move forward with cordova-js integration we really need to figure
>>> that part of it out.
>>> - I will work rest of day in getting cordova-js into the apache git repo
>>> and finishing up that work.
>>> - BlackBerry still needs work and testing - Tim, you available?
>>> - Shaz and I have a remote hack sesh planned for tomorrow morning to get
>>> iOS on track. Will have a better idea how that platform is looking
>>> tomorrow.
>>> - Bada 2.0 still needs a platform implementation before we can move with
>>> cordova-js on it.
>>>
>>
>> --
>> GOFG - Get On Fat Guy
>> http://www.gofg.at/ - powered by Cordova
>>
>
>
>
> --
> Gord Tanner
> Senior Developer / Code Poet
> tinyHippos Inc.
> @tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

I am on BlackBerry today.

Currently showing:
Error: SyntaxError: Unable to parse JSON string alert.

I will attempt to get it up and running again today.

I also have the start of a node runner for callback-js tests here:
https://github.com/gtanner/callback-js

Gord

On Wed, Feb 15, 2012 at 5:19 AM, Viras <vi...@users.sourceforge.net> wrote:

> Can you please drop me a line once cordova-js is on the official repos &
> mirrored? I will then give integrating the new common-JS into cordova-qt a
> go!
>
> Am 2012-02-15 00:09, schrieb Filip Maj:
>
>  Update on unified JavaScript work in cordova for today:
>>
>> - looks like the WP7 implementation cannot run our mobile-spec, which is a
>> hurdle in making sure it supports the cross-platform cordova API. Before
>> we can move forward with cordova-js integration we really need to figure
>> that part of it out.
>> - I will work rest of day in getting cordova-js into the apache git repo
>> and finishing up that work.
>> - BlackBerry still needs work and testing - Tim, you available?
>> - Shaz and I have a remote hack sesh planned for tomorrow morning to get
>> iOS on track. Will have a better idea how that platform is looking
>> tomorrow.
>> - Bada 2.0 still needs a platform implementation before we can move with
>> cordova-js on it.
>>
>
> --
> GOFG - Get On Fat Guy
> http://www.gofg.at/ - powered by Cordova
>



-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Viras <vi...@users.sourceforge.net>]

Can you please drop me a line once cordova-js is on the official repos 
& mirrored? I will then give integrating the new common-JS into 
cordova-qt a go!

Am 2012-02-15 00:09, schrieb Filip Maj:
> Update on unified JavaScript work in cordova for today:
>
> - looks like the WP7 implementation cannot run our mobile-spec, which 
> is a
> hurdle in making sure it supports the cross-platform cordova API. 
> Before
> we can move forward with cordova-js integration we really need to 
> figure
> that part of it out.
> - I will work rest of day in getting cordova-js into the apache git 
> repo
> and finishing up that work.
> - BlackBerry still needs work and testing - Tim, you available?
> - Shaz and I have a remote hack sesh planned for tomorrow morning to 
> get
> iOS on track. Will have a better idea how that platform is looking
> tomorrow.
> - Bada 2.0 still needs a platform implementation before we can move 
> with
> cordova-js on it.

-- 
GOFG - Get On Fat Guy
http://www.gofg.at/ - powered by Cordova

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Update on unified JavaScript work in cordova for today:

- looks like the WP7 implementation cannot run our mobile-spec, which is a
hurdle in making sure it supports the cross-platform cordova API. Before
we can move forward with cordova-js integration we really need to figure
that part of it out.
- I will work rest of day in getting cordova-js into the apache git repo
and finishing up that work.
- BlackBerry still needs work and testing - Tim, you available?
- Shaz and I have a remote hack sesh planned for tomorrow morning to get
iOS on track. Will have a better idea how that platform is looking
tomorrow.
- Bada 2.0 still needs a platform implementation before we can move with
cordova-js on it.

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Status update for everyone.

- Looks like Simon has done a good chunk of work to eliminate native cruft
on the Android implementation (moving stuff from native into JavaScript
where possible). Thank you Simon! It is working and complete on Android -
the first cordova platform to support cordova-js. That is awesome! Final
step: it would be awesome if one of the Android platform "owners"
(Joe/Simon) can take the unified-js branch of the native code from my fork
(https://github.com/filmaj/incubator-cordova-android/tree/unified-js),
rebase/merge as needed and run through the tests and make sure the latest
changes such as the PhoneGap->Cordova name change didn't mess anything up.
Then we can put the cordova-js seal of approval on Android :D
- I am working out the kinks with WP7+cordova-js (and node.js) integration
on Windows this week.
- Shaz is working out name change to cordova stuff on native ios. Shaz and
I have a remote hack session planned for mid-week to get the ball rolling
with cordova-js integration. I have a todo list of needed changes for ios
integration so hopefully that won't be too tough. I am going to try to get
it running on the sim on my dev machine before then anyways.
- The PhoneGap-to-Cordova name change on the BlackBerry implementation
seems to have messed up cordova-js working on that platform. I made a few
changes to get us back on track but it's still not working. Gord will take
a look when he can.
- Anis is setting up platform definitions for Bada (only v2.0? Both 1.0
and 2.0?) in cordova-js this week. Bada 1.0 vs. 2.0 will be separate
implementations anyways so we should treat them as separate platforms in
cordova-js. He still needs to iron out the native-to-JS bridge on Bada 2.0
though.
- Also need to work out the kinks on PlayBook. We are still missing File
API on PlayBook but we may be able to re-use BlackBerry Smartphone
WebWorks code for that (not sure still need to investigate).

What about webOS and Symbian? Are we gonna roll out cordova-js for those
platforms too? My intuition is no until those platforms require updates...

Re: Work Items for 1.5.0 - unified JS

[Brian LeRoux <b...@brian.io>]

+1 wiki time

(I will do the same w/ proj structuring)

On Fri, Feb 10, 2012 at 3:00 AM, Patrick Mueller <pm...@gmail.com> wrote:
> On Thu, Feb 9, 2012 at 21:52, Gord Tanner <go...@tinyhippos.com> wrote:
>
>> Here is a pull request with a AMD-lite (well really CommonJS light) module
>> manager:
>> https://github.com/callback/callback-js/pull/16
>
>
> Wow, that's tiny!  Partially because it's require() doesn't handle relative
> module id's.  :-)  We can add that back in; I like the idea of starting
> small and then adding on when we have to.
>
> We should probably pull in the CJS test cases - I have these floating
> around somewhere.  And I think there are AMD test cases, but ... not sure
> we really need them, since our "AMD" usage is pretty simplistic.
>
>
>> We can dump this guy anywhere (cordova.require seemed to be the winning
>> idea last I checked).
>>
>
> So, one thing I was thinking is that we may not actually want to keep a
> require() in a global object like cordova.  The problem is, that require()
> should only really be used from the "main" script.  Every module gets their
> own instance of a require() function, which is customized to their module's
> "path" (typically closed over a path variable - another fix needed for your
> require).
>
> If we have a "global" require hanging around, I have a feeling people may
> be tempted to use it.  Which would be wrong, if they're already in a module
> somewhere.
>
> I think it's time to create a page on the Wiki, go over some of the options
> w/r/t modules.
>
> --
> Patrick Mueller
> http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Thu, Feb 9, 2012 at 21:52, Gord Tanner <go...@tinyhippos.com> wrote:

> Here is a pull request with a AMD-lite (well really CommonJS light) module
> manager:
> https://github.com/callback/callback-js/pull/16


Wow, that's tiny!  Partially because it's require() doesn't handle relative
module id's.  :-)  We can add that back in; I like the idea of starting
small and then adding on when we have to.

We should probably pull in the CJS test cases - I have these floating
around somewhere.  And I think there are AMD test cases, but ... not sure
we really need them, since our "AMD" usage is pretty simplistic.


> We can dump this guy anywhere (cordova.require seemed to be the winning
> idea last I checked).
>

So, one thing I was thinking is that we may not actually want to keep a
require() in a global object like cordova.  The problem is, that require()
should only really be used from the "main" script.  Every module gets their
own instance of a require() function, which is customized to their module's
"path" (typically closed over a path variable - another fix needed for your
require).

If we have a "global" require hanging around, I have a feeling people may
be tempted to use it.  Which would be wrong, if they're already in a module
somewhere.

I think it's time to create a page on the Wiki, go over some of the options
w/r/t modules.

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Gord Tanner <go...@tinyhippos.com>]

Here is a pull request with a AMD-lite (well really CommonJS light) module
manager:
https://github.com/callback/callback-js/pull/16

We can dump this guy anywhere (cordova.require seemed to be the winning
idea last I checked).

This


On Thu, Feb 9, 2012 at 12:07 PM, Filip Maj <fi...@adobe.com> wrote:

> Three parts to this email. First:
>
> >[ Whole bunch of discussion]
> >
> >Perhaps it's time to define "AMD-lite" runtime somewhere?
>
> ^^ Pretty much.
>
> In my mind the simplest way to distill the discussion down is: do we want
> to employ almond or some other AMD+CJS-compliant loaders, and make it
> obvious to users that this comes with cordova, or roll our amdlite or smd
> or whatever you want to call it, a cut-down version tailored for our
> needs, and hide the fact we use it (closure that stuff up)?
>
> Second:
>
> One thing Mike and I chatted about today was the various platform
> definition files - there being a common one and various platform-specific
> ones, with both defining namespaces/globals that each will drop. It used a
> JSON convention that currently is something like:
>
>
> objects:{
>  PhoneGap:{
>    path:"lib/phonegap",
>    children:{
>      exec:{
>        path:"lib/phonegap/exec"
>      }
>    }
>  },
>  navigator:{
>    children:{
>      accelerometer:{
>        path: "lib/phonegap/plugin/accelerometer"
>      }
>    }
>  }
> }
>
> I believe Pat expressed some form of disgust when he saw that :) I agree
> it can certainly be better. One convention that could be employed is
> having a string value instead of an object if it's a module path alone (no
> children). Mike took it a different route and was thinking of something
> string-based like:
>
> {
>  "window.PhoneGap":"lib/phonegap",
>  "window.PhoneGap.exec":"lib/phonegap/exec"
> }
>
> Builder would need to be changed to accommodate the above, to sort the
> namespace strings and build up the necessary parent object if they don't
> exist, but both would work. Not sure if you recommended anything Pat but
> it's certainly open to discussion.
>
> Third:
>
> I really want to ship cordova-js for 1.5. There is a lot that can be
> improved, but I'm hoping that improvements can be slowly introduced over
> the next few releases. I am hoping that none of the issues that you
> brought up, Pat, are "show-stoppers".
>
> That's it from me.
>
>


-- 
Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.
@tinyhippos

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Thu, Feb 9, 2012 at 13:35, Jesse <pu...@gmail.com> wrote:

> Re: shipping date.
> I can say with almost absolute uncertainty that I alone will not get this
> into WP7 for 1.5 release at the end of the month.


To me, the important thing is making steps in the right direction; shipping
just some of the platforms as "built from cordova-js modules", and some of
the not, is perfectly fine to me: we made some headway.  It's not like the
cordova user community should be able to tell that their
phonegap.js/cordova.js was built from modules, at this point.

But certainly the more platforms, the better.

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Brian LeRoux <b...@brian.io>]

downloading windows 7 now... I haven't writ code for windows since 2000 was new!

*shudders*

On Thu, Feb 9, 2012 at 11:42 AM, Filip Maj <fi...@adobe.com> wrote:
> I'll do the same and work on a patch. I'll post links to patch source so
> we can collaborate on getting this done, Jesse/Gord. I'll aim for next
> week, and Jesse we can sync up in person.
>
> On 12-02-09 7:45 PM, "gtanner@gmail.com" <gt...@gmail.com> wrote:
>
>>I am setting up a windows dev environment.
>>
>>I was a c# dev in a past life so I can see if I can step up on wp7 too.
>>
>>
>>Sent on the TELUS Mobility network with BlackBerry
>>
>>-----Original Message-----
>>From: Jesse <pu...@gmail.com>
>>Date: Thu, 9 Feb 2012 10:35:15
>>To: <ca...@incubator.apache.org>
>>Reply-To: callback-dev@incubator.apache.org
>>Subject: Re: Work Items for 1.5.0 - unified JS
>>
>>Re: shipping date.
>>I can say with almost absolute uncertainty that I alone will not get this
>>into WP7 for 1.5 release at the end of the month.
>>
>>On Thu, Feb 9, 2012 at 9:48 AM, Patrick Mueller <pm...@gmail.com> wrote:
>>
>>> On Thu, Feb 9, 2012 at 12:07, Filip Maj <fi...@adobe.com> wrote:
>>>
>>> > Three parts to this email. First:
>>> >
>>> > >[ Whole bunch of discussion]
>>> > >
>>> > >Perhaps it's time to define "AMD-lite" runtime somewhere?
>>> >
>>> > ^^ Pretty much.
>>> >
>>> > In my mind the simplest way to distill the discussion down is: do we
>>>want
>>> > to employ almond or some other AMD+CJS-compliant loaders, and make it
>>> > obvious to users that this comes with cordova, or roll our amdlite or
>>>smd
>>> > or whatever you want to call it, a cut-down version tailored for our
>>> > needs, and hide the fact we use it (closure that stuff up)?
>>> >
>>>
>>> If we closure it up, we don't need to say anything about
>>>AMD/AMD-lite/SMD.
>>>  If we have a version that we don't closure up, we do neede to talk
>>>about
>>> the AMD-ish API.  Easiest path is to closure it up, I guess.  I might
>>>press
>>> for an option on the build script, which we wouldn't use for the
>>>production
>>> cordova.js, to allow for other options:
>>>
>>> - don't closure it up
>>> - don't closure it up, and don't prepend our AMD-ish runtime, allowing
>>> someone else to prepend theirs (eg, require.js, Dojo, etc)
>>>
>>>
>>> > Second:
>>> >
>>> > One thing Mike and I chatted about today was the various platform
>>> > definition files ... It used a
>>> > JSON convention that currently is something like:
>>> >
>>> > [[icky crap elided]]
>>> >
>>> > ... One convention that could be employed is
>>> > having a string value instead of an object if it's a module path alone
>>> (no
>>> > children). Mike took it a different route and was thinking of
>>>something
>>> > string-based like:
>>> >
>>> > {
>>> >  "window.PhoneGap":"lib/phonegap",
>>> >  "window.PhoneGap.exec":"lib/phonegap/exec"
>>> > }
>>> >
>>>
>>> This was the sort of thing I was thinking about.  Rather than object
>>> structures, we can use strings with path structures ("." or "/" or
>>>whatever
>>> delimited).
>>>
>>>
>>> > Third:
>>> >
>>> > I really want to ship cordova-js for 1.5. There is a lot that can be
>>> > improved, but I'm hoping that improvements can be slowly introduced
>>>over
>>> > the next few releases. I am hoping that none of the issues that you
>>> > brought up, Pat, are "show-stoppers".
>>> >
>>>
>>> +1 on shipping a "built from modules" cordova.js for 1.5.  Anyway we
>>>can do
>>> that.  It's a step in the right direction.  Some implementation choices
>>> imply (in my mind) show-stoppers, like shipping almond 0.3 - so we don't
>>> use those implementation choices.
>>>
>>> --
>>> Patrick Mueller
>>> http://muellerware.org
>>>
>>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

I'll do the same and work on a patch. I'll post links to patch source so
we can collaborate on getting this done, Jesse/Gord. I'll aim for next
week, and Jesse we can sync up in person.

On 12-02-09 7:45 PM, "gtanner@gmail.com" <gt...@gmail.com> wrote:

>I am setting up a windows dev environment.
>
>I was a c# dev in a past life so I can see if I can step up on wp7 too.
>
>
>Sent on the TELUS Mobility network with BlackBerry
>
>-----Original Message-----
>From: Jesse <pu...@gmail.com>
>Date: Thu, 9 Feb 2012 10:35:15
>To: <ca...@incubator.apache.org>
>Reply-To: callback-dev@incubator.apache.org
>Subject: Re: Work Items for 1.5.0 - unified JS
>
>Re: shipping date.
>I can say with almost absolute uncertainty that I alone will not get this
>into WP7 for 1.5 release at the end of the month.
>
>On Thu, Feb 9, 2012 at 9:48 AM, Patrick Mueller <pm...@gmail.com> wrote:
>
>> On Thu, Feb 9, 2012 at 12:07, Filip Maj <fi...@adobe.com> wrote:
>>
>> > Three parts to this email. First:
>> >
>> > >[ Whole bunch of discussion]
>> > >
>> > >Perhaps it's time to define "AMD-lite" runtime somewhere?
>> >
>> > ^^ Pretty much.
>> >
>> > In my mind the simplest way to distill the discussion down is: do we
>>want
>> > to employ almond or some other AMD+CJS-compliant loaders, and make it
>> > obvious to users that this comes with cordova, or roll our amdlite or
>>smd
>> > or whatever you want to call it, a cut-down version tailored for our
>> > needs, and hide the fact we use it (closure that stuff up)?
>> >
>>
>> If we closure it up, we don't need to say anything about
>>AMD/AMD-lite/SMD.
>>  If we have a version that we don't closure up, we do neede to talk
>>about
>> the AMD-ish API.  Easiest path is to closure it up, I guess.  I might
>>press
>> for an option on the build script, which we wouldn't use for the
>>production
>> cordova.js, to allow for other options:
>>
>> - don't closure it up
>> - don't closure it up, and don't prepend our AMD-ish runtime, allowing
>> someone else to prepend theirs (eg, require.js, Dojo, etc)
>>
>>
>> > Second:
>> >
>> > One thing Mike and I chatted about today was the various platform
>> > definition files ... It used a
>> > JSON convention that currently is something like:
>> >
>> > [[icky crap elided]]
>> >
>> > ... One convention that could be employed is
>> > having a string value instead of an object if it's a module path alone
>> (no
>> > children). Mike took it a different route and was thinking of
>>something
>> > string-based like:
>> >
>> > {
>> >  "window.PhoneGap":"lib/phonegap",
>> >  "window.PhoneGap.exec":"lib/phonegap/exec"
>> > }
>> >
>>
>> This was the sort of thing I was thinking about.  Rather than object
>> structures, we can use strings with path structures ("." or "/" or
>>whatever
>> delimited).
>>
>>
>> > Third:
>> >
>> > I really want to ship cordova-js for 1.5. There is a lot that can be
>> > improved, but I'm hoping that improvements can be slowly introduced
>>over
>> > the next few releases. I am hoping that none of the issues that you
>> > brought up, Pat, are "show-stoppers".
>> >
>>
>> +1 on shipping a "built from modules" cordova.js for 1.5.  Anyway we
>>can do
>> that.  It's a step in the right direction.  Some implementation choices
>> imply (in my mind) show-stoppers, like shipping almond 0.3 - so we don't
>> use those implementation choices.
>>
>> --
>> Patrick Mueller
>> http://muellerware.org
>>
>

Re: Work Items for 1.5.0 - unified JS

[gt...@gmail.com]

I am setting up a windows dev environment.

I was a c# dev in a past life so I can see if I can step up on wp7 too.


Sent on the TELUS Mobility network with BlackBerry

-----Original Message-----
From: Jesse <pu...@gmail.com>
Date: Thu, 9 Feb 2012 10:35:15 
To: <ca...@incubator.apache.org>
Reply-To: callback-dev@incubator.apache.org
Subject: Re: Work Items for 1.5.0 - unified JS

Re: shipping date.
I can say with almost absolute uncertainty that I alone will not get this
into WP7 for 1.5 release at the end of the month.

On Thu, Feb 9, 2012 at 9:48 AM, Patrick Mueller <pm...@gmail.com> wrote:

> On Thu, Feb 9, 2012 at 12:07, Filip Maj <fi...@adobe.com> wrote:
>
> > Three parts to this email. First:
> >
> > >[ Whole bunch of discussion]
> > >
> > >Perhaps it's time to define "AMD-lite" runtime somewhere?
> >
> > ^^ Pretty much.
> >
> > In my mind the simplest way to distill the discussion down is: do we want
> > to employ almond or some other AMD+CJS-compliant loaders, and make it
> > obvious to users that this comes with cordova, or roll our amdlite or smd
> > or whatever you want to call it, a cut-down version tailored for our
> > needs, and hide the fact we use it (closure that stuff up)?
> >
>
> If we closure it up, we don't need to say anything about AMD/AMD-lite/SMD.
>  If we have a version that we don't closure up, we do neede to talk about
> the AMD-ish API.  Easiest path is to closure it up, I guess.  I might press
> for an option on the build script, which we wouldn't use for the production
> cordova.js, to allow for other options:
>
> - don't closure it up
> - don't closure it up, and don't prepend our AMD-ish runtime, allowing
> someone else to prepend theirs (eg, require.js, Dojo, etc)
>
>
> > Second:
> >
> > One thing Mike and I chatted about today was the various platform
> > definition files ... It used a
> > JSON convention that currently is something like:
> >
> > [[icky crap elided]]
> >
> > ... One convention that could be employed is
> > having a string value instead of an object if it's a module path alone
> (no
> > children). Mike took it a different route and was thinking of something
> > string-based like:
> >
> > {
> >  "window.PhoneGap":"lib/phonegap",
> >  "window.PhoneGap.exec":"lib/phonegap/exec"
> > }
> >
>
> This was the sort of thing I was thinking about.  Rather than object
> structures, we can use strings with path structures ("." or "/" or whatever
> delimited).
>
>
> > Third:
> >
> > I really want to ship cordova-js for 1.5. There is a lot that can be
> > improved, but I'm hoping that improvements can be slowly introduced over
> > the next few releases. I am hoping that none of the issues that you
> > brought up, Pat, are "show-stoppers".
> >
>
> +1 on shipping a "built from modules" cordova.js for 1.5.  Anyway we can do
> that.  It's a step in the right direction.  Some implementation choices
> imply (in my mind) show-stoppers, like shipping almond 0.3 - so we don't
> use those implementation choices.
>
> --
> Patrick Mueller
> http://muellerware.org
>

Re: Work Items for 1.5.0 - unified JS

[Jesse <pu...@gmail.com>]

Re: shipping date.
I can say with almost absolute uncertainty that I alone will not get this
into WP7 for 1.5 release at the end of the month.

On Thu, Feb 9, 2012 at 9:48 AM, Patrick Mueller <pm...@gmail.com> wrote:

> On Thu, Feb 9, 2012 at 12:07, Filip Maj <fi...@adobe.com> wrote:
>
> > Three parts to this email. First:
> >
> > >[ Whole bunch of discussion]
> > >
> > >Perhaps it's time to define "AMD-lite" runtime somewhere?
> >
> > ^^ Pretty much.
> >
> > In my mind the simplest way to distill the discussion down is: do we want
> > to employ almond or some other AMD+CJS-compliant loaders, and make it
> > obvious to users that this comes with cordova, or roll our amdlite or smd
> > or whatever you want to call it, a cut-down version tailored for our
> > needs, and hide the fact we use it (closure that stuff up)?
> >
>
> If we closure it up, we don't need to say anything about AMD/AMD-lite/SMD.
>  If we have a version that we don't closure up, we do neede to talk about
> the AMD-ish API.  Easiest path is to closure it up, I guess.  I might press
> for an option on the build script, which we wouldn't use for the production
> cordova.js, to allow for other options:
>
> - don't closure it up
> - don't closure it up, and don't prepend our AMD-ish runtime, allowing
> someone else to prepend theirs (eg, require.js, Dojo, etc)
>
>
> > Second:
> >
> > One thing Mike and I chatted about today was the various platform
> > definition files ... It used a
> > JSON convention that currently is something like:
> >
> > [[icky crap elided]]
> >
> > ... One convention that could be employed is
> > having a string value instead of an object if it's a module path alone
> (no
> > children). Mike took it a different route and was thinking of something
> > string-based like:
> >
> > {
> >  "window.PhoneGap":"lib/phonegap",
> >  "window.PhoneGap.exec":"lib/phonegap/exec"
> > }
> >
>
> This was the sort of thing I was thinking about.  Rather than object
> structures, we can use strings with path structures ("." or "/" or whatever
> delimited).
>
>
> > Third:
> >
> > I really want to ship cordova-js for 1.5. There is a lot that can be
> > improved, but I'm hoping that improvements can be slowly introduced over
> > the next few releases. I am hoping that none of the issues that you
> > brought up, Pat, are "show-stoppers".
> >
>
> +1 on shipping a "built from modules" cordova.js for 1.5.  Anyway we can do
> that.  It's a step in the right direction.  Some implementation choices
> imply (in my mind) show-stoppers, like shipping almond 0.3 - so we don't
> use those implementation choices.
>
> --
> Patrick Mueller
> http://muellerware.org
>

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Thu, Feb 9, 2012 at 12:07, Filip Maj <fi...@adobe.com> wrote:

> Three parts to this email. First:
>
> >[ Whole bunch of discussion]
> >
> >Perhaps it's time to define "AMD-lite" runtime somewhere?
>
> ^^ Pretty much.
>
> In my mind the simplest way to distill the discussion down is: do we want
> to employ almond or some other AMD+CJS-compliant loaders, and make it
> obvious to users that this comes with cordova, or roll our amdlite or smd
> or whatever you want to call it, a cut-down version tailored for our
> needs, and hide the fact we use it (closure that stuff up)?
>

If we closure it up, we don't need to say anything about AMD/AMD-lite/SMD.
 If we have a version that we don't closure up, we do neede to talk about
the AMD-ish API.  Easiest path is to closure it up, I guess.  I might press
for an option on the build script, which we wouldn't use for the production
cordova.js, to allow for other options:

- don't closure it up
- don't closure it up, and don't prepend our AMD-ish runtime, allowing
someone else to prepend theirs (eg, require.js, Dojo, etc)


> Second:
>
> One thing Mike and I chatted about today was the various platform
> definition files ... It used a
> JSON convention that currently is something like:
>
> [[icky crap elided]]
>
> ... One convention that could be employed is
> having a string value instead of an object if it's a module path alone (no
> children). Mike took it a different route and was thinking of something
> string-based like:
>
> {
>  "window.PhoneGap":"lib/phonegap",
>  "window.PhoneGap.exec":"lib/phonegap/exec"
> }
>

This was the sort of thing I was thinking about.  Rather than object
structures, we can use strings with path structures ("." or "/" or whatever
delimited).


> Third:
>
> I really want to ship cordova-js for 1.5. There is a lot that can be
> improved, but I'm hoping that improvements can be slowly introduced over
> the next few releases. I am hoping that none of the issues that you
> brought up, Pat, are "show-stoppers".
>

+1 on shipping a "built from modules" cordova.js for 1.5.  Anyway we can do
that.  It's a step in the right direction.  Some implementation choices
imply (in my mind) show-stoppers, like shipping almond 0.3 - so we don't
use those implementation choices.

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Three parts to this email. First:

>[ Whole bunch of discussion]
> 
>Perhaps it's time to define "AMD-lite" runtime somewhere?

^^ Pretty much.

In my mind the simplest way to distill the discussion down is: do we want
to employ almond or some other AMD+CJS-compliant loaders, and make it
obvious to users that this comes with cordova, or roll our amdlite or smd
or whatever you want to call it, a cut-down version tailored for our
needs, and hide the fact we use it (closure that stuff up)?

Second:

One thing Mike and I chatted about today was the various platform
definition files - there being a common one and various platform-specific
ones, with both defining namespaces/globals that each will drop. It used a
JSON convention that currently is something like:


objects:{
  PhoneGap:{
    path:"lib/phonegap",
    children:{
      exec:{
        path:"lib/phonegap/exec"
      }
    }
  },
  navigator:{
    children:{
      accelerometer:{
        path: "lib/phonegap/plugin/accelerometer"
      }
    }
  }
}

I believe Pat expressed some form of disgust when he saw that :) I agree
it can certainly be better. One convention that could be employed is
having a string value instead of an object if it's a module path alone (no
children). Mike took it a different route and was thinking of something
string-based like:

{
  "window.PhoneGap":"lib/phonegap",
  "window.PhoneGap.exec":"lib/phonegap/exec"
}

Builder would need to be changed to accommodate the above, to sort the
namespace strings and build up the necessary parent object if they don't
exist, but both would work. Not sure if you recommended anything Pat but
it's certainly open to discussion.

Third:

I really want to ship cordova-js for 1.5. There is a lot that can be
improved, but I'm hoping that improvements can be slowly introduced over
the next few releases. I am hoping that none of the issues that you
brought up, Pat, are "show-stoppers".

That's it from me.

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Wed, Feb 8, 2012 at 14:34, James Burke <jr...@gmail.com> wrote:

> On Wed, Feb 8, 2012 at 6:53 AM, Patrick Mueller <pm...@gmail.com> wrote:
> > - almond currently doesn't throw exceptions when undefined modules are
> > require()'d.  This is a very bad thing.  There's currently a bug open on
> > this at GitHub [2], which you should chime in on, as James is for some
> > reason reticent about fixing it.
>
> The bug is still open. It will restrict the ways in with almond may be
> used, but I am open to narrowing that focus. So feedback in that bug
> is encouraged.
>

Let's move the bug conversation to the bug.  Currently, the code does not
"fail fast" like it does in other CJS environments, and that's a problem.
 Also, how do you distinguish a module that didn't load, from a module
which does `module.exports = null`, for instance.


> Node's require is not suitable for use in the browser, in particular
> the lack of a callback require really hurts, and loader plugins help
> deal with the async nature of resources loading in the browser.
>

Not a problem, because Cordova isn't a "browser".  A significant amount of
code that makes up the app must be available immediately; sometimes all of
it, as some platform owners are leery of allowing apps to download "live
code".   Being able to load a "wad" of - let's call them 'packages' - at
once - like a Dojo layer (my understanding of a dojo layer anyway) - is
something that some apps may want to (and be allowed to) do.  But that's
way different from loading individual modules in an async fashion.


> The ability to inline text templates via the text plugin in builds is
> really handy.
>

The ability load resources in a JavaScript program is great.  The current
AMD mechanism, using module id's which have cruft prefixed with them,
renders your modules unusable in node (without some kind of AMD
super-wrapper).  Resource loading either shouldn't require crufty prefixes
on the module name - require("./package.json") does "the right thing" (for
me, returns JSON.parse() of the contents) - or it should be done with a
different API: module.loadResource("./package.json").

Don't get me started on the "has" or "domReady" plugins!!!


> > * given the above, I'd prefer that we own our own AMD-lite runtime.
> >  Eventually, I'd like to have node's "node_modules" dynamic runtime
> module
> > look up as well ...
>
> I recently added an "npmrel" task to volo:
> https://github.com/volojs/volo/blob/master/volo/npmrel/doc.md


Looks like this is rewriting source code to massage the require() string
arguments in the source.  To me, that's a last-resort option.   Doesn't
work if someone dynamically generates their module names used with
require(), for instance.  Adding an additional path search up
"node_modules" subdirectories would work fine as well, since we have all
the modules available at runtime; I understand this is huge issue for async
module loading though.  Again, that's not a requirement for Cordova.


> Insert the standard disclaimer: not all node/npm code is suitable for
> use in the browser, you may need to contact the original code author
> for slight modifications, since they may not have intended browser
> usage.
>

ha!  I guess the standard disclaimer is required, we don't want people
thinking they can run express in their Cordova app, eh?  That is, until we
actually support it!  Zing!


> Unfortunately I have not looked at the latest cordova code, but I do
> plan on making cordova-based apps that use an AMD loader. In
> particular ones that can use an 'env' plugin to load the right
> adapters/plugins for android vs ios vs whatever. So I am happy to test
> out any solution that allows me to run my own AMD shim (or full
> loader) that at least allows for loader plugins.
>

Ya, I think I've already brought up the fact that IBM is certainly
interested in using Dojo w/Cordova, and it seems like the right approach is
to allow someone to provide an "AMD-lite" compatible runtime which would be
used instead of ours.  Compatible means it can do way more than our
AMD-lite impl.  So when you do that - indicate you are using require.js or
Dojo - you can of course use all your enhanced AMD stuff.  There are a
variety of ways to slice this problem - your help will be greatly
appreciated when it comes to figuring out how we make this happen.

Perhaps it's time to define "AMD-lite" runtime somewhere?  What do they
call these in Java - profiles?  (CLDC, MIDP, CDC, etc - it has happily been
too many years for me to remember).  The odd thing is this "AMD-lite"
doesn't provide ANY async semantics; it's really CJS +
define(fully-qualified-module-id, moduleFactoryFunction),  Isn't that what
node ended up supporting for a little while?  Why did they remove it?
 Perhaps we could provide a marker in case someone needs to know, at
runtime, they're using AMD-lite: setting define.amdlite =
{something-not-null} or define.amd.lite = {something-not-null}.  In any
case, I think calling this "AMD-lite" feels right to me.  Or maybe SMD -
synchronous module definition (kinda a different way of looking at CJS's
old "transport" specs).


> > * Has anyone thought about making all this work via npm (or equivalent)
> > somehow?  ...
>
> The aforementioned volo can install code from github, or any url that
> is to a tar.gz file, and allows setup of projects that have a certain
> build style via project templates on github. If the project implements
> a package.json 'amd' property, then any project dependencies added to
> it can be converted to the wrapped style.
>
> Just mentioning it as a tool that may help build up phonegap projects,
> at least for ones that want a particular style. volo also allows
> installing new 'commands' for it, so for example, you could come up
> with a set of phonegap specific commands for it. The other plus is
> that it is designed to be delivered as a single file -- someone could
> take it, bundle a set of different default commands and deliver that
> JS file for others to use that has built in phonegap-specific
> functionality.
>

Interesting; this veers into the whole "what is the 'cordova' command-line
program, and what does it do?" discussion.

I don't have much interest in getting modules' source files massaged, but I
suspect there's lots of other things common coding activities that could be
shared - calling compressors, file-collectors, AMD-wrappers, inliners, etc.
 I'll take a look at volo ...


> I get lost in the amount of bugmail for this project, so I end up not
> checking this list that often. Maybe I need to do better filters. But
> always feel free to ping me to look at a thread/repo if it would be
> helpful.
>

Will try to remember.  I appreciate your contributions.

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[James Burke <jr...@gmail.com>]

On Wed, Feb 8, 2012 at 6:53 AM, Patrick Mueller <pm...@gmail.com> wrote:
> * In general, I'm very happy with the current shape.  Which is: 1) our
> modules are authored in CJS style (no AMD wrapper) 2) an AMD wrapper is
> added at build time, where the relevant modules are concatenated into
> platform-specific all-in-one .js files.
>
> * currently almond [1] is being used as the AMD runtime.  Couple of
> problems with that:
>
> - almond currently doesn't throw exceptions when undefined modules are
> require()'d.  This is a very bad thing.  There's currently a bug open on
> this at GitHub [2], which you should chime in on, as James is for some
> reason reticent about fixing it.

The bug is still open. It will restrict the ways in with almond may be
used, but I am open to narrowing that focus. So feedback in that bug
is encouraged.

> - while almond supports both require(moduleName) and define(moduleId,
> moduleFactory), which are the two APIs we seem to be making use of, it also
> supports the overloaded async require() forms, as well as the define()
> forms that allow you to specify pre-reqs.  It also supports "plugins".  All
> of that "also" stuff, in my book, is not good, and I don't want to make it
> available to our users by default.  Nor do I want our code to make use of
> it.  Those "also"s are not supported in natively in node, for instance,
> making any module you write that depends on them, a module that will not
> run naturally in node.

Node's require is not suitable for use in the browser, in particular
the lack of a callback require really hurts, and loader plugins help
deal with the async nature of resources loading in the browser.The
ability to inline text templates via the text plugin in builds is
really handy.

That said, I'm supportive of what you say below about making your own
AMD-lite shim. It is good to have specific ones tailored to specific
design goals.

> * given the above, I'd prefer that we own our own AMD-lite runtime.
>  Eventually, I'd like to have node's "node_modules" dynamic runtime module
> look up as well, which I'm not sure we will be able to find in a
> minimalistic AMD-lite runtime.  weinre has been using modjewel [3] forever
> as 3rd party code, and it's being added directly to weinre in an upcoming
> commit [4].  Turns out I know the author, and although he's kind of a
> prick, I think I can convince him to add the node_modules lookup bit.  :-)

I recently added an "npmrel" task to volo:
https://github.com/volojs/volo/blob/master/volo/npmrel/doc.md

You can try it following the volo details here:
https://github.com/volojs/volo (use the master dist/volo.js)

The goal is to allow the consumption of an NPM-installed package that
has nested node_modules dependencies in an AMD loader. The end result
is that it should allow usage of that package in any basic AMD loader
or shim, like almond, without requiring some new configuration options
or loader logic.

So even if you make your own AMD-lite, perhaps the above command can
help massage any npm/node package into something that can be used
directly.

Insert the standard disclaimer: not all node/npm code is suitable for
use in the browser, you may need to contact the original code author
for slight modifications, since they may not have intended browser
usage. Also, npmrel is still very new. I'm sure it needs exposure to
more real world code, but I'm willing to do bug fixes for it.

> * "make the AMD runtime available to our users" - from the note above.
>  Turns out, we've exposed at least "requirejs", "require", and "define" in
> the platform-specific all-in-one files.  That's great and that's horrible.
>  I would love to offer our users an AMD-lite capability.  But for some
> folks, like folks using Dojo, this is probably going to be problematic.  I
> see three possible use cases: 1) expose our AMD-lite to folks 2) don't
> expose our AMD-lite, by just wrapping the existing platform-specific
> all-in-one .js files in another function wrapper 3) allow folks to supply
> their own AMD-lite compatible runtime, like requirejs or dojo.  Maybe the
> best thing to do is to is 1), and then provide a command-line mechanism for
> folks to wrapper it for 2), or use an alt-AMD-lite runtime 3).

Unfortunately I have not looked at the latest cordova code, but I do
plan on making cordova-based apps that use an AMD loader. In
particular ones that can use an 'env' plugin to load the right
adapters/plugins for android vs ios vs whatever. So I am happy to test
out any solution that allows me to run my own AMD shim (or full
loader) that at least allows for loader plugins.

> * Has anyone thought about making all this work via npm (or equivalent)
> somehow?  This would mean that every "top-level" Cordova component would
> actually be an npm package, with an associated package.json file.  I guess
> the story would be that you could "npm install foo" and "npm remove"
> packages all day long, and arrange to "rebuild" the platform=specific
> all-in-one .js file.  For me, I could imagine building my app as a set of
> packages as well (well, one "main" package), and treat Cordova components
> no differently than I treat underscore, backbone, etc (eg, as AMD-lite-able
> modules).  [[note: I'm not actually suggesting that we publish Cordova
> components at npmjs.org; just yet :-) ]]

The aforementioned volo can install code from github, or any url that
is to a tar.gz file, and allows setup of projects that have a certain
build style via project templates on github. If the project implements
a package.json 'amd' property, then any project dependencies added to
it can be converted to the wrapped style.

Just mentioning it as a tool that may help build up phonegap projects,
at least for ones that want a particular style. volo also allows
installing new 'commands' for it, so for example, you could come up
with a set of phonegap specific commands for it. The other plus is
that it is designed to be delivered as a single file -- someone could
take it, bundle a set of different default commands and deliver that
JS file for others to use that has built in phonegap-specific
functionality.

I get lost in the amount of bugmail for this project, so I end up not
checking this list that often. Maybe I need to do better filters. But
always feel free to ping me to look at a thread/repo if it would be
helpful.

James

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Tue, Feb 7, 2012 at 09:05, Filip Maj <fi...@adobe.com> wrote:

> The exact repo I'll be going over is located at ... blah blah blah
>

Perfect.

Some thoughts on module usage in callback-js.

* In general, I'm very happy with the current shape.  Which is: 1) our
modules are authored in CJS style (no AMD wrapper) 2) an AMD wrapper is
added at build time, where the relevant modules are concatenated into
platform-specific all-in-one .js files.

* currently almond [1] is being used as the AMD runtime.  Couple of
problems with that:

- almond currently doesn't throw exceptions when undefined modules are
require()'d.  This is a very bad thing.  There's currently a bug open on
this at GitHub [2], which you should chime in on, as James is for some
reason reticent about fixing it.

- while almond supports both require(moduleName) and define(moduleId,
moduleFactory), which are the two APIs we seem to be making use of, it also
supports the overloaded async require() forms, as well as the define()
forms that allow you to specify pre-reqs.  It also supports "plugins".  All
of that "also" stuff, in my book, is not good, and I don't want to make it
available to our users by default.  Nor do I want our code to make use of
it.  Those "also"s are not supported in natively in node, for instance,
making any module you write that depends on them, a module that will not
run naturally in node.

* given the above, I'd prefer that we own our own AMD-lite runtime.
 Eventually, I'd like to have node's "node_modules" dynamic runtime module
look up as well, which I'm not sure we will be able to find in a
minimalistic AMD-lite runtime.  weinre has been using modjewel [3] forever
as 3rd party code, and it's being added directly to weinre in an upcoming
commit [4].  Turns out I know the author, and although he's kind of a
prick, I think I can convince him to add the node_modules lookup bit.  :-)

* "make the AMD runtime available to our users" - from the note above.
 Turns out, we've exposed at least "requirejs", "require", and "define" in
the platform-specific all-in-one files.  That's great and that's horrible.
 I would love to offer our users an AMD-lite capability.  But for some
folks, like folks using Dojo, this is probably going to be problematic.  I
see three possible use cases: 1) expose our AMD-lite to folks 2) don't
expose our AMD-lite, by just wrapping the existing platform-specific
all-in-one .js files in another function wrapper 3) allow folks to supply
their own AMD-lite compatible runtime, like requirejs or dojo.  Maybe the
best thing to do is to is 1), and then provide a command-line mechanism for
folks to wrapper it for 2), or use an alt-AMD-lite runtime 3).

* not entirely clear to me whether we are intending that folks can use
require(someCordovaComponent) in their own code or not.  Presumably there
is some VERY close relationship between the things exposed via some path
through "window" and the module exports you get back from a
require(someCordovaComponent), and so this is "just" adding some
documentation, and then adding some test cases to ensure the same objects
are available both ways.

* Has anyone thought about making all this work via npm (or equivalent)
somehow?  This would mean that every "top-level" Cordova component would
actually be an npm package, with an associated package.json file.  I guess
the story would be that you could "npm install foo" and "npm remove"
packages all day long, and arrange to "rebuild" the platform=specific
all-in-one .js file.  For me, I could imagine building my app as a set of
packages as well (well, one "main" package), and treat Cordova components
no differently than I treat underscore, backbone, etc (eg, as AMD-lite-able
modules).  [[note: I'm not actually suggesting that we publish Cordova
components at npmjs.org; just yet :-) ]]

* we should provide debug versions of the all-in-one .js files - see [5]
for more info; Browserify is making use of the same technique (IIRC).

[1] https://github.com/jrburke/almond
[2] https://github.com/jrburke/almond/issues/8
[3] https://github.com/pmuellr/modjewel
[4]
https://github.com/pmuellr/incubator-cordova-weinre/blob/issue-83/weinre.web/modjewel.js
[5]
http://pmuellr.blogspot.com/2011/11/debugging-concatenated-javascript-files.html

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Good call Pat.

The exact repo I'll be going over is located at
https://github.com/callback/callback-js (still waiting on a git home at
Apache, INFRA ticket filed).

I've got a branch of the incubator-cordova-android repository with all
changes necessary to get cordova-js integrated into the android
implementation here:

https://github.com/filmaj/incubator-cordova-android/tree/unified-js

Using github's handy compare feature, you can compare it to the master
branch here:

https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
d-js


For the above "comparison" view, ignore most of the Media-related code.
Essentially we need to stop referencing JavaScript globals from native.
Examples of these sorts of changes:

- firing nativeready:
https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
d-js#L12L207
- firing pause/resume events from native:
https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
d-js#L15L850
- invoking callback success/error handlers for different APIS:
https://github.com/filmaj/incubator-cordova-android/compare/master...unifie
d-js#L17L103

Other important things to highlight in Cordova-JS:

- build/packager.js:
https://github.com/callback/callback-js/blob/master/build/packager.js -
this module handles reading and compiling the various .js files in the
cordova-js repo together into cordova.<platform>.js files. When you run
"jake" from the repo root, that invokes the "bundle" function from this
module.
- lib/platform: .js files in here define the global objects that will be
dropped once phonegap is ready to boot. Most are platform-specific
definitions and are quite small. There is one, called common.js, common to
all platforms, that is the biggest. Basically all the globla namespaces ->
JS module mappings are defined here.
- lib/phonegap.js: 
https://github.com/callback/callback-js/blob/master/lib/phonegap.js - does
the add/removeEventListener hijacking that is common to all platforms, and
exposes callbackSuccess/error handlers to native.
- lib/channel.js: 
https://github.com/callback/callback-js/blob/master/lib/channel.js - event
emitter/listener that we use for all phonegap events such as nativeReady,
deviceReady, etc.
- lib/bootstrap.js:
https://github.com/callback/callback-js/blob/master/lib/bootstrap.js -
"boot" function defined here is what initializes phonegap. It'll run
through the platform definitions (lib/platform) and drop the modules
referenced in there into the appropriate name spaces in JS.

That's more than enough for you guys to chew on I think :)

Let me know if there's anything else I can provide!

On 12-02-07 2:44 PM, "Patrick Mueller" <pm...@gmail.com> wrote:

>On Tue, Feb 7, 2012 at 04:17, Filip Maj <fi...@adobe.com> wrote:
>
>> Friendly reminder that I've set up the cordovajs show-n-tell for
>>TOMORROW
>> (Wednesday Feb 8th) for 9AM PST.
>>
>
>Great!
>
>Could you post some links to relevant projects floating out there in the
>ether?  I'd like to be able to see look over the code before the
>show-n-tell.
>
>-- 
>Patrick Mueller
>http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Patrick Mueller <pm...@gmail.com>]

On Tue, Feb 7, 2012 at 04:17, Filip Maj <fi...@adobe.com> wrote:

> Friendly reminder that I've set up the cordovajs show-n-tell for TOMORROW
> (Wednesday Feb 8th) for 9AM PST.
>

Great!

Could you post some links to relevant projects floating out there in the
ether?  I'd like to be able to see look over the code before the
show-n-tell.

-- 
Patrick Mueller
http://muellerware.org

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Hey all

Friendly reminder that I've set up the cordovajs show-n-tell for TOMORROW
(Wednesday Feb 8th) for 9AM PST.

This is just an overview / description of the project, how it is
structured, how we are employing requirejs to modularize all of our APIs,
and information of that sort. I will also go through the Android
implementation and show how to integrate the new JS into the current
Android implementation. My goal is to get platform owners/maintainers to:

1. Understand the structure of the project
2. Understand how to integrate into their platform
3. Understand how to help out and patch cordova-js for future

Of course answer any questions anyone may have.

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/08/2012 9:00AM PST
Duration:01:00
URL:http://my.adobeconnect.com/cordovajs/

Call-In Phone Numbers
----
Internal (to Adobe): 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-03 11:16 AM, "Filip Maj" <fi...@adobe.com> wrote:

>Ill be in Europe so anything after 9AM PST means I'll be doing it after
>6PM my time.. I would prefer not to commit to anything past 7PM.
>
>
>
>On 12-02-03 11:06 AM, "Becky Gibson" <gi...@gmail.com> wrote:
>
>>I can make it work if necessary but would prefer sometime other than noon
>>Eastern on Wednesday.
>>
>>-becky
>>
>>On Feb 3, 2012, at 1:46 PM, Filip Maj wrote:
>>
>>> Would something like 9AM PST for Weds 2/8 work?
>>> 
>>> On 12-02-02 2:38 PM, "Bryce Curtis" <cu...@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 <fi...@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" <cu...@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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>>>>>>>>>> <st...@gmail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> +1 on connect session
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>>>>>>>>>>>>>>>> *   BlackBerry, I have the same thing going on but it
>>>>> is
>>>>>>> at
>>>>>>>>>> about
>>>>>>>>>>>>>>>> 80%:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>> 
>>>>> 
>>>>>https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/u
>>>>>n
>>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>> 
>>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

Ill be in Europe so anything after 9AM PST means I'll be doing it after
6PM my time.. I would prefer not to commit to anything past 7PM.



On 12-02-03 11:06 AM, "Becky Gibson" <gi...@gmail.com> wrote:

>I can make it work if necessary but would prefer sometime other than noon
>Eastern on Wednesday.
>
>-becky
>
>On Feb 3, 2012, at 1:46 PM, Filip Maj wrote:
>
>> Would something like 9AM PST for Weds 2/8 work?
>> 
>> On 12-02-02 2:38 PM, "Bryce Curtis" <cu...@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 <fi...@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" <cu...@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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>>>>>>>>> <st...@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> +1 on connect session
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>>>>>>>>>>>>>>> 
>>>>>>>>> 
>>>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>>>>>>>>>>>>>>> *   BlackBerry, I have the same thing going on but it
>>>> is
>>>>>> at
>>>>>>>>> about
>>>>>>>>>>>>>>> 80%:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>> 
>>>>>> 
>>>> 
>>>>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.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>> 
>

Re: Work Items for 1.5.0 - unified JS

[Becky Gibson <gi...@gmail.com>]

I can make it work if necessary but would prefer sometime other than noon Eastern on Wednesday.

-becky

On Feb 3, 2012, at 1:46 PM, Filip Maj wrote:

> Would something like 9AM PST for Weds 2/8 work?
> 
> On 12-02-02 2:38 PM, "Bryce Curtis" <cu...@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 <fi...@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" <cu...@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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>>>>>>>> <st...@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> +1 on connect session
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>>>>>>>>>>>>>> 
>>>>>>>> 
>>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>>>>>>>>>>>>>> *   BlackBerry, I have the same thing going on but it
>>> is
>>>>> at
>>>>>>>> about
>>>>>>>>>>>>>> 80%:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>> 
>>>>> 
>>> 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.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
> 

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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

On 12-02-02 2:38 PM, "Bryce Curtis" <cu...@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 <fi...@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" <cu...@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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>> >> >>><st...@gmail.com>
>> >> >>> >>>>>wrote:
>> >> >>> >>>>>
>> >> >>> >>>>>> +1 on connect session
>> >> >>> >>>>>>
>> >> >>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>> >> >>> >>>>>> >
>> >> >>> 
>>https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >> >>> >>>>>> >  *   BlackBerry, I have the same thing going on but it
>>is
>> >>at
>> >> >>>about
>> >> >>> >>>>>>80%:
>> >> >>> >>>>>> >
>> >> >>> >>>>>>
>> >> >>> >>>>>>
>> >> >>>
>> >> 
>>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.
>> >> >>> >>>>>> >
>> >> >>> >>>>>>
>> >> >>> >>>>
>> >> >>> >>
>> >> >>>
>> >> >
>> >>
>> >>
>>
>>

Re: Work Items for 1.5.0 - unified JS

[Bryce Curtis <cu...@gmail.com>]

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 <fi...@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" <cu...@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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
> >> >>><st...@gmail.com>
> >> >>> >>>>>wrote:
> >> >>> >>>>>
> >> >>> >>>>>> +1 on connect session
> >> >>> >>>>>>
> >> >>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
> >> >>> >>>>>> >
> >> >>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >> >>> >>>>>> >  *   BlackBerry, I have the same thing going on but it is
> >>at
> >> >>>about
> >> >>> >>>>>>80%:
> >> >>> >>>>>> >
> >> >>> >>>>>>
> >> >>> >>>>>>
> >> >>>
> >> 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.
> >> >>> >>>>>> >
> >> >>> >>>>>>
> >> >>> >>>>
> >> >>> >>
> >> >>>
> >> >
> >>
> >>
>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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" <cu...@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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>> >>><st...@gmail.com>
>> >>> >>>>>wrote:
>> >>> >>>>>
>> >>> >>>>>> +1 on connect session
>> >>> >>>>>>
>> >>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>> >>> >>>>>> >
>> >>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >>> >>>>>> >  *   BlackBerry, I have the same thing going on but it is
>>at
>> >>>about
>> >>> >>>>>>80%:
>> >>> >>>>>> >
>> >>> >>>>>>
>> >>> >>>>>>
>> >>>
>> 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.
>> >>> >>>>>> >
>> >>> >>>>>>
>> >>> >>>>
>> >>> >>
>> >>>
>> >
>>
>>

Re: Work Items for 1.5.0 - unified JS

[Bryce Curtis <cu...@gmail.com>]

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 <fi...@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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
> >>><st...@gmail.com>
> >>> >>>>>wrote:
> >>> >>>>>
> >>> >>>>>> +1 on connect session
> >>> >>>>>>
> >>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
> >>> >>>>>> >
> >>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >>> >>>>>> >  *   BlackBerry, I have the same thing going on but it is at
> >>>about
> >>> >>>>>>80%:
> >>> >>>>>> >
> >>> >>>>>>
> >>> >>>>>>
> >>>
> 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.
> >>> >>>>>> >
> >>> >>>>>>
> >>> >>>>
> >>> >>
> >>>
> >
>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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" <fi...@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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>>><st...@gmail.com>
>>> >>>>>wrote:
>>> >>>>>
>>> >>>>>> +1 on connect session
>>> >>>>>>
>>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>> >>>>>> >
>>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>> >>>>>> >  *   BlackBerry, I have the same thing going on but it is at
>>>about
>>> >>>>>>80%:
>>> >>>>>> >
>>> >>>>>>
>>> >>>>>>
>>> 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.
>>> >>>>>> >
>>> >>>>>>
>>> >>>>
>>> >>
>>>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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" <cu...@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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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
>><st...@gmail.com>
>> >>>>>wrote:
>> >>>>>
>> >>>>>> +1 on connect session
>> >>>>>>
>> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>> >>>>>> >
>> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >>>>>> >  *   BlackBerry, I have the same thing going on but it is at
>>about
>> >>>>>>80%:
>> >>>>>> >
>> >>>>>>
>> >>>>>>
>> 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.
>> >>>>>> >
>> >>>>>>
>> >>>>
>> >>
>>

Re: Work Items for 1.5.0 - unified JS

[Bryce Curtis <cu...@gmail.com>]

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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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 <st...@gmail.com>
> >>>>>wrote:
> >>>>>
> >>>>>> +1 on connect session
> >>>>>>
> >>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
> >>>>>> >
> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >>>>>> >  *   BlackBerry, I have the same thing going on but it is at about
> >>>>>>80%:
> >>>>>> >
> >>>>>>
> >>>>>>
> 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.
> >>>>>> >
> >>>>>>
> >>>>
> >>
>

Re: Work Items for 1.5.0 - unified JS

[Brian LeRoux <b...@brian.io>]

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 <sh...@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 <fi...@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" <sh...@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 <fi...@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" <cu...@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 <st...@gmail.com>
>>>>>wrote:
>>>>>
>>>>>> +1 on connect session
>>>>>>
>>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>>>>> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>>>>> >  *   BlackBerry, I have the same thing going on but it is at about
>>>>>>80%:
>>>>>> >
>>>>>>
>>>>>>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.
>>>>>> >
>>>>>>
>>>>
>>

Re: Work Items for 1.5.0 - unified JS

[Shazron <sh...@gmail.com>]

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 <fi...@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" <sh...@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 <fi...@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" <cu...@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 <st...@gmail.com>
>>>>wrote:
>>>>
>>>>> +1 on connect session
>>>>>
>>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>>>> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>>>> >  *   BlackBerry, I have the same thing going on but it is at about
>>>>>80%:
>>>>> >
>>>>>
>>>>>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.
>>>>> >
>>>>>
>>>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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" <sh...@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 <fi...@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" <cu...@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 <st...@gmail.com>
>>>wrote:
>>>
>>>> +1 on connect session
>>>>
>>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>>> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>>> >  *   BlackBerry, I have the same thing going on but it is at about
>>>>80%:
>>>> >
>>>>
>>>>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.
>>>> >
>>>>
>>

Re: Work Items for 1.5.0 - unified JS

[Shazron <sh...@gmail.com>]

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 <fi...@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" <cu...@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 <st...@gmail.com>
>>wrote:
>>
>>> +1 on connect session
>>>
>>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>>> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>>> >  *   BlackBerry, I have the same thing going on but it is at about
>>>80%:
>>> >
>>>
>>>https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/unif
>>>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.
>>> >
>>>
>

Re: Work Items for 1.5.0 - unified JS

[Filip Maj <fi...@adobe.com>]

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" <cu...@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 <st...@gmail.com>
>wrote:
>
>> +1 on connect session
>>
>> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
>> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>> >  *   BlackBerry, I have the same thing going on but it is at about
>>80%:
>> >
>> 
>>https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/unif
>>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.
>> >
>>

Re: Work Items for 1.5.0 - unified JS

[Bryce Curtis <cu...@gmail.com>]

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 <st...@gmail.com> wrote:

> +1 on connect session
>
> On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
> > https://github.com/filmaj/incubator-cordova-android/tree/unified-js
> >  *   BlackBerry, I have the same thing going on but it is at about 80%:
> >
> https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/unified-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.
> >
>

Re: Work Items for 1.5.0 - unified JS

[Steven Gill <st...@gmail.com>]

+1 on connect session

On Wed, Feb 1, 2012 at 2:21 PM, Filip Maj <fi...@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:
> https://github.com/filmaj/incubator-cordova-android/tree/unified-js
>  *   BlackBerry, I have the same thing going on but it is at about 80%:
> https://github.com/filmaj/incubator-cordova-blackberry-webworks/tree/unified-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.
>