What about the start/stop progress?
On Wed, Sep 18, 2013 at 9:03 PM, Ian Clelland wrote:
> +1
>
> Also, if you are a component "owner", it's pretty simple in JIRA to add a
> dashboard widget that shows you all unassigned bugs in your component.
>
> Ian
>
>
> On Wed, Sep 18, 2013 at 11:49 PM, Joe
+1
Also, if you are a component "owner", it's pretty simple in JIRA to add a
dashboard widget that shows you all unassigned bugs in your component.
Ian
On Wed, Sep 18, 2013 at 11:49 PM, Joe Bowser wrote:
> +1
>
+1
+1
Simon Mac Donald
http://hi.im/simonmacdonald
On Wed, Sep 18, 2013 at 11:00 PM, Andrew Grieve wrote:
> Motivation:
> It's impossible to know whether new bugs have been looked at by the default
> assignee.
>
> Rationale:
> Setting it to , means new bugs will be obviously "untriaged".
> Once as
Motivation:
It's impossible to know whether new bugs have been looked at by the default
assignee.
Rationale:
Setting it to , means new bugs will be obviously "untriaged".
Once assigned, it will mean someone intends to work on it.
This won't eliminate bugs that get assigned and then not fixed in a
If it's easy to support, then I think it's worth doing.
A custom scheme would work, but I think we can do it with a less intrusive
change:
We came up with the following hack during our chrome-apps-on-cordova work
for having CORS work when on a custom scheme. Should work for WebSQL as
well though.
(FWIW, I've assumed any bug is up for grabs if it isn't marked "in
progress", regardless of who is assigned.)
On Wed, Sep 18, 2013 at 7:31 PM, Andrew Grieve wrote:
> I assigned it to David just because I thought it would be a good bug for
> him and thought it sounded important to fix. I don't t
I assigned it to David just because I thought it would be a good bug for
him and thought it sounded important to fix. I don't think he's in any
hurry to get to it, so feel free to assign it to yourself. I don't really
consider bugs to be actually assigned when they are assigned to the default
perso
We definitely want this, and there's an issue created for it already:
https://issues.apache.org/jira/browse/CB-4382
If you can look into adding it, that'd be awesome. Possible that +Ian will
be looking at it shortly as well.
On Wed, Sep 18, 2013 at 4:52 PM, Michael Wolf wrote:
> All:
>
> Curiou
Windows Phone has never supported it. I have always felt that this is more
of a browser responsibility and didn't belong in the 'phonegap features'
matrix. Just like we don't list querySelectorAll or SVG support.
Someone needs to write a JS shim that uses the File API which IS available
on all th
Ok, We've been ignoring this for quite a while, but it's not going away:
There's still people who want to use WebSQL, and WebSQL is still
totally broken. Part of the reason it's broken is the fact that
Android prevents us from using the official WebSQL API on file URIs,
and that we have a nasty c
D'oh my maths issa bad. 50% increase in testing, of course.
On Wed, Sep 18, 2013 at 1:31 PM, Shazron wrote:
> Developer neglect, really. Seeing as I don't really have a work iOS 5
> device to test on. If I did, testing would add another platform, so 33.33%
> increase in testing time :p
>
> Also
I'm currently trying to figure out CB-4858, which got assigned to
David, but I'm finding that I'm getting stuck at this part:
private String updateUrl(String url) {
Uri newUrl = Uri.parse(url);
if (newUrl.isRelative()) {
//url = this.webView.getUrl().substring(0,
t
All:
Curious what you thought of this. We have a situation where we would want to
know the platforms being built and other arguments being passed, in the hooks.
See any reason why this shouldn't be integrated ?
If not I'm going to look into adding this.
mw
Shaz - Thanks for the update :). If iOS is the last one then I'd say let's
go without, but maybe keep at it until we get BB tagged? (just my opinion)
Heading home now - anyone know if Lorin is away or not?
On Wed, Sep 18, 2013 at 3:35 PM, Shazron wrote:
> When i mean ios-deploy still works, it
Developer neglect, really. Seeing as I don't really have a work iOS 5
device to test on. If I did, testing would add another platform, so 33.33%
increase in testing time :p
Also, any code changes _have_ to take into account older platforms, whether
the API exists, and guard against it during runti
Out of curiosity, what would be your back-of-the-napkin calculation on the cost
per Cordova release to keep iOS 5 support?
Ping Lorin & Shaz.
On Wed, Sep 18, 2013 at 2:19 AM, Steven Gill wrote:
> FFOS will be tagged tomorrow. I have a few changes I am going to get in
> tomorrow before tagging but it will be good to go very soon!
>
> With FFOS, Only two plugins have been ported so far (vibration and device).
> We ar
On Wed, Sep 18, 2013 at 3:10 PM, Joe Bowser wrote:
> OK, that's pretty damn dishonest. I did pull and see that it was
> retagged like you said it was yesterday. I think blaming me for using
> the old tag back before you retagged is a pretty crap thing to do.
>
Woah - I'm not blaming here, I don
http://static.giantbomb.com/uploads/original/4/40057/2482831-archer-1-phrasing.jpg
Simon Mac Donald
http://hi.im/simonmacdonald
On Wed, Sep 18, 2013 at 3:10 PM, Joe Bowser wrote:
> OK, that's pretty damn dishonest. I did pull and see that it was
> retagged like you said it was yesterday. I thin
I'm 99% done with iOS specific fixes. One last one I'm trying to do is
ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
This means if I don't get this fix in, we _can_ deploy from the command
line using ios-deploy _but_ we can't attach to the debugger. Will that be
acceptable yo
When i mean ios-deploy still works, it _installs_ it on the device, but
does _not_ run it.
On Wed, Sep 18, 2013 at 12:31 PM, Shazron wrote:
> I'm 99% done with iOS specific fixes. One last one I'm trying to do is
> ios-deploy with lldb: https://issues.apache.org/jira/browse/CB-4804
>
> This mea
The extra hash on the end was the reason for the re-tag of cordova-js.
Maybe you forgot to "git pull" and still have your cordova-js at the
previous tag?
Coho's not involved in any of that. The code is in
cordova-js/build/packager.js
On Wed, Sep 18, 2013 at 2:35 PM, Joe Bowser wrote:
> After I
OK, that's pretty damn dishonest. I did pull and see that it was
retagged like you said it was yesterday. I think blaming me for using
the old tag back before you retagged is a pretty crap thing to do.
Also, Why in the hell are we storing the version in
CordovaWebView.java? Does it need to be the
After I let Andrew do the tagging of RC1, I noticed something that
looks broken by the fact that I can't reproduce this result without
using coho, and I can't find in the source where coho messes with the
build labels.
Now, as well all know, the JS is generated by Grunt. Assuming that
we're going
On Fri, Sep 13, 2013 at 8:23 AM, Michael Sierra wrote:
> I'm doing a bunch of cleanup work on the doc about config.xml
> preferences, and have accumulated a faceful of queries I could use
> some help with. I'm also folding in some parallel PhoneGap Build doc
> where appropriate, but suspect some o
Thanks, Bryan. If you still think you can answer the main batch of BB queries,
can you also check if BB's HideKeyboardFormAccessoryBar pref really responds to
'enable'/'disable' values rather than 'true'/'false' as is doc'ed for iOS?
--Mike Sierra
From:
Hi Everyone. :)
My points below are but the surface of my own perspective on Cordova,
I'm holding back my Cordova philosophy discussion for Brian next week
heh ^^
The last hangout was a great forum for discussion, certainly these
essay type threads belong there.
I can sympathise a little with Joe
Two points to re-iterate.
1. We have a release tool of beta quality is probably isn't quite ready for
prime time. That's ok. We're all on the same page of automation to reduce
complexity and likely human error. Lets fix it.
2. Essay's in email or docs are a bit of a pain to read and sometimes hav
29 matches
Mail list logo
