Re: CEF & Cordova?
Ripple is fine for development. Not so much for office users. On Fri, Feb 8, 2013 at 7:26 PM, Gord Tanner wrote: > You can always use Ripple. > > Github.com/blackberry/ripple-ui > > Install it via npm: > > Npm install ripple -g > From developer.blackberry.com > Or > From the chrome App Store > > Sent from my iPhone > > On 2013-02-08, at 4:16 PM, David Lewis wrote: > >> Yes. Specifically Windows 7 as Win8 isn't even being talked about. >> >> http://code.google.com/p/chromiumembedded/ >> >> The cefclient looks to be a might more reasonable to work with than >> actual webkit. I've tweaked it to load locally and display as kiosk. >> Just need to wrap my head around exec(). >> >> On Fri, Feb 8, 2013 at 4:08 PM, Kerri Shotts wrote: >>> Wait -- are you asking if there's a desktop version of Phonegap? I was >>> assuming you meant a Chrome-based render for mobile devices, esp. since the >>> webkit on some mobile devices is quite borked. (Android 2.x, I'm looking at >>> you.) >>> >>> >>> >>> ___ >>> Kerri Shotts >>> photoKandy Studios, LLC >>> >>> On the Web: http://www.photokandy.com/ >>> >>> Social Media: >>> Twitter: @photokandy, http://twitter.com/photokandy >>> Tumblr: http://photokandy.tumblr.com/ >>> Github: https://github.com/kerrishotts >>>https://github.com/organizations/photokandyStudios >>> CoderWall: https://coderwall.com/kerrishotts >>> >>> Apps on the Apple Store: >>> >>> https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 >>> >>> >>> On Friday, February 8, 2013 at 2:57 PM, David Lewis wrote: >>> That's unfortunate. My team is working on webkit specific apps just because so many mobile devices use it; iOS, Android, and Blackberry 7+. Having a desktop webkit container would alleviate a lot of work forking Windows specific versions. I need to get it done anyway, I just thought I'd ask. The closest I've found is DesktopGap but it has less PG support than the current Win7 container. On Fri, Feb 8, 2013 at 3:27 PM, Kerri Shotts >>> (mailto:kerrisho...@gmail.com)> wrote: > Most modern platform's internal browsers are based on webkit -- iPhone > and Android, etc. Windows Phone (and the upcoming Firefox OS) would be > exceptions to the rule. > > I know there's been work done on supporting PG with Chrome as the > renderer, but don't hold your breath for it; a lot of stuff would have to > be rewritten. > ___ > Kerri Shotts > photoKandy Studios, LLC > > On the Web: http://www.photokandy.com/ > > Social Media: > Twitter: @photokandy, http://twitter.com/photokandy > Tumblr: http://photokandy.tumblr.com/ > Github: https://github.com/kerrishotts > https://github.com/organizations/photokandyStudios > CoderWall: https://coderwall.com/kerrishotts > > Apps on the Apple Store: > https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 > > > On Friday, February 8, 2013 at 1:33 PM, David Lewis wrote: > >> My project requires a webkit browser. Does anyone have experience >> adding Cordova support to Chromium Embedded Framework? >>> >>>
Re: CEF & Cordova?
You can always use Ripple. Github.com/blackberry/ripple-ui Install it via npm: Npm install ripple -g From developer.blackberry.com Or From the chrome App Store Sent from my iPhone On 2013-02-08, at 4:16 PM, David Lewis wrote: > Yes. Specifically Windows 7 as Win8 isn't even being talked about. > > http://code.google.com/p/chromiumembedded/ > > The cefclient looks to be a might more reasonable to work with than > actual webkit. I've tweaked it to load locally and display as kiosk. > Just need to wrap my head around exec(). > > On Fri, Feb 8, 2013 at 4:08 PM, Kerri Shotts wrote: >> Wait -- are you asking if there's a desktop version of Phonegap? I was >> assuming you meant a Chrome-based render for mobile devices, esp. since the >> webkit on some mobile devices is quite borked. (Android 2.x, I'm looking at >> you.) >> >> >> >> ___ >> Kerri Shotts >> photoKandy Studios, LLC >> >> On the Web: http://www.photokandy.com/ >> >> Social Media: >> Twitter: @photokandy, http://twitter.com/photokandy >> Tumblr: http://photokandy.tumblr.com/ >> Github: https://github.com/kerrishotts >>https://github.com/organizations/photokandyStudios >> CoderWall: https://coderwall.com/kerrishotts >> >> Apps on the Apple Store: >> >> https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 >> >> >> On Friday, February 8, 2013 at 2:57 PM, David Lewis wrote: >> >>> That's unfortunate. My team is working on webkit specific apps just >>> because so many mobile devices use it; iOS, Android, and Blackberry >>> 7+. Having a desktop webkit container would alleviate a lot of work >>> forking Windows specific versions. I need to get it done anyway, I >>> just thought I'd ask. The closest I've found is DesktopGap but it has >>> less PG support than the current Win7 container. >>> >>> On Fri, Feb 8, 2013 at 3:27 PM, Kerri Shotts >> (mailto:kerrisho...@gmail.com)> wrote: Most modern platform's internal browsers are based on webkit -- iPhone and Android, etc. Windows Phone (and the upcoming Firefox OS) would be exceptions to the rule. I know there's been work done on supporting PG with Chrome as the renderer, but don't hold your breath for it; a lot of stuff would have to be rewritten. ___ Kerri Shotts photoKandy Studios, LLC On the Web: http://www.photokandy.com/ Social Media: Twitter: @photokandy, http://twitter.com/photokandy Tumblr: http://photokandy.tumblr.com/ Github: https://github.com/kerrishotts https://github.com/organizations/photokandyStudios CoderWall: https://coderwall.com/kerrishotts Apps on the Apple Store: https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 On Friday, February 8, 2013 at 1:33 PM, David Lewis wrote: > My project requires a webkit browser. Does anyone have experience > adding Cordova support to Chromium Embedded Framework? >> >>
Re: Cordova-js debug files
Actually, interesting note on iOS 6 debugging - it's impossible to test 'normal' initialization, because you don't get the opportunity to debug a web app until it comes up, and it's already been initialized. If we want to support debugging initialization code, we could consider delaying the initialization dance, allowing a web app to initialize when it wants to. You could then launch your app - none of the Cordova code would be initialized (deviceReady not sent), then launch the debugger, then somehow tell Cordova to start up and debug it. Maybe Apple will fix this, but I'm not wagering any money on it. On Fri, Feb 8, 2013 at 6:21 PM, Filip Maj wrote: > For initialization debugging methinks > > On 2/8/13 3:13 PM, "Jesse" wrote: > > >Can someone explain the use/purpose of the generated > >pkg/debug/cordova.***-debug.js ? > >JSHint reports they are just large collections of bad-escapements ... are > >these still used for something? > > > >-- > >@purplecabbage > >risingj.com > > -- Patrick Mueller http://muellerware.org
Re: Cordova-js debug files
>JSHint reports ... I created these way back when. The idea is to create debuggable cat'd files, using the typical eval() with //@sourceURL hack, so you can see the individual files in the debugger. This didn't make much sense until iOS 6, on actual devices (but worked with desktops, most of the time). I believe I've tested these on iOS 6, so you load the big wad cordova.js, but see individual files in the debugger. Neat. But not sure it's worth it. Perhaps comment out the bits in the build, so we don't build them, but we know how to later if we need to. On Fri, Feb 8, 2013 at 6:21 PM, Filip Maj wrote: > For initialization debugging methinks > > On 2/8/13 3:13 PM, "Jesse" wrote: > > >Can someone explain the use/purpose of the generated > >pkg/debug/cordova.***-debug.js ? > >JSHint reports they are just large collections of bad-escapements ... are > >these still used for something? > > > >-- > >@purplecabbage > >risingj.com > > -- Patrick Mueller http://muellerware.org
Re: Cordova-js debug files
For initialization debugging methinks On 2/8/13 3:13 PM, "Jesse" wrote: >Can someone explain the use/purpose of the generated >pkg/debug/cordova.***-debug.js ? >JSHint reports they are just large collections of bad-escapements ... are >these still used for something? > >-- >@purplecabbage >risingj.com
Re: [iOS] Call for testing
I ran a few updates and made the error output a bit verbose. Shout out to
Tommy Carlos-Williams for his patience walking through the process with me
on IRC.
Conclusion: the xcodebuild -version command would exit with code 1 because
the Terms of Use were not accepted at a global level. This ended up being
reported:
You have not agreed to the Xcode license agreements, please run
'xcodebuild -license' (for user-level acceptance) or 'sudo xcodebuild
-license' (for system-wide acceptance) from within a Terminal window to
review and agree to the Xcode license agreements.
I've updated the code and pushed 2.4.6 to npm, so Becky maybe give that a
shot and see if you get similar output to the above. If you are installing
globally and need to sudo to install, you'll need to sudo to accept the
xcodebuild license as well.
On 2/8/13 1:59 PM, "Andrew Grieve" wrote:
>maybe xcodebuild -version is different when run with sudo?
>
>
>On Fri, Feb 8, 2013 at 4:45 PM, Filip Maj wrote:
>
>> Cool, thanks for checking it out Becky.
>>
>> That is exactly where some users are reporting their issues.
>>
>> Funny thing is, cordova-cli only runs "xcodebuild -version" to determine
>> if Xcode is installed or not. As long as the xcodebuild executable is in
>> your PATH it *should* work. I don't see how Xcode-select factors in here
>> though. Any ideas? Is my approach of checking iOS min reqs by shelling
>>out
>> to xcodebuild too naïve?
>>
>> On 2/8/13 1:38 PM, "Becky Gibson" wrote:
>>
>> >Interesting. I ran this once and it worked (I had to use sudo).
>>Then, I
>> >realized that I might have my xcode-selects variable set wrong since I
>> >recently downloaded Xcode 4.6 via the iOS downloads page rather than
>>via
>> >the AppStore. I put Xcode 4.6 into a subdirectory:
>> > /Applications/Xcode46/Xcode.app rather than right in the Applications
>> >folder. I realized that I should have also updated my xcode-select
>> >variable. I did that:
>> > sudo /usr/bin/xcode-select -switch
>> >/Applications/Xcode46/Xcode.app/Contents/Developer
>> >Then when I run sudo npm install -g cordova again, iOS fails:
>> > WARNING: Your system does not meet requirements to create
>>iosprojects.
>> >See error output below.
>> >Xcode is not installed. Cannot add iOS platform.
>> >SKIPPING ios bootstrap.
>> >
>> >So, I would guess it has to do with the xcode-selects value.
>> >
>> >Also, FWIW running the suggested sudo chown -R
>> >/usr/local/lib/node_modules/cordova command and it didn't work for
>>me. I
>> >haven't investigate that yet.
>> >
>> >-becky
>> >
>> >
>> >On Fri, Feb 8, 2013 at 3:59 PM, Filip Maj wrote:
>> >
>> >> Hey everyone,
>> >>
>> >> I've had a couple of reports of people using the cordova-cli tools
>>and
>> >> having issues installing. Apparently the post-install script
>> >>("bootstrap")
>> >> complains that Xcode is not installed on the system. Both users were
>> >> running Xcode 4.6.
>> >>
>> >> I've since upgraded my Xcode and done both a fresh install as well
>>as an
>> >> upgrade from old cli tools to new, and cannot reproduce (the
>>bootstrap
>> >> works; I get "SUCCESS: min reqs for iOS met").
>> >>
>> >> Could other contributors on the ML here, who have Xcode at least
>>4.5.2
>> >> installed, give it a shot and see if the installation goes through?
>> >>
>> >> To install, have node installed and run: npm install -g cordova
>> >> (you may need to put sudo in front of that if your node is installed
>> >> globally)
>> >>
>> >> Near the end of the installation process you should see something
>>like:
>> >>
>> >> > cordova@2.4.4 install /usr/local/lib/node_modules/cordova
>> >> > node bootstrap.js && ./bin/notice
>> >>
>> >> SUCCESS: Minimum requirements for blackberry met.
>> >> BOOTSTRAPPING blackberry...
>> >> SUCCESS: Minimum requirements for ios met.
>> >> BOOTSTRAPPING ios...
>> >> SUCCESS: ios ready to rock!
>> >> SUCCESS: blackberry ready to rock!
>> >> SUCCESS: Minimum requirements for android met.
>> >> BOOTSTRAPPING android...
>> >> SUCCESS: android ready to rock!
>> >>
>> >>
>> >> If you do notice issues, please file any details on the following
>>JIRA
>> >> issue I have set up to track details:
>> >> https://issues.apache.org/jira/browse/CB-2404
>> >>
>> >> Thanks in advance!
>> >> Fil
>> >>
>> >>
>>
>>
Re: State of 2.4
I'm going to pull together a blog post on what is new on Android this weekend. I see Shaz already has one up for iOS. If anyone wants something specific included let me know. Simon Mac Donald http://hi.im/simonmacdonald On Fri, Feb 8, 2013 at 2:48 PM, Andrew Grieve wrote: > Awesome! Thanks for doing all of the work there. > > > On Fri, Feb 8, 2013 at 12:49 PM, Filip Maj wrote: > >> Yes! I had resolved the various "tag 2.4.0" issues on JIRA and was under >> the impression everyone had seen that. >> >> The 2.4.0 bits are up on http://apache.org/dist/cordova/ >> >> On 2/8/13 6:47 AM, "Andrew Grieve" wrote: >> >> >I saw the PhoneGap release announcement. Does this mean we're done the >> >release for 2.4.? We can start merging in pull requests? >> >>
Re: too long to package a release?
Nice! Thanks, Andrew!
-- Marcel Kinard
On Feb 7, 2013, at 2:59 PM, Andrew Grieve wrote:
> The doc's not up-to-date, but I think we ended on consensus for the code
> version. I've taken a stab at updating the wiki pages:
>
> http://wiki.apache.org/cordova/CordovaAndGit -- Added the idea of having
> both a master and a next branch
> http://wiki.apache.org/cordova/CommitterWorkflow -- Added Jesse's version
> of the "which branch - in code"
> http://wiki.apache.org/cordova/CuttingReleases -- Changed tagging
> instructions to refer to the "next" branch
>
>
> On Thu, Feb 7, 2013 at 1:26 PM, Marcel Kinard wrote:
>
>> With 2.5 starting, it appears time to poke this thread.
>>
>> - Is the Google doc refreshed with the latest consensus?
>> - If so, should the Google doc be transferred to a wiki page?
>> - Have the necessary branches been created?
>> - Are we all in the boat, and understand how to row this beast?
>>
>> -- Marcel Kinard
>>
>> On Jan 24, 2013, at 5:14 PM, Jesse wrote:
>>
>>> Nice Shaz, but I was hoping it was a github style network visualization
>>> that included a few versions worth of merges.
>>> Who wants to draw that?
>>>
>>> On Thu, Jan 24, 2013 at 2:05 PM, Shazron wrote:
>>>
Inline image got mangled, here it is linked: http://cl.ly/MOrD
On Thu, Jan 24, 2013 at 1:39 PM, Shazron wrote:
> Thanks for the pseudocode Andrew, seems simpler to understand ;)
>> Jesse's
> re-factor makes it even easier. Here's my contrib for those more
>> visually
> inclined:
>
>
> [image: Inline image 2]
>
>
> On Thu, Jan 24, 2013 at 1:29 PM, Andrew Grieve >> wrote:
>
>> Nice! even simpler. :)
>>
>>
>> On Thu, Jan 24, 2013 at 3:44 PM, Jesse
>> wrote:
>>
>>> Thanks for clarifying Andrew. et al, I guess I was mis-understanding
>> some
>>> of the earlier discussion around naming stuff.
>>>
>>> So everything is going to master all the time, and we only care about
>>> 'next' if we are inReleaseMode and it is a bug fix?
>>>
>>> if(inReleaseMode && isBugFix) {
>>> commitToBranch('next');
>>> mergeBranch('next').into('master');
>>> }
>>> else {
>>> commitToBranch('master');
>>> }
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Jan 24, 2013 at 12:29 PM, Andrew Grieve <
>> agri...@chromium.org
wrote:
>>>
Just to clarify - there should be *no* using of the git
>> cherry-picking
command, only git merge.
Jesse - not sure what you're referring to with "branch must be named
>> x".
The latest revision of the proposal has only two branches: master
>> and
>>> next.
Do you mean you don't like the name "next"?
Maybe the proposal will seem simpler if put in the form of code :)
if (!inReleaseMode) {
commitToBranch('master');
} else {
if (isBugFix) {
commitToBranch('next');
mergeBranch('next').into('master');
} else {
commitToBranch('master');
}
}
On Thu, Jan 24, 2013 at 3:06 PM, Braden Shepherdson <
>> bra...@chromium.org
> wrote:
> Most of the time the flow will be unchanged: push to master.
>> Tagging
things
> we already know how to do; that doesn't change.
>
> The only new flow for most people is cherrypicking bug fixes from
>>> master
to
> next, which we can give examples of. Plus that could remain the
> responsibility of the main platform maintainers, who are doing the
tagging.
>
> Braden
>
>
> On Thu, Jan 24, 2013 at 2:56 PM, Jesse
>>> wrote:
>
>> On Thu, Jan 24, 2013 at 11:09 AM, Braden Shepherdson <
> bra...@chromium.org
>>> wrote:
>>
>>> The founding goal we're trying to accomplish here is that we
>> don't
want
>>> everyone sitting on changes to be in the next version while we
>> use
> master
>>> to prep a release.
>>>
>>> I don't think having one branch for prepping the release and
>>> another
> for
>>> main development is a lot of bureaucracy.
>>>
>>
>> It is not, the 'branch must be named x' is mainly where I have
concerns.
>> Really I just want things simple.
>>
>>
>>>
>>>
>>> On Thu, Jan 24, 2013 at 1:57 PM, Jesse MacFadyen <
>> purplecabb...@gmail.com
wrote:
>>>
I have been quietly listening on this thread, but thought I
>>> should
at
least share my opinion.
I don't think adding contribution rules helps anyone. Git is
complicated enough
Re: [iOS] Call for testing
I'm thinking it is some kind of npm weirdness that I am not accounting
for..
Since this is an npm post-install script, it runs as a "nobody" user
(which is the "user" that npm runs as).. Maybe that has something to do
with it?
Is not wiring this up into post-install seem reasonable to anyone else?
Maybe on first-run instead of directly after an install?
On 2/8/13 1:59 PM, "Andrew Grieve" wrote:
>maybe xcodebuild -version is different when run with sudo?
>
>
>On Fri, Feb 8, 2013 at 4:45 PM, Filip Maj wrote:
>
>> Cool, thanks for checking it out Becky.
>>
>> That is exactly where some users are reporting their issues.
>>
>> Funny thing is, cordova-cli only runs "xcodebuild -version" to determine
>> if Xcode is installed or not. As long as the xcodebuild executable is in
>> your PATH it *should* work. I don't see how Xcode-select factors in here
>> though. Any ideas? Is my approach of checking iOS min reqs by shelling
>>out
>> to xcodebuild too naïve?
>>
>> On 2/8/13 1:38 PM, "Becky Gibson" wrote:
>>
>> >Interesting. I ran this once and it worked (I had to use sudo).
>>Then, I
>> >realized that I might have my xcode-selects variable set wrong since I
>> >recently downloaded Xcode 4.6 via the iOS downloads page rather than
>>via
>> >the AppStore. I put Xcode 4.6 into a subdirectory:
>> > /Applications/Xcode46/Xcode.app rather than right in the Applications
>> >folder. I realized that I should have also updated my xcode-select
>> >variable. I did that:
>> > sudo /usr/bin/xcode-select -switch
>> >/Applications/Xcode46/Xcode.app/Contents/Developer
>> >Then when I run sudo npm install -g cordova again, iOS fails:
>> > WARNING: Your system does not meet requirements to create
>>iosprojects.
>> >See error output below.
>> >Xcode is not installed. Cannot add iOS platform.
>> >SKIPPING ios bootstrap.
>> >
>> >So, I would guess it has to do with the xcode-selects value.
>> >
>> >Also, FWIW running the suggested sudo chown -R
>> >/usr/local/lib/node_modules/cordova command and it didn't work for
>>me. I
>> >haven't investigate that yet.
>> >
>> >-becky
>> >
>> >
>> >On Fri, Feb 8, 2013 at 3:59 PM, Filip Maj wrote:
>> >
>> >> Hey everyone,
>> >>
>> >> I've had a couple of reports of people using the cordova-cli tools
>>and
>> >> having issues installing. Apparently the post-install script
>> >>("bootstrap")
>> >> complains that Xcode is not installed on the system. Both users were
>> >> running Xcode 4.6.
>> >>
>> >> I've since upgraded my Xcode and done both a fresh install as well
>>as an
>> >> upgrade from old cli tools to new, and cannot reproduce (the
>>bootstrap
>> >> works; I get "SUCCESS: min reqs for iOS met").
>> >>
>> >> Could other contributors on the ML here, who have Xcode at least
>>4.5.2
>> >> installed, give it a shot and see if the installation goes through?
>> >>
>> >> To install, have node installed and run: npm install -g cordova
>> >> (you may need to put sudo in front of that if your node is installed
>> >> globally)
>> >>
>> >> Near the end of the installation process you should see something
>>like:
>> >>
>> >> > cordova@2.4.4 install /usr/local/lib/node_modules/cordova
>> >> > node bootstrap.js && ./bin/notice
>> >>
>> >> SUCCESS: Minimum requirements for blackberry met.
>> >> BOOTSTRAPPING blackberry...
>> >> SUCCESS: Minimum requirements for ios met.
>> >> BOOTSTRAPPING ios...
>> >> SUCCESS: ios ready to rock!
>> >> SUCCESS: blackberry ready to rock!
>> >> SUCCESS: Minimum requirements for android met.
>> >> BOOTSTRAPPING android...
>> >> SUCCESS: android ready to rock!
>> >>
>> >>
>> >> If you do notice issues, please file any details on the following
>>JIRA
>> >> issue I have set up to track details:
>> >> https://issues.apache.org/jira/browse/CB-2404
>> >>
>> >> Thanks in advance!
>> >> Fil
>> >>
>> >>
>>
>>
Re: [iOS] Call for testing
maybe xcodebuild -version is different when run with sudo?
On Fri, Feb 8, 2013 at 4:45 PM, Filip Maj wrote:
> Cool, thanks for checking it out Becky.
>
> That is exactly where some users are reporting their issues.
>
> Funny thing is, cordova-cli only runs "xcodebuild -version" to determine
> if Xcode is installed or not. As long as the xcodebuild executable is in
> your PATH it *should* work. I don't see how Xcode-select factors in here
> though. Any ideas? Is my approach of checking iOS min reqs by shelling out
> to xcodebuild too naïve?
>
> On 2/8/13 1:38 PM, "Becky Gibson" wrote:
>
> >Interesting. I ran this once and it worked (I had to use sudo). Then, I
> >realized that I might have my xcode-selects variable set wrong since I
> >recently downloaded Xcode 4.6 via the iOS downloads page rather than via
> >the AppStore. I put Xcode 4.6 into a subdirectory:
> > /Applications/Xcode46/Xcode.app rather than right in the Applications
> >folder. I realized that I should have also updated my xcode-select
> >variable. I did that:
> > sudo /usr/bin/xcode-select -switch
> >/Applications/Xcode46/Xcode.app/Contents/Developer
> >Then when I run sudo npm install -g cordova again, iOS fails:
> > WARNING: Your system does not meet requirements to create iosprojects.
> >See error output below.
> >Xcode is not installed. Cannot add iOS platform.
> >SKIPPING ios bootstrap.
> >
> >So, I would guess it has to do with the xcode-selects value.
> >
> >Also, FWIW running the suggested sudo chown -R
> >/usr/local/lib/node_modules/cordova command and it didn't work for me. I
> >haven't investigate that yet.
> >
> >-becky
> >
> >
> >On Fri, Feb 8, 2013 at 3:59 PM, Filip Maj wrote:
> >
> >> Hey everyone,
> >>
> >> I've had a couple of reports of people using the cordova-cli tools and
> >> having issues installing. Apparently the post-install script
> >>("bootstrap")
> >> complains that Xcode is not installed on the system. Both users were
> >> running Xcode 4.6.
> >>
> >> I've since upgraded my Xcode and done both a fresh install as well as an
> >> upgrade from old cli tools to new, and cannot reproduce (the bootstrap
> >> works; I get "SUCCESS: min reqs for iOS met").
> >>
> >> Could other contributors on the ML here, who have Xcode at least 4.5.2
> >> installed, give it a shot and see if the installation goes through?
> >>
> >> To install, have node installed and run: npm install -g cordova
> >> (you may need to put sudo in front of that if your node is installed
> >> globally)
> >>
> >> Near the end of the installation process you should see something like:
> >>
> >> > cordova@2.4.4 install /usr/local/lib/node_modules/cordova
> >> > node bootstrap.js && ./bin/notice
> >>
> >> SUCCESS: Minimum requirements for blackberry met.
> >> BOOTSTRAPPING blackberry...
> >> SUCCESS: Minimum requirements for ios met.
> >> BOOTSTRAPPING ios...
> >> SUCCESS: ios ready to rock!
> >> SUCCESS: blackberry ready to rock!
> >> SUCCESS: Minimum requirements for android met.
> >> BOOTSTRAPPING android...
> >> SUCCESS: android ready to rock!
> >>
> >>
> >> If you do notice issues, please file any details on the following JIRA
> >> issue I have set up to track details:
> >> https://issues.apache.org/jira/browse/CB-2404
> >>
> >> Thanks in advance!
> >> Fil
> >>
> >>
>
>
Re: too long to package a release?
Awesome! Stoked to see "next" branches dropping for the upcoming 2.5.0rc's
!
On 2/7/13 11:59 AM, "Andrew Grieve" wrote:
>The doc's not up-to-date, but I think we ended on consensus for the code
>version. I've taken a stab at updating the wiki pages:
>
>http://wiki.apache.org/cordova/CordovaAndGit -- Added the idea of having
>both a master and a next branch
>http://wiki.apache.org/cordova/CommitterWorkflow -- Added Jesse's version
>of the "which branch - in code"
>http://wiki.apache.org/cordova/CuttingReleases -- Changed tagging
>instructions to refer to the "next" branch
>
>
>On Thu, Feb 7, 2013 at 1:26 PM, Marcel Kinard wrote:
>
>> With 2.5 starting, it appears time to poke this thread.
>>
>> - Is the Google doc refreshed with the latest consensus?
>> - If so, should the Google doc be transferred to a wiki page?
>> - Have the necessary branches been created?
>> - Are we all in the boat, and understand how to row this beast?
>>
>> -- Marcel Kinard
>>
>> On Jan 24, 2013, at 5:14 PM, Jesse wrote:
>>
>> > Nice Shaz, but I was hoping it was a github style network
>>visualization
>> > that included a few versions worth of merges.
>> > Who wants to draw that?
>> >
>> > On Thu, Jan 24, 2013 at 2:05 PM, Shazron wrote:
>> >
>> >> Inline image got mangled, here it is linked: http://cl.ly/MOrD
>> >>
>> >>
>> >> On Thu, Jan 24, 2013 at 1:39 PM, Shazron wrote:
>> >>
>> >>> Thanks for the pseudocode Andrew, seems simpler to understand ;)
>> Jesse's
>> >>> re-factor makes it even easier. Here's my contrib for those more
>> visually
>> >>> inclined:
>> >>>
>> >>>
>> >>> [image: Inline image 2]
>> >>>
>> >>>
>> >>> On Thu, Jan 24, 2013 at 1:29 PM, Andrew Grieve > >wrote:
>> >>>
>> Nice! even simpler. :)
>>
>>
>> On Thu, Jan 24, 2013 at 3:44 PM, Jesse
>> wrote:
>>
>> > Thanks for clarifying Andrew. et al, I guess I was
>>mis-understanding
>> some
>> > of the earlier discussion around naming stuff.
>> >
>> > So everything is going to master all the time, and we only care
>>about
>> > 'next' if we are inReleaseMode and it is a bug fix?
>> >
>> > if(inReleaseMode && isBugFix) {
>> >commitToBranch('next');
>> >mergeBranch('next').into('master');
>> > }
>> > else {
>> >commitToBranch('master');
>> > }
>> >
>> >
>> >
>> >
>> >
>> > On Thu, Jan 24, 2013 at 12:29 PM, Andrew Grieve <
>> agri...@chromium.org
>> >> wrote:
>> >
>> >> Just to clarify - there should be *no* using of the git
>> cherry-picking
>> >> command, only git merge.
>> >>
>> >> Jesse - not sure what you're referring to with "branch must be
>>named
>> x".
>> >> The latest revision of the proposal has only two branches: master
>> and
>> > next.
>> >> Do you mean you don't like the name "next"?
>> >>
>> >> Maybe the proposal will seem simpler if put in the form of code
>>:)
>> >>
>> >> if (!inReleaseMode) {
>> >>commitToBranch('master');
>> >> } else {
>> >> if (isBugFix) {
>> >>commitToBranch('next');
>> >>mergeBranch('next').into('master');
>> >> } else {
>> >>commitToBranch('master');
>> >> }
>> >> }
>> >>
>> >>
>> >> On Thu, Jan 24, 2013 at 3:06 PM, Braden Shepherdson <
>> bra...@chromium.org
>> >>> wrote:
>> >>
>> >>> Most of the time the flow will be unchanged: push to master.
>> Tagging
>> >> things
>> >>> we already know how to do; that doesn't change.
>> >>>
>> >>> The only new flow for most people is cherrypicking bug fixes
>>from
>> > master
>> >> to
>> >>> next, which we can give examples of. Plus that could remain the
>> >>> responsibility of the main platform maintainers, who are doing
>>the
>> >> tagging.
>> >>>
>> >>> Braden
>> >>>
>> >>>
>> >>> On Thu, Jan 24, 2013 at 2:56 PM, Jesse
>> > wrote:
>> >>>
>> On Thu, Jan 24, 2013 at 11:09 AM, Braden Shepherdson <
>> >>> bra...@chromium.org
>> > wrote:
>>
>> > The founding goal we're trying to accomplish here is that we
>> don't
>> >> want
>> > everyone sitting on changes to be in the next version while we
>> use
>> >>> master
>> > to prep a release.
>> >
>> > I don't think having one branch for prepping the release and
>> > another
>> >>> for
>> > main development is a lot of bureaucracy.
>> >
>>
>> It is not, the 'branch must be named x' is mainly where I have
>> >> concerns.
>> Really I just want things simple.
>>
>>
>> >
>> >
>> > On Thu, Jan 24, 2013 at 1:57 PM, Jesse MacFadyen <
>> purplecabb...@gmail.com
>> >> wrote:
>> >
>> >> I have been quietly listening on this thread, but thought I
>> > should
>> >> at
>> >> least share my opin
Re: refactoring mobile spec (was: Creating repos for core plugins)
First pass: a test/ directory with one or more \w+.test.js files? Tools can find the .test.js files and run them automagically? Up to the author to decide which test framework to run with (jasmine, their own, qunit, whatever). All necessary supporting files to be included under ./test as well? What should be the test environment we want to focus on enabling plugin authors using? Node? Or provide a full integration testing path to test inside a cordova container as well? On 2/7/13 4:11 PM, "Michael Brooks" wrote: >Yes, each plugin should be responsible for its own tests. This is >something >that we should practice with the core plugins and encourage with >third-party plugins. > >I'm still playing catch up, but this is something that must be added to >the >plugin spec IMO. > >Michael > >On Thu, Feb 7, 2013 at 12:48 PM, Filip Maj wrote: > >> This is definitely what I had envisioned as well.. >> >> On 2/7/13 11:13 AM, "Andrew Grieve" wrote: >> >> >If someone wants to lead the charge on this angle of the plugin >> >splitting-out, that would be awesome. On the priority list though, I >>think >> >it's pretty low. Right now you have to set up the project file, add >>the >> >JS, and then run the tests. This model will still work when plugins are >> >separated out. >> > >> > >> >On Thu, Feb 7, 2013 at 1:21 PM, Marcel Kinard >>wrote: >> > >> >> I don't want to jump forward too far, but would it make sense to >>breakup >> >> mobile-spec in a similar way so that the tests for a plugin are >>actually >> >> located in the plugin's repo? Then the test and the function under >>test >> >> would be synchronized. And it could potentially open the way for >> >> third-parties to supply tests for their own plugins. >> >> >> >> -- Marcel Kinard >> >> >> >> On Feb 7, 2013, at 10:44 AM, Andrew Grieve >> wrote: >> >> >> >> > https://issues.apache.org/jira/browse/INFRA-5839 >> >> >> >> >> >>
Re: [iOS] Call for testing
Cool, thanks for checking it out Becky.
That is exactly where some users are reporting their issues.
Funny thing is, cordova-cli only runs "xcodebuild -version" to determine
if Xcode is installed or not. As long as the xcodebuild executable is in
your PATH it *should* work. I don't see how Xcode-select factors in here
though. Any ideas? Is my approach of checking iOS min reqs by shelling out
to xcodebuild too naïve?
On 2/8/13 1:38 PM, "Becky Gibson" wrote:
>Interesting. I ran this once and it worked (I had to use sudo). Then, I
>realized that I might have my xcode-selects variable set wrong since I
>recently downloaded Xcode 4.6 via the iOS downloads page rather than via
>the AppStore. I put Xcode 4.6 into a subdirectory:
> /Applications/Xcode46/Xcode.app rather than right in the Applications
>folder. I realized that I should have also updated my xcode-select
>variable. I did that:
> sudo /usr/bin/xcode-select -switch
>/Applications/Xcode46/Xcode.app/Contents/Developer
>Then when I run sudo npm install -g cordova again, iOS fails:
> WARNING: Your system does not meet requirements to create iosprojects.
>See error output below.
>Xcode is not installed. Cannot add iOS platform.
>SKIPPING ios bootstrap.
>
>So, I would guess it has to do with the xcode-selects value.
>
>Also, FWIW running the suggested sudo chown -R
>/usr/local/lib/node_modules/cordova command and it didn't work for me. I
>haven't investigate that yet.
>
>-becky
>
>
>On Fri, Feb 8, 2013 at 3:59 PM, Filip Maj wrote:
>
>> Hey everyone,
>>
>> I've had a couple of reports of people using the cordova-cli tools and
>> having issues installing. Apparently the post-install script
>>("bootstrap")
>> complains that Xcode is not installed on the system. Both users were
>> running Xcode 4.6.
>>
>> I've since upgraded my Xcode and done both a fresh install as well as an
>> upgrade from old cli tools to new, and cannot reproduce (the bootstrap
>> works; I get "SUCCESS: min reqs for iOS met").
>>
>> Could other contributors on the ML here, who have Xcode at least 4.5.2
>> installed, give it a shot and see if the installation goes through?
>>
>> To install, have node installed and run: npm install -g cordova
>> (you may need to put sudo in front of that if your node is installed
>> globally)
>>
>> Near the end of the installation process you should see something like:
>>
>> > cordova@2.4.4 install /usr/local/lib/node_modules/cordova
>> > node bootstrap.js && ./bin/notice
>>
>> SUCCESS: Minimum requirements for blackberry met.
>> BOOTSTRAPPING blackberry...
>> SUCCESS: Minimum requirements for ios met.
>> BOOTSTRAPPING ios...
>> SUCCESS: ios ready to rock!
>> SUCCESS: blackberry ready to rock!
>> SUCCESS: Minimum requirements for android met.
>> BOOTSTRAPPING android...
>> SUCCESS: android ready to rock!
>>
>>
>> If you do notice issues, please file any details on the following JIRA
>> issue I have set up to track details:
>> https://issues.apache.org/jira/browse/CB-2404
>>
>> Thanks in advance!
>> Fil
>>
>>
Re: [iOS] Call for testing
Interesting. I ran this once and it worked (I had to use sudo). Then, I
realized that I might have my xcode-selects variable set wrong since I
recently downloaded Xcode 4.6 via the iOS downloads page rather than via
the AppStore. I put Xcode 4.6 into a subdirectory:
/Applications/Xcode46/Xcode.app rather than right in the Applications
folder. I realized that I should have also updated my xcode-select
variable. I did that:
sudo /usr/bin/xcode-select -switch
/Applications/Xcode46/Xcode.app/Contents/Developer
Then when I run sudo npm install -g cordova again, iOS fails:
WARNING: Your system does not meet requirements to create iosprojects.
See error output below.
Xcode is not installed. Cannot add iOS platform.
SKIPPING ios bootstrap.
So, I would guess it has to do with the xcode-selects value.
Also, FWIW running the suggested sudo chown -R
/usr/local/lib/node_modules/cordova command and it didn't work for me. I
haven't investigate that yet.
-becky
On Fri, Feb 8, 2013 at 3:59 PM, Filip Maj wrote:
> Hey everyone,
>
> I've had a couple of reports of people using the cordova-cli tools and
> having issues installing. Apparently the post-install script ("bootstrap")
> complains that Xcode is not installed on the system. Both users were
> running Xcode 4.6.
>
> I've since upgraded my Xcode and done both a fresh install as well as an
> upgrade from old cli tools to new, and cannot reproduce (the bootstrap
> works; I get "SUCCESS: min reqs for iOS met").
>
> Could other contributors on the ML here, who have Xcode at least 4.5.2
> installed, give it a shot and see if the installation goes through?
>
> To install, have node installed and run: npm install -g cordova
> (you may need to put sudo in front of that if your node is installed
> globally)
>
> Near the end of the installation process you should see something like:
>
> > cordova@2.4.4 install /usr/local/lib/node_modules/cordova
> > node bootstrap.js && ./bin/notice
>
> SUCCESS: Minimum requirements for blackberry met.
> BOOTSTRAPPING blackberry...
> SUCCESS: Minimum requirements for ios met.
> BOOTSTRAPPING ios...
> SUCCESS: ios ready to rock!
> SUCCESS: blackberry ready to rock!
> SUCCESS: Minimum requirements for android met.
> BOOTSTRAPPING android...
> SUCCESS: android ready to rock!
>
>
> If you do notice issues, please file any details on the following JIRA
> issue I have set up to track details:
> https://issues.apache.org/jira/browse/CB-2404
>
> Thanks in advance!
> Fil
>
>
Re: CEF & Cordova?
Yes. Specifically Windows 7 as Win8 isn't even being talked about. http://code.google.com/p/chromiumembedded/ The cefclient looks to be a might more reasonable to work with than actual webkit. I've tweaked it to load locally and display as kiosk. Just need to wrap my head around exec(). On Fri, Feb 8, 2013 at 4:08 PM, Kerri Shotts wrote: > Wait -- are you asking if there's a desktop version of Phonegap? I was > assuming you meant a Chrome-based render for mobile devices, esp. since the > webkit on some mobile devices is quite borked. (Android 2.x, I'm looking at > you.) > > > > ___ > Kerri Shotts > photoKandy Studios, LLC > > On the Web: http://www.photokandy.com/ > > Social Media: > Twitter: @photokandy, http://twitter.com/photokandy > Tumblr: http://photokandy.tumblr.com/ > Github: https://github.com/kerrishotts > https://github.com/organizations/photokandyStudios > CoderWall: https://coderwall.com/kerrishotts > > Apps on the Apple Store: > > https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 > > > On Friday, February 8, 2013 at 2:57 PM, David Lewis wrote: > >> That's unfortunate. My team is working on webkit specific apps just >> because so many mobile devices use it; iOS, Android, and Blackberry >> 7+. Having a desktop webkit container would alleviate a lot of work >> forking Windows specific versions. I need to get it done anyway, I >> just thought I'd ask. The closest I've found is DesktopGap but it has >> less PG support than the current Win7 container. >> >> On Fri, Feb 8, 2013 at 3:27 PM, Kerri Shotts > (mailto:kerrisho...@gmail.com)> wrote: >> > Most modern platform's internal browsers are based on webkit -- iPhone and >> > Android, etc. Windows Phone (and the upcoming Firefox OS) would be >> > exceptions to the rule. >> > >> > I know there's been work done on supporting PG with Chrome as the >> > renderer, but don't hold your breath for it; a lot of stuff would have to >> > be rewritten. >> > ___ >> > Kerri Shotts >> > photoKandy Studios, LLC >> > >> > On the Web: http://www.photokandy.com/ >> > >> > Social Media: >> > Twitter: @photokandy, http://twitter.com/photokandy >> > Tumblr: http://photokandy.tumblr.com/ >> > Github: https://github.com/kerrishotts >> > https://github.com/organizations/photokandyStudios >> > CoderWall: https://coderwall.com/kerrishotts >> > >> > Apps on the Apple Store: >> > https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 >> > >> > >> > On Friday, February 8, 2013 at 1:33 PM, David Lewis wrote: >> > >> > > My project requires a webkit browser. Does anyone have experience >> > > adding Cordova support to Chromium Embedded Framework? >> > > >> > >> > >
Re: CEF & Cordova?
Wait -- are you asking if there's a desktop version of Phonegap? I was assuming you meant a Chrome-based render for mobile devices, esp. since the webkit on some mobile devices is quite borked. (Android 2.x, I'm looking at you.) ___ Kerri Shotts photoKandy Studios, LLC On the Web: http://www.photokandy.com/ Social Media: Twitter: @photokandy, http://twitter.com/photokandy Tumblr: http://photokandy.tumblr.com/ Github: https://github.com/kerrishotts https://github.com/organizations/photokandyStudios CoderWall: https://coderwall.com/kerrishotts Apps on the Apple Store: https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 On Friday, February 8, 2013 at 2:57 PM, David Lewis wrote: > That's unfortunate. My team is working on webkit specific apps just > because so many mobile devices use it; iOS, Android, and Blackberry > 7+. Having a desktop webkit container would alleviate a lot of work > forking Windows specific versions. I need to get it done anyway, I > just thought I'd ask. The closest I've found is DesktopGap but it has > less PG support than the current Win7 container. > > On Fri, Feb 8, 2013 at 3:27 PM, Kerri Shotts (mailto:kerrisho...@gmail.com)> wrote: > > Most modern platform's internal browsers are based on webkit -- iPhone and > > Android, etc. Windows Phone (and the upcoming Firefox OS) would be > > exceptions to the rule. > > > > I know there's been work done on supporting PG with Chrome as the renderer, > > but don't hold your breath for it; a lot of stuff would have to be > > rewritten. > > ___ > > Kerri Shotts > > photoKandy Studios, LLC > > > > On the Web: http://www.photokandy.com/ > > > > Social Media: > > Twitter: @photokandy, http://twitter.com/photokandy > > Tumblr: http://photokandy.tumblr.com/ > > Github: https://github.com/kerrishotts > > https://github.com/organizations/photokandyStudios > > CoderWall: https://coderwall.com/kerrishotts > > > > Apps on the Apple Store: > > https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 > > > > > > On Friday, February 8, 2013 at 1:33 PM, David Lewis wrote: > > > > > My project requires a webkit browser. Does anyone have experience > > > adding Cordova support to Chromium Embedded Framework? > > > > > >
Re: CEF & Cordova?
That's unfortunate. My team is working on webkit specific apps just because so many mobile devices use it; iOS, Android, and Blackberry 7+. Having a desktop webkit container would alleviate a lot of work forking Windows specific versions. I need to get it done anyway, I just thought I'd ask. The closest I've found is DesktopGap but it has less PG support than the current Win7 container. On Fri, Feb 8, 2013 at 3:27 PM, Kerri Shotts wrote: > Most modern platform's internal browsers are based on webkit -- iPhone and > Android, etc. Windows Phone (and the upcoming Firefox OS) would be exceptions > to the rule. > > I know there's been work done on supporting PG with Chrome as the renderer, > but don't hold your breath for it; a lot of stuff would have to be rewritten. > ___ > Kerri Shotts > photoKandy Studios, LLC > > On the Web: http://www.photokandy.com/ > > Phone: > +1 (312) 380-1035 (Google Voice) > +1 (618) 541-0176 (Mobile) > > Social Media: > Twitter: @photokandy, http://twitter.com/photokandy > Tumblr: http://photokandy.tumblr.com/ > Github: https://github.com/kerrishotts > https://github.com/organizations/photokandyStudios > CoderWall: https://coderwall.com/kerrishotts > > Apps on the Apple Store: > > https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 > > > On Friday, February 8, 2013 at 1:33 PM, David Lewis wrote: > >> My project requires a webkit browser. Does anyone have experience >> adding Cordova support to Chromium Embedded Framework? >> >> > >
[iOS] Call for testing
Hey everyone,
I've had a couple of reports of people using the cordova-cli tools and
having issues installing. Apparently the post-install script ("bootstrap")
complains that Xcode is not installed on the system. Both users were
running Xcode 4.6.
I've since upgraded my Xcode and done both a fresh install as well as an
upgrade from old cli tools to new, and cannot reproduce (the bootstrap
works; I get "SUCCESS: min reqs for iOS met").
Could other contributors on the ML here, who have Xcode at least 4.5.2
installed, give it a shot and see if the installation goes through?
To install, have node installed and run: npm install -g cordova
(you may need to put sudo in front of that if your node is installed
globally)
Near the end of the installation process you should see something like:
> cordova@2.4.4 install /usr/local/lib/node_modules/cordova
> node bootstrap.js && ./bin/notice
SUCCESS: Minimum requirements for blackberry met.
BOOTSTRAPPING blackberry...
SUCCESS: Minimum requirements for ios met.
BOOTSTRAPPING ios...
SUCCESS: ios ready to rock!
SUCCESS: blackberry ready to rock!
SUCCESS: Minimum requirements for android met.
BOOTSTRAPPING android...
SUCCESS: android ready to rock!
If you do notice issues, please file any details on the following JIRA
issue I have set up to track details:
https://issues.apache.org/jira/browse/CB-2404
Thanks in advance!
Fil
Re: CEF & Cordova?
Most modern platform's internal browsers are based on webkit -- iPhone and Android, etc. Windows Phone (and the upcoming Firefox OS) would be exceptions to the rule. I know there's been work done on supporting PG with Chrome as the renderer, but don't hold your breath for it; a lot of stuff would have to be rewritten. ___ Kerri Shotts photoKandy Studios, LLC On the Web: http://www.photokandy.com/ Phone: +1 (312) 380-1035 (Google Voice) +1 (618) 541-0176 (Mobile) Social Media: Twitter: @photokandy, http://twitter.com/photokandy Tumblr: http://photokandy.tumblr.com/ Github: https://github.com/kerrishotts https://github.com/organizations/photokandyStudios CoderWall: https://coderwall.com/kerrishotts Apps on the Apple Store: https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 On Friday, February 8, 2013 at 1:33 PM, David Lewis wrote: > My project requires a webkit browser. Does anyone have experience > adding Cordova support to Chromium Embedded Framework? > >
Re: State of 2.4
Awesome! Thanks for doing all of the work there. On Fri, Feb 8, 2013 at 12:49 PM, Filip Maj wrote: > Yes! I had resolved the various "tag 2.4.0" issues on JIRA and was under > the impression everyone had seen that. > > The 2.4.0 bits are up on http://apache.org/dist/cordova/ > > On 2/8/13 6:47 AM, "Andrew Grieve" wrote: > > >I saw the PhoneGap release announcement. Does this mean we're done the > >release for 2.4.? We can start merging in pull requests? > >
Re: Platform directories when unzipping and building 2.4 from source?
The javascript is a sub-project, you shouldn't need to use it on its own. Each platform subdirectory already has a set of javascript built specifically for that platform. On 2/8/13 11:36 AM, "Jean-Sebastien Delfino" wrote: >Hi all, > >While building 2.4 from source I noticed that the files in the platform >zips seem to be missing a path prefix. I was expecting to see js/README.md >instead of README.md in cordova-js.zip. > >Is that intentional? > >Will everything still work if I unzip cordova-js.zip under javascript/* >instead of js/* for example? or are you guys assuming a specific directory >structure? > >Thanks! > >- Jean-Sebastien
Platform directories when unzipping and building 2.4 from source?
Hi all, While building 2.4 from source I noticed that the files in the platform zips seem to be missing a path prefix. I was expecting to see js/README.md instead of README.md in cordova-js.zip. Is that intentional? Will everything still work if I unzip cordova-js.zip under javascript/* instead of js/* for example? or are you guys assuming a specific directory structure? Thanks! - Jean-Sebastien
CEF & Cordova?
My project requires a webkit browser. Does anyone have experience adding Cordova support to Chromium Embedded Framework?
Re: Creating repos for core plugins
I hate to say this but I think this is where Subversion is better than Git. One can checkout a sub-folder and does not need multiple repositories :-) On Fri, Feb 8, 2013 at 7:33 AM, Michal Mocny wrote: > [image: Inline image 1] > > > On Fri, Feb 8, 2013 at 10:10 AM, Brian LeRoux wrote: > >> For Git repos, I think so. >> >> On Fri, Feb 8, 2013 at 6:53 AM, Marcel Kinard wrote: >> > Have we set a record for the number of repositories for a single >> project at Apache? ;-) >> > >> > On Feb 8, 2013, at 2:40 AM, Brian LeRoux wrote: >> > >> >> Thanks for driving this Andrew! I hope infra doesn't hate us for this!! >> >> >> >> On Thu, Feb 7, 2013 at 7:44 AM, Andrew Grieve >> wrote: >> >>> https://issues.apache.org/jira/browse/INFRA-5839 >> >>> >> >>> >> > >> > >
Re: State of 2.4
Yes! I had resolved the various "tag 2.4.0" issues on JIRA and was under the impression everyone had seen that. The 2.4.0 bits are up on http://apache.org/dist/cordova/ On 2/8/13 6:47 AM, "Andrew Grieve" wrote: >I saw the PhoneGap release announcement. Does this mean we're done the >release for 2.4.? We can start merging in pull requests?
Re: Pull request for [CB-2280] and [CB-2281]
Thanks, You can check the comments in jira and in the pull request. Let me know if you need something from me :) /yaniv On 08/02/13 15:46, "Andrew Grieve" wrote: >Yep, I can certainly take this on :) > > >On Fri, Feb 8, 2013 at 9:38 AM, Yaniv De Ridder >wrote: > >> I'm looking for a committer to have a look at my pull requests to get >>them >> integrated. I was until now working with Shazron Abdullah but he asked >>me >> if I can eventually look for someone else as he is really busy right >>now. >> >> @Andrew Grieve You maybe ? >> >> /yaniv >>
Re: Creating repos for core plugins
[image: Inline image 1] On Fri, Feb 8, 2013 at 10:10 AM, Brian LeRoux wrote: > For Git repos, I think so. > > On Fri, Feb 8, 2013 at 6:53 AM, Marcel Kinard wrote: > > Have we set a record for the number of repositories for a single project > at Apache? ;-) > > > > On Feb 8, 2013, at 2:40 AM, Brian LeRoux wrote: > > > >> Thanks for driving this Andrew! I hope infra doesn't hate us for this!! > >> > >> On Thu, Feb 7, 2013 at 7:44 AM, Andrew Grieve > wrote: > >>> https://issues.apache.org/jira/browse/INFRA-5839 > >>> > >>> > > >
Re: Creating repos for core plugins
For Git repos, I think so. On Fri, Feb 8, 2013 at 6:53 AM, Marcel Kinard wrote: > Have we set a record for the number of repositories for a single project at > Apache? ;-) > > On Feb 8, 2013, at 2:40 AM, Brian LeRoux wrote: > >> Thanks for driving this Andrew! I hope infra doesn't hate us for this!! >> >> On Thu, Feb 7, 2013 at 7:44 AM, Andrew Grieve wrote: >>> https://issues.apache.org/jira/browse/INFRA-5839 >>> >>> >
Re: Creating repos for core plugins
Have we set a record for the number of repositories for a single project at Apache? ;-) On Feb 8, 2013, at 2:40 AM, Brian LeRoux wrote: > Thanks for driving this Andrew! I hope infra doesn't hate us for this!! > > On Thu, Feb 7, 2013 at 7:44 AM, Andrew Grieve wrote: >> https://issues.apache.org/jira/browse/INFRA-5839 >> >>
State of 2.4
I saw the PhoneGap release announcement. Does this mean we're done the release for 2.4.? We can start merging in pull requests?
Re: Pull request for [CB-2280] and [CB-2281]
Yep, I can certainly take this on :) On Fri, Feb 8, 2013 at 9:38 AM, Yaniv De Ridder wrote: > I'm looking for a committer to have a look at my pull requests to get them > integrated. I was until now working with Shazron Abdullah but he asked me > if I can eventually look for someone else as he is really busy right now. > > @Andrew Grieve You maybe ? > > /yaniv >
Pull request for [CB-2280] and [CB-2281]
I'm looking for a committer to have a look at my pull requests to get them integrated. I was until now working with Shazron Abdullah but he asked me if I can eventually look for someone else as he is really busy right now. @Andrew Grieve You maybe ? /yaniv
Re: Adding new LocalFileSystem constants.
Andrew: I like it. At some point, probably after 3.x, we need to take all these non-standard findings back to the w3c. Grouping them in their own plugins makes sense to me instead of gumming up the standards "pure" implementations. On Wed, Feb 6, 2013 at 8:14 AM, Andrew Grieve wrote: > Good point about their being the possibility of multiple shared media. Last > night I convinced myself that adding new constants may not be the best path > forward, and instead proposed a new API (on the JIRA issue.). > > > On Tue, Feb 5, 2013 at 2:50 PM, Bryan Higgins wrote: > >> Thanks for the info Andrew! >> >> It seems like the main difference between Android and BB10 is that we >> provide shared storage both internal and external. Apps like the camera >> will prompt where files should be saved once an SD card is inserted. It's >> also possible we could have multiple external sources (ie cloud storage, >> usb). >> >> My 2 cents is that SHARED is probably a better name for the default target. >> For platforms with removable media, constants are probably not the best way >> to go. As a developer, I'd want a API to query available mount points and >> go from there. >> >> >> >> On Tue, Feb 5, 2013 at 1:53 PM, Andrew Grieve >> wrote: >> >> > Thanks for the input Bryan! >> > >> > Good ref's for storage locations: >> > Android: >> http://developer.android.com/guide/topics/data/data-storage.html >> > ): >> > iOS: >> > >> > >> http://developer.apple.com/library/ios/#documentation/FileManagement/Conceptual/FileSystemProgrammingGUide/FileSystemOverview/FileSystemOverview.html >> > >> > Shared files: >> > On Android, they go on /sdcard/Pictures, /sdcard/Music, etc. >> > On iOS, Photos & Videos are shared via the AssetLibrary framework and >> music >> > through the MusicPlayer framework. Neither one is provides a >> > filesystem-like interface. >> > >> > >> > Would SHARED be different from EXTERNAL_ROOT? Maybe SHARED would be a >> > better name for it? >> > >> > >> > On Tue, Feb 5, 2013 at 1:31 PM, Bryan Higgins > > >wrote: >> > >> > > Hi Andrew, >> > > >> > > I really like this proposal. It's something we'd likely pick up for >> > > BlackBerry WebWorks. >> > > >> > > Right now we have a separate API call which removes the sandbox and >> > exposes >> > > the full file system via PERSISTENT. We provide constants for paths to >> > > things like application root, sd card and shared directories. Sandboxed >> > > file systems are rooted in a subdirectory of the application. That >> > approach >> > > (plus our use of local:/// protocol) has caused some confusion with >> > > developers. >> > > >> > > I think the list of android constants would work well for BB10, perhaps >> > > with the addition of SHARED. I'm not too familiar with iOS and Android >> > file >> > > systems. Is there a single directory which contains shared documents, >> > > music, etc? >> > > >> > > Thanks, >> > > Bryan >> > > >> > > >> > > >> > > On Tue, Feb 5, 2013 at 11:52 AM, Andrew Grieve >> > > wrote: >> > > >> > > > FYI - Still looking for feedback here! >> > > > >> > > > -- Forwarded message -- >> > > > From: Andrew Grieve (JIRA) >> > > > Date: Tue, Feb 5, 2013 at 11:38 AM >> > > > Subject: [jira] [Commented] (CB-285) Add property returning root path >> > of >> > > > PhoneGap files >> > > > To: callback-...@incubator.apache.org >> > > > >> > > > >> > > > >> > > > [ >> > > > >> > > > >> > > >> > >> https://issues.apache.org/jira/browse/CB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571437#comment-13571437 >> > > > ] >> > > > >> > > > Andrew Grieve commented on CB-285: >> > > > -- >> > > > >> > > > I like the idea of switching PERSISTENT to be internal-only. The W3C >> > spec >> > > > intends this area to be sandboxed to the app, so shouldn't be on the >> > > > sdcard. >> > > > >> > > > I think we need more than just an APP constant though, as there are >> > many >> > > > places where an app might want to put things. >> > > > >> > > > For iOS, You'd minimally want: >> > > > 1. Application bundle, >> > > > 2. >> > > > >> > > > >> > > > The other locations are all subdirectories of , so >> > not >> > > a >> > > > big deal if we don't have constants for them >> > > > >> > > > For Android, You'd minimally want: >> > > > 1. Assets directory (seems like a parallel to iOS Application Bundle) >> > > > 2. Application data on internal storage >> > (/data/data/$PACKAGE_NAME/files) >> > > > 3. Application cache on internal storage >> > (/data/data/$PACKAGE_NAME/cache) >> > > > 4. External root: (/sdcard) >> > > > >> > > > We could maybe combine #2 and #3 into a single one that gave you >> > > > /data/data/$PACKAGE_NAME, and document that Android wants files in >> the >> > > > "files" and "cache" directories. >> > > > >> > > > >> > > > >> > > > The Ideal iOS constants: >> > > > 1. PERSISTENT changes from /Documents --> >> > > > /Library/CdvPersistentStorage >> > > > 2. TEMPO
RE: Tagging 2.3.0rc2?
Hi Herm, I have 2 pull requests to put into Cordova webOS 2.5.0rc1 https://github.com/apache/cordova-js/pull/7 https://github.com/apache/cordova-js/pull/8 Thanks for merging them in Markus -Original Message- From: Herm Wong [mailto:kingoftheo...@hotmail.com] Sent: Dienstag, 15. Januar 2013 00:17 To: dev@cordova.apache.org Subject: RE: Tagging 2.3.0rc2? I'm merging this change in now; it'll be in the 2.4.0rc1 release. > From: markus.leutwy...@hp.com > To: dev@cordova.apache.org > Subject: RE: Tagging 2.3.0rc2? > Date: Fri, 4 Jan 2013 07:29:00 + > > Hi Herm, > > Here we go > > https://github.com/apache/cordova-js/pull/2 > > Thanks > > Markus > > -Original Message- > From: Herm Wong [mailto:kingoftheo...@hotmail.com] > Sent: Donnerstag, 3. Januar 2013 21:51 > To: dev@cordova.apache.org > Subject: RE: Tagging 2.3.0rc2? > > send me the url for your git repo and I'll merge in the changes from there. > > > From: markus.leutwy...@hp.com > > To: dev@cordova.apache.org > > Subject: RE: Tagging 2.3.0rc2? > > Date: Fri, 14 Dec 2012 00:59:21 + > > > > When will we cut 2.3.0rc2? > > > > Herm: I have added functionality to support for the menubutton in > > cordova-js for webOS ... how can I get that into rc2? > > > > Markus > > > > -Original Message- > > From: Shazron [mailto:shaz...@gmail.com] > > Sent: Dienstag, 11. Dezember 2012 22:19 > > To: dev@cordova.apache.org > > Subject: Re: Tagging 2.3.0rc2? > > > > iOS is almost ready to tag pending testing. Unfortunately most of us are > > off-site Wednesday so I can only test this Thursday and tag. > > > > > > On Mon, Dec 10, 2012 at 2:25 PM, Anis KADRI wrote: > > > > > Double the usual spam. Thanks Joe :-) ! > > > > > > > > > On Mon, Dec 10, 2012 at 2:20 PM, Joe Bowser wrote: > > > > > > > OK, I'm deleting the duplicates so we don't get confused. Sorry > > > > about getting inpatient! > > > > > > > > On Mon, Dec 10, 2012 at 2:17 PM, Joe Bowser wrote: > > > > > OH crap, I created a duplicate in our tracker. :( > > > > > > > > > > On Mon, Dec 10, 2012 at 2:16 PM, Michael Brooks > > > > > wrote: > > > > >> @Jesse I agree with you timeline. > > > > >> > > > > >> @Joe Yep, let's get the ball rolling. > > > > >> > > > > >> I've created JIRA issue CB-1982 to track our progress: > > > > >> > > > > >> https://issues.apache.org/jira/browse/CB-1982 > > > > >> > > > > >> Go Go Go! > > > > >> > > > > >> Michael > > > > >> > > > > >> On Mon, Dec 10, 2012 at 12:32 PM, Joe Bowser > > > > >> > > > wrote: > > > > >> > > > > >>> So, are we getting this ball rolling? > > > > >>> > > > > >>> On Fri, Dec 7, 2012 at 4:48 PM, Jesse > > > > >>> > > > wrote: > > > > >>> > +me > > > > >>> > > > > > >>> > Also, 2.3.0 final will be the last release of the year > > > > >>> > with > > > everyone > > > > >>> > hopefully enjoying some time off. > > > > >>> > Many of the Adobe+Cordova committers will be otherwise > > > > >>> > occupied > > > much > > > > >>> > of next week, so it may be best to push the release of > > > > >>> > 2.3.0 to the middle of the following week, on like the > > > > >>> > 18th or 19th > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > On Fri, Dec 7, 2012 at 4:37 PM, Anis KADRI > > > > >>> > > > > > wrote: > > > > >>> >> I approve this message > > > > >>> >> > > > > >>> >> > > > > >>> >> On Fri, Dec 7, 2012 at 3:28 PM, Brian LeRoux > > > > >>> >> wrote: > > > > >>> >> > > > > >>> >>> agree > > > > >>> >>> > > > > >>> >>> On Fri, Dec 7, 2012 at 1:38 PM, Simon MacDonald > > > > >>> >>> wrote: > > > > >>> >>> > We doing that or going straight to 2.3.0 release? > > > > >>> >>> > Personally > > > I'd > > > > >>> like to > > > > >>> >>> > see a 2.3.0rc2 on Monday then if no fixes are checked > > > > >>> >>> > in cut > > > > 2.3.0 > > > > >>> the > > > > >>> >>> > following week. > > > > >>> >>> > > > > > >>> >>> > Simon Mac Donald > > > > >>> >>> > http://hi.im/simonmacdonald > > > > >>> >>> > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > -- > > > > >>> > @purplecabbage > > > > >>> > risingj.com > > > > >>> > > > > > > > >
Re: JS Symbols
I'm cool w/ window.cordova.plugins (or is it window.Cordova.plugins?) Don't think we should prescribe anything for 3rd party plugins but encourage namespaced behavior as jesse suggests. On Thu, Feb 7, 2013 at 2:00 PM, Anis KADRI wrote: > I agree with window.plugins for everything that is not a polyfill. > > > On Thu, Feb 7, 2013 at 12:43 PM, Filip Maj wrote: > >> Agree with everything Jesse said. cordova.plugins could be considered >> "safe", but not required. It's just JavaScript! >> >> On 2/6/13 6:27 PM, "Jesse" wrote: >> >> >> I would prefer cordova.plugins instead of directly on cordova. >> >+1 >> > >> >I agree, and like having core plugins live under cordova.plugins.*, but I >> >don't think this should be a requirement of other plugins. >> > >> >For example: com.dropbox.session.startAuthentication(this); >> >makes sense to me >> > >> >In the end, anyone can come along and make their own aliases anyway ... >> >it's only js >> > >> >var dBox = com.dropbox; >> > >> >PS: if devs are 'discovering' plugins in web inspector, then they already >> >have installed them in their app ... ? And this assumes that web-inspector >> >is available on the platform in question. >> > >> > >> >On Wed, Feb 6, 2013 at 6:11 PM, Shazron wrote: >> > >> >> I agree with Michal that hanging things off the cordova object can get >> >> pretty unmanageable after a while, and having it namespaced under >> >> cordova.plugins or something similar would be better. >> >> >> >> InAppBrowser is a weird one since window.open will work in browsers, but >> >> not everything it supports is supported in browsers (addEventListener, >> >>etc) >> >> >> >> >> >> On Wed, Feb 6, 2013 at 5:48 PM, Michal Mocny >> >>wrote: >> >> >> >> > I like the proposal, and do think our extensions should be namespaced. >> >> > However, your one example of InAppBrowser is debatable if it is a >> >> polyfill >> >> > or extension, and has good arguments for either side. So, perhaps we >> >>can >> >> > leave that example (or any other specific plugin) aside, and focus on >> >>the >> >> > overall proposal. >> >> > >> >> > I would prefer cordova.plugins instead of directly on cordova. >> >> > >> >> > I also think it would be nice for devs to discover cordova extensions >> >>in >> >> > web inspector by just typing cordova.plugins. and see whats available. >> >> > >> >> > -Michal >> >> > >> >> > >> >> > On Wed, Feb 6, 2013 at 11:33 AM, Andrew Grieve >> >> wrote: >> >> > >> >> > > Some of our APIs are meant to be polyfills, and some of them are >> >>not. >> >> > > >> >> > > It's great to expose the polyfill-type ones using the >> >>standards-based >> >> > > symbols. E.g. FileEntry, requestFileSystem. >> >> > > >> >> > > For the custom ones though, I think it's important for devs to >> >>realize >> >> > that >> >> > > the APIs they are using are custom to Cordova, and will never work >> >>in >> >> > other >> >> > > browsers. >> >> > > >> >> > > Examples: >> >> > > Camera: window.Camera >> >> > > InAppBrowser: window.open() >> >> > > globalization: navigator.globalization >> >> > > >> >> > > There's been some talk about deprecating the window.plugins >> >>namespace. >> >> > But >> >> > > why? I think it would be clearer if these apis were: >> >> > > Camera: plugins.camera >> >> > > InAppBrowser: plugins.inappbrowser.open >> >> > > globalization: plugins.globalization >> >> > > >> >> > > This makes it much more clear that the APIs are not browser-based >> >>ones, >> >> > but >> >> > > Cordova-specific. >> >> > > >> >> > > If the rational to get rid of the plugins is to save on a global >> >> symbol, >> >> > > how about using cordova as the namespace? >> >> > > >> >> > > cordova.camera.getPicture() >> >> > > cordova.inappbrowser.open() >> >> > > corodva.globalization.getLocale() >> >> > > >> >> > > aka: >> >> > > cordova.$PLUGIN_NAME.exports >> >> > > >> >> > > Thoughts? >> >> > > >> >> > >> >> >> > >> > >> > >> >-- >> >@purplecabbage >> >risingj.com >> >>
Re: Proposal for JS in Plugins
You know what. I'm super wrong. I was thinking in the context of a native project and not a *cordova* project. The flaw in the thinking was that we were shipping only one file we build leaving devs to include as they see fit. But whats really happening is that we are generating a new file for every plugin add/remove which will be different for each platform. If they move that file around and include from a directory of their choosing we're fucked. The difference here is the audience. A developer content to NOT use our tools, and compose their own app for a single platform, say Android, is going to have to figure out inclusion themselves. For us, its a build time concern. Not magic. Consider: we are required to re-build every time a user adds/removes a plugin. And if they move that generated file, again, we're fucked. This is increasingly looking like a script injectwhich we could make configurable with config.xml so that it isn't too magical feeling. We should talk about how the www install part works though. I wonder if it would appropriate to propose a special folder in www for this purpose. Like node_modules but without fugly underscores. On Wed, Feb 6, 2013 at 4:01 PM, Andrew Grieve wrote: > For a project who's main language is JS, I'm a bit surprised that injecting > a script tag through DOM manipulation would put us into the "magic" > category... > > Brian - Your sentiments about the development stack don't make sense to me. > The development stack is *the* job of CLI. We are prescribing a way to set > up your project so that it's easy to have an x-platform www directory, and > writing tools to make it easy to add/remove plugins. Is not "the > development stack" *the* goal of CLI? > > This isn't a problem that we can "not solve". It's a problem that exists, > and doing nothing *is a solution*. Here's the "do nothing" solution: > - Let plugins put their .js file anywhere within the www/ directory (and > hope that it doesn't clobber anything) > - Have them write documentation to instruct users that they must insert > their script tags into each of their .html files > - Hope that users notice the instructions, and that they are correct, and > that they don't mess them up > - Hope that users can remember which JS files belong to what if they ever > want to remove plugins > > Note that for our core plugins, we have 78 .js files just within > lib/common/plugin. > > A variation on "do nothing": > - Tell each plugin developer to come up with their own packaging system > - Tell them to check in a pre-packaged version with every commit (or just > on releases) > - Tell them to write instructions for the manual steps involved in adding / > removing their plugins. > > I don't accept that this isn't a problem. If there are actually better > alternatives, I'd like to hear what they are, and what the development > workflow looks like for both the plugin users as well as the plugin > developers. > > > Anis - What sort of needs / requirements are you thinking of that won't > work with the injecting script tags approach? Let's try and work through > them. The same argument could be used to shoot down the entire CLI effort... > > > Andrew > > > On Wed, Feb 6, 2013 at 6:27 PM, Joe Bowser wrote: > >> I also disagree with automagically injecting the script tags. If >> we're adding the script tags, we have the ability of adding the script >> tags wrong, and breaking people's apps with magic. We have enough >> trouble directing our users to use Cordova/PhoneGap without us trying >> to make things more clever. >> >> On Wed, Feb 6, 2013 at 2:39 PM, Anis KADRI wrote: >> > I don't think we should be automatically injecting javascript tags. >> > Instruct users to do so when they add a plugin by displaying the tag. >> > Everyone has different needs/requirements. >> > >> > Also >> > >> > *"cordova plugin add file" >> > - Download plugin files to project/plugins >> > - Runs plugman to install native parts of the plugin. >> > - Plugman will copy JS files listed into >> > project/platforms/cordova-js/lib/...* >> > * * >> > *plugman supports installation by local-dir/git-repo/name. Names are >> > listed/stored on an outside source. So I believe this step should just >> call >> > plugman with the name/git/local-dir. We've already agreed that all >> plugins >> > will have separate repositories, yes ?* >> > > Which step are you referring to? Could you maybe write out the version of > how things work that you're suggesting? > > > >> > * >> > * >> > *I also agree that plugin.xml should support dependencies and that we >> > should update the plugin spec. **I like the requires-plugin tag but I am >> > not sure I like that js-symbols tag in plugin.xml though. **I am confused >> > about that "Exporting Module Symbols" section. An example would be >> > appreciated.* >> > > There's this example in the doc already: > * > > > > target=”requestFileSystem”> > >target=”navigator.connection”> > > > * > * > * > And what symbol
Re: FW: File API for Review
Yes and yes On Wed, Feb 6, 2013 at 12:06 PM, Filip Maj wrote: > In light of recent discussion re: figuring out whether to add new > constants for various FileSystem locations (I.e. PERSISTENT vs TEMPORARY > vs APP vs SOMENEWDIRECTORYLOCATION), perhaps we should chime in on this > new thread that came into the web apps WG? > > On 2/6/13 11:58 AM, "Arun Ranganathan" wrote: > >>Greetings WebApps WG! >> >>Review on the File API is encouraged: >> >>http://dev.w3.org/2006/webapi/FileAPI/ >> >>A few substantial changes that might need particular attention before we >>initiate a call for LCWD or something comparably official: >> >>1. autoRevoke behavior of Blob URIs has changed. Previous drafts made >>the autoRevoke behavior on by default (by consensus), but didn't harness >>revocation to a suitable and unambiguous "scope." Thanks to a fix to >>HTML[1] we can leverage the global script clean-up jobs list, to which we >>add revocation of Blob URIs. Blob URIs are thus either scoped to the >>next time global script clean-up jobs are processed (by default), OR when >>document unloading steps are processed if the developer opts out of the >>default but never pairs it with a call to URL.revokeObjectURL, OR when >>URL.revokeObjectURL is called. >> >>In particular, this behavior defers from shipping implementations such as >>IE10. This is possibly the biggest change: >> >>http://dev.w3.org/2006/webapi/FileAPI/#lifeTime >> >>http://dev.w3.org/2006/webapi/FileAPI/#creating-revoking >> >>2. An utility to smooth line ending variations (Unix vs. Windows) has >>been added, but is an orphan interface currently. Nobody's fussed over >>this, and it might not be a problem at all, but I'd like to draw your >>attention to it :) While currently only relevant for DOMString arguments >>to the Blob constructor, we might work with the utility to add other >>arguments (including ArrayBufferViews, etc.). >> >>http://dev.w3.org/2006/webapi/FileAPI/#convenienceAPI >> >>3. Progress events have been clarified. >> >>4. readAsDataURL currently makes progress notifications throughout the >>read, but only returns a non-null return value at the end of the read. >> >>http://dev.w3.org/2006/webapi/FileAPI/#readAsDataURL >> >>Specification bugs still exist, and this draft doesn't address all open >>bugs [2]; further bugs and issues, if any, should be logged or discussed >>on this listserv. The remaining bugs present use cases that aren't major >>enough to warrant feature extensions. >> >>-- A* >> >>[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=19554 >> >>[2] >>https://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&component=Fil >>e%20API&resolution=---&list_id=4913 >
Re: a Cordova Jake Error ?
I have no control other than to request help from infra. (To my knowledge.)
Paul: after reviewing that doc Anis sent can you open a ticket w/ Infra?
On Thu, Feb 7, 2013 at 12:45 PM, Filip Maj wrote:
> You should be committing to Apache repos:
> https://git-wip-us.apache.org/repos/asf/
>
> If you go to http://people.apache.org/committer-index.html and search for
> your last name, you'll see that you are a committer listed under the
> cordova project.
>
> I'm CC'ing Brian. Brian, can you check Paul's permissions? Is this
> something that you can fix Brian?
>
> On 2/7/13 8:03 AM, "Plaquette, Paul" wrote:
>
>>Hi Anis,
>>
>>Do you have an idea of what could go wrong with codova repositories access
>>rights?
>>
>>in the mail i received there was :
>>
>>Please note that until the Project Management Committee responsible for
>>the
>>> project to which you were given group membership actually grants you
>>>access
>>> to the relevant source code modules, you won't be able to commit
>>>anything.
>>> If you have problems committing, you need to email
>>> priv...@cordova.apache.org.
>>
>>
>>Moreover, should we commit on apache repositories or on github mirrors
>>repositories?
>>
>>
>>Thanks,
>>Paul
>>
>>
>>
>>On Wed, Feb 6, 2013 at 8:11 PM, Anis KADRI wrote:
>>
>>> The beauty of Mac OS X users and their case-insensitive filesystems :-)
>>>
>>>
>>> On Wed, Feb 6, 2013 at 4:50 AM, Gord Tanner wrote:
>>>
>>> > I can clean this up today
>>> >
>>> > Sent from my iPhone
>>> >
>>> > On 2013-02-06, at 4:28 AM, "Plaquette, Paul"
>>>
>>> > wrote:
>>> >
>>> > > I would love to...
>>> > > But it seems I am not yet a "double zero committer"
>>> > > I Mean with the "permission to commit" ;-)
>>> > >
>>> > > -Original Message-
>>> > > From: Filip Maj [mailto:f...@adobe.com]
>>> > > Sent: Wednesday, February 06, 2013 1:21 AM
>>> > > To: dev@cordova.apache.org
>>> > > Subject: Re: a Cordova Jake Error ?
>>> > >
>>> > > Hey Paul, I believe this issue already notes this problem:
>>> > >
>>> > > https://issues.apache.org/jira/browse/CB-2345
>>> > >
>>> > >
>>> > > Feel free to patch it, you are a committer after all :)
>>> > >
>>> > > On 2/5/13 7:53 AM, "Plaquette, Paul"
>>>rote:
>>> > >
>>> > >> sounds the culprit might be a line in the jakefile:
>>> > >>
>>> > >>
>>> "lib/firefoxos/plugin/firefoxos/Device.js":/(this\.cordova\s=\s").+(")/
>>> > >> ,
>>> > >>
>>> > >> in place of:
>>> > >>
>>> > >>
>>> "lib/firefoxos/plugin/firefoxos/device.js":/(this\.cordova\s=\s").+(")/
>>> > >> ,
>>> > >>
>>> > >> hope this helps !
>>> > >>
>>> > >>
>>> > >> On Tue, Feb 5, 2013 at 4:45 PM, Plaquette, Paul
>>> > >> wrote:
>>> > >>
>>> > >>> Hi all,
>>> > >>>
>>> > >>> I get a fresh Cordova repository and by the way I also updated
>>>node
>>> > >>> on my ubuntu 12.04 laptop.
>>> > >>>
>>> > >>> When I build using command line jake I got this:
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>> jake aborted.
>>> > >>> Error: ENOENT, no such file or directory
>>> > >>> 'lib/firefoxos/plugin/firefoxos/Device.js'
>>> > >>>at Object.openSync (fs.js:230:18) (See full trace by running
>>>task
>>> > >>> with --trace)
>>> > >>>
>>> > >>> the build succeed if the device.js file in firefoxos is renamed as
>>> > >>> Device.js
>>> > >>>
>>> > >>> Does someone see what is going wrong?
>>> > >>> (Actually I wonder if it is an issue on may machine or not)
>>> > >>>
>>> > >>> Cordially,
>>> > >>> Paul
>>> > >>>
>>> > >>>
>>> > >>> --
>>> > >>>
>>> > >>>
>>> > >>> Paul Plaquette,
>>> > >>> Senior Software Engineer
>>> > >>> Intel Corporation SAS
>>> > >>> Open source Technology Center - OTC
>>> > >>> France, Montpellier
>>> > >>
>>> > >>
>>> > >> --
>>> > >>
>>> > >>
>>> > >> Paul Plaquette,
>>> > >> Senior Software Engineer
>>> > >> Intel Corporation SAS
>>> > >> Open source Technology Center - OTC
>>> > >> France, Montpellier
>>> > >
>>> > >
>>>-
>>> > > Intel Corporation SAS (French simplified joint stock company)
>>> > > Registered headquarters: "Les Montalets"- 2, rue de Paris,
>>> > > 92196 Meudon Cedex, France
>>> > > Registration Number: 302 456 199 R.C.S. NANTERRE
>>> > > Capital: 4,572,000 Euros
>>> > >
>>> > > This e-mail and any attachments may contain confidential material
>>>for
>>> > > the sole use of the intended recipient(s). Any review or
>>>distribution
>>> > > by others is strictly prohibited. If you are not the intended
>>> > > recipient, please contact the sender and delete all copies.
>>> > >
>>> >
>>> -
>>> Intel Corporation SAS (French simplified joint stock company)
>>> Registered headquarters: "Les Montalets"- 2, rue de Paris,
>>> 92196 Meudon Cedex, France
>>> Registration Number: 302 456 199 R.C.S. NANTERRE
>>> Capital: 4,572,000 Euros
>>>
>>> This e-mail and any attachments may contain confidential material for
>>> the sole use of the int
Re: cordova-cli documentation in cordova-docs
+1 also docs.cordova.io On 08/02/2013, at 5:21 PM, Brian LeRoux wrote: > Should probably start its life as markdown files in the cordova-cli > repo to allow interactive help during usage. (First place I'd go for > help using it would be the tool itself.) > > On Thu, Feb 7, 2013 at 4:13 PM, Michael Brooks > wrote: >> I would vote for it to be included in the Cordova documentation ( >> docs.cordova.io). >> >> Michael >> >> On Thu, Feb 7, 2013 at 3:10 PM, Anis KADRI wrote: >> >>> I don't know about getting started but I vote for it being part of >>> docs.cordova.io >>> >>> >>> On Thu, Feb 7, 2013 at 3:04 PM, Filip Maj wrote: >>> We have none at the moment :) Any thoughts/recommendations on where it should go, what it should look like? Part of the getting started guide or no? >>>
