How does this affect URI handling? We've had far bigger issues with
file:///android-asset failing on ICS+. Did you test with URIs that contain
a question mark, pound or a colon?
On Apr 16, 2013 7:23 PM, "Andrew Grieve" wrote:
> Found a juicy hack that works around the webview disabling WebSQL
Only when we decide to drop plugin.
On Apr 16, 2013 8:14 PM, "Filip Maj" wrote:
> https://issues.apache.org/jira/browse/CB-1109
>
>
> We need to add a deprecation notice to change this, is that right?
>
>
https://issues.apache.org/jira/browse/CB-1109
We need to add a deprecation notice to change this, is that right?
Found a juicy hack that works around the webview disabling WebSQL for file:
URLs.
For our Chrome Apps plugins, we serve apps from chrome-extension:// URLs
instead of file:// URLs. This is possible via shouldInterceptRequest(),
where we just map the requests to the files.
So... I had the idea to t
Yep I can edit, thanks Shaz!
On Tue, Apr 16, 2013 at 3:14 PM, Brian LeRoux wrote:
> ya no kidding
>
>
> On Tue, Apr 16, 2013 at 2:46 PM, Anis KADRI wrote:
>
> > That's cool! I was getting tired of googling every apache conference
> since
> > 1970.
> >
> >
> > On Tue, Apr 16, 2013 at 2:42 PM, F
ya no kidding
On Tue, Apr 16, 2013 at 2:46 PM, Anis KADRI wrote:
> That's cool! I was getting tired of googling every apache conference since
> 1970.
>
>
> On Tue, Apr 16, 2013 at 2:42 PM, Filip Maj wrote:
>
> > Yep works! Thanks shaz
> >
> > also: no more super annoying "what city was apache
brianleroux
On Tue, Apr 16, 2013 at 2:42 PM, Filip Maj wrote:
> Yep works! Thanks shaz
>
> also: no more super annoying "what city was apache con 2004 held in?"
> questions. Double-win.
>
> On 4/16/13 2:39 PM, "Shazron" wrote:
>
> >Ok, I've added
> >- FilMaj
> >- AndrewGrieve
> >- MichaelBrook
That's cool! I was getting tired of googling every apache conference since
1970.
On Tue, Apr 16, 2013 at 2:42 PM, Filip Maj wrote:
> Yep works! Thanks shaz
>
> also: no more super annoying "what city was apache con 2004 held in?"
> questions. Double-win.
>
> On 4/16/13 2:39 PM, "Shazron" wrote
Yep works! Thanks shaz
also: no more super annoying "what city was apache con 2004 held in?"
questions. Double-win.
On 4/16/13 2:39 PM, "Shazron" wrote:
>Ok, I've added
>- FilMaj
>- AndrewGrieve
>- MichaelBrooks
>
>to the AdminGroup, please test whether you can edit.
>
>For the others, please r
For the GUI - I've started on something - only for new project create
though, with hopefully cordova-cli support in the future:
http://shazronatadobe.wordpress.com/2013/04/16/create-new-phonegapcordova-projects-using-cordova-create-gui/
On Tue, Apr 16, 2013 at 2:32 PM, Anis KADRI wrote:
> Thank
Ok, I've added
- FilMaj
- AndrewGrieve
- MichaelBrooks
to the AdminGroup, please test whether you can edit.
For the others, please reply with your wiki usernames so I can add you...
On Tue, Apr 16, 2013 at 10:14 AM, Shazron wrote:
> Nope, still no access :(
> I re-opened https://issues.apach
Yay wiki is back up so I will summarize this stuff in a new article there
On 4/16/13 2:29 PM, "Anis KADRI" wrote:
>I like fil's proposal. Either way, I don't think it should be an error, it
>should just be a warning. If if it's an error then when you have n
>platforms and one is not supported so
Thanks for your feedback! Our focus right now is on command line tools but
I hope one day someone will want to write graphical user interfaces for all
this stuff.
On Tue, Apr 16, 2013 at 1:54 PM, Aaron Charbonneau wrote:
> Plugman seemed pretty straight forward. There's alot of info in the Read
I like fil's proposal. Either way, I don't think it should be an error, it
should just be a warning. If if it's an error then when you have n
platforms and one is not supported some of them might not get the plugin
because one of them didn't get it (because unsupported).
On Tue, Apr 16, 2013 at 1
Plugman seemed pretty straight forward. There's alot of info in the Readme
about the plugin.xml file, but it was alot easier to understand it by
looking at a simple example like this one:
https://github.com/phonegap-build/GAPlugin/blob/master/plugin.xml
Perhaps having a simple example of the plug
To be clear: we are talking about plugman as functionality on its own.
Understandably the CLI will consume plugman and thus this is a good
behavior to make explicit.
So, how about this: if you specify installing a plugin into a platform it
doesn't support, the user will be WARNED, but plugman will
The main use-case is knowing at install time that your app isn't going to
work.
You're right though that there is a use-case for platform-specific plugins.
E.g. if (cordova.plugins.somePlugin) { .. use it ... } else { ... don't use
it ... }
Maybe a good first step is to issue a warning?
On Tue,
If you specify --platform ios for a plugin that does not support ios
it should be an error.
Cheers,
Jesse
Sent from my iPhone5
On 2013-04-16, at 12:12 PM, Braden Shepherdson wrote:
Why do you want errors when a plugin doesn't support a platform? Currently
this silently does nothing, and this
Why do you want errors when a plugin doesn't support a platform? Currently
this silently does nothing, and this is by design. Some plugins only
support some platforms, and that's fine. It just won't install on the
others it doesn't support.
Braden
On Tue, Apr 16, 2013 at 2:53 PM, Filip Maj wrot
awesome!
On Tue, Apr 16, 2013 at 2:38 PM, Brian LeRoux wrote:
> I'm down for this. (Given no plugins really work w/ it yet anyhow.)
>
>
> On Tue, Apr 16, 2013 at 11:28 AM, Michal Mocny
> wrote:
>
> > Should I also change cordova-cli in future to enable by default?
> >
> >
> > On Tue, Apr 16, 2
>Would like errors about trying to add a platform / plugin when the plugin
>doesn't support the platform.
Error out and stop, or warn about a mismatch?
>Idea: Add all plugins & platforms to config.xml, so instead of having to
>type "cordova plugin/platform add ..." for all plugins & platforms, y
Maybe toss that into the release article on the wiki so we have a paper
trail / written reminder of that?
On 4/16/13 11:50 AM, "Michal Mocny" wrote:
>Actually AppDelegate.m app template is written for non-arc, so I'll update
>the version bundled with cordova-cli to be arc friendly. We will need
Would like errors about trying to add a platform / plugin when the plugin
doesn't support the platform.
Idea: Add all plugins & platforms to config.xml, so instead of having to
type "cordova plugin/platform add ..." for all plugins & platforms, you can
list them in your config.xml and type "cordov
Actually AppDelegate.m app template is written for non-arc, so I'll update
the version bundled with cordova-cli to be arc friendly. We will need to
remember to redo this every time we copy a new ios project into
cordova-cli. Kinda sucks, but its temporary.
-Michal
On Tue, Apr 16, 2013 at 2:48
We will summarize baseline use cases for plugin management w.r.t.
dependencies on a wiki article (once wiki is usable again). From these we
can write tests that will drive our implementation work. Failure points we
already know are:
- asset collisions for native code and non-js web assets. We er
+1
On 4/16/13 7:52 PM, "Filip Maj" wrote:
>+1.
>
>So, how do we feel about starting an RC soon?
>
>On 4/16/13 10:19 AM, "Brian LeRoux" wrote:
>
>>It would be ideal to see 2.7 ship before the month is out for sure.
>>
>>
>>On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser wrote:
>>
>>> I think that t
I'm down for this. (Given no plugins really work w/ it yet anyhow.)
On Tue, Apr 16, 2013 at 11:28 AM, Michal Mocny wrote:
> Should I also change cordova-cli in future to enable by default?
>
>
> On Tue, Apr 16, 2013 at 2:23 PM, Brian LeRoux wrote:
>
> > plugin compat
> >
> >
> > On Tue, Apr 16
Should I also change cordova-cli in future to enable by default?
On Tue, Apr 16, 2013 at 2:23 PM, Brian LeRoux wrote:
> plugin compat
>
>
> On Tue, Apr 16, 2013 at 11:14 AM, James Jong wrote:
>
> > ARC was enabled and then later disabled previously. Does anyone remember
> > the reasons for th
plugin compat
On Tue, Apr 16, 2013 at 11:14 AM, James Jong wrote:
> ARC was enabled and then later disabled previously. Does anyone remember
> the reasons for that?
>
> -James Jong
>
> On Apr 16, 2013, at 2:07 PM, Lucas Holmquist wrote:
>
> > +1
> > On Apr 16, 2013, at 2:06 PM, Brian LeRoux
It breaks pretty much all existing plugins.
On Tue, Apr 16, 2013 at 2:14 PM, James Jong wrote:
> ARC was enabled and then later disabled previously. Does anyone remember
> the reasons for that?
>
> -James Jong
>
> On Apr 16, 2013, at 2:07 PM, Lucas Holmquist wrote:
>
> > +1
> > On Apr 16, 201
Sounds good! I'll throw out EOD tomorrow as a target. Has anyone got
anything that they want to get in before we cut?
On Tue, Apr 16, 2013 at 1:52 PM, Filip Maj wrote:
> +1.
>
> So, how do we feel about starting an RC soon?
>
> On 4/16/13 10:19 AM, "Brian LeRoux" wrote:
>
> >It would be ideal
ARC was enabled and then later disabled previously. Does anyone remember the
reasons for that?
-James Jong
On Apr 16, 2013, at 2:07 PM, Lucas Holmquist wrote:
> +1
> On Apr 16, 2013, at 2:06 PM, Brian LeRoux wrote:
>
>> sgtm
>>
>>
>> On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny wrote:
ok, cool
On Tue, Apr 16, 2013 at 1:42 AM, Jukka Zitting wrote:
> Hi,
>
> On Tue, Apr 16, 2013 at 12:51 AM, Brian LeRoux wrote:
> > Not totally sure why but I'm getting a message that we have a report for
> > April (even though I don't think we do b/c we should be quarterly.)
>
> It looks like t
+1
On Apr 16, 2013, at 2:06 PM, Brian LeRoux wrote:
> sgtm
>
>
> On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny wrote:
>
>> I think we plan to default to ARC support for iOS projects post 3.0.
>>
>> As a first transition I'm hoping to add a --arc option to the create script
>> to use optiona
sgtm
On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny wrote:
> I think we plan to default to ARC support for iOS projects post 3.0.
>
> As a first transition I'm hoping to add a --arc option to the create script
> to use optionally starting today, since its necessary for bleeding edge new
> style
Sounds good to me
On 4/16/13 10:58 AM, "Michal Mocny" wrote:
>I think we plan to default to ARC support for iOS projects post 3.0.
>
>As a first transition I'm hoping to add a --arc option to the create
>script
>to use optionally starting today, since its necessary for bleeding edge
>new
>style
+1
On Tue, Apr 16, 2013 at 2:03 PM, Shazron wrote:
> +1
>
>
> On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny wrote:
>
> > I think we plan to default to ARC support for iOS projects post 3.0.
> >
> > As a first transition I'm hoping to add a --arc option to the create
> script
> > to use option
+1
On Tue, Apr 16, 2013 at 10:58 AM, Michal Mocny wrote:
> I think we plan to default to ARC support for iOS projects post 3.0.
>
> As a first transition I'm hoping to add a --arc option to the create script
> to use optionally starting today, since its necessary for bleeding edge new
> style p
I think we plan to default to ARC support for iOS projects post 3.0.
As a first transition I'm hoping to add a --arc option to the create script
to use optionally starting today, since its necessary for bleeding edge new
style plugins/cli already.
Sound Good?
-Michal
Definitely.
It was deprecated in 2.6, so you have a while.
I will also investigate if it makes more sense to keep it, using your
plugin as a great use-case/
@purplecabbage
risingj.com
On Tue, Apr 16, 2013 at 10:35 AM, Don Coleman wrote:
> KeepCallback will work but requires API breaking chan
+1.
So, how do we feel about starting an RC soon?
On 4/16/13 10:19 AM, "Brian LeRoux" wrote:
>It would be ideal to see 2.7 ship before the month is out for sure.
>
>
>On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser wrote:
>
>> I think that this would be a good thing. It'd be nice to get a
>> rele
KeepCallback will work but requires API breaking change to my plugin across
all platforms. It seems like I need to do that at some point. Can you give
me a heads up before you remove InvokeCustomScript?
On Tue, Apr 16, 2013 at 1:14 PM, Jesse wrote:
> Hi Don,
>
> There is not a specific replace
Right on, how was the experience w/ Plugman? Anything we are missing /
should change?
On Mon, Apr 15, 2013 at 6:04 PM, Aaron Charbonneau wrote:
> Plugman is a pretty cool little tool! I was able to get the ScreenCapture
> plugin working with it fairly easily for both iOS and Android, here it is
It would be ideal to see 2.7 ship before the month is out for sure.
On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser wrote:
> I think that this would be a good thing. It'd be nice to get a
> released lined up for Conf-Month! (Adobe Max, Google IO, JSConf, etc).
>
> On Tue, Apr 16, 2013 at 7:35 AM,
Nope, still no access :(
I re-opened https://issues.apache.org/jira/browse/INFRA-6131
On Tue, Apr 16, 2013 at 12:07 AM, Jukka Zitting wrote:
> Hi,
>
> On Mon, Apr 15, 2013 at 9:51 PM, Shazron wrote:
> > But there is still a problem - I don't have access to these pages to add
> > people:
> > - h
Hi Don,
There is not a specific replacement, but using KeepCallback, you can
dispatch multiple results.
This may require a change in logic on the JS side.
PluginResult result = new PluginResult(PluginResult.Status.OK, DATA);
result.KeepCallback = true;
DispatchCommandResult(result);
Cheers,
J
I should also add. I appreciate that this is a change, and every change
has some learning overhead and we shouldn't stuff everything possible in
all the time.
However, I think 3.0 and cli are a big change, and we should do the big
re-org all at once, so lets decide this now in a way we wont regre
Okay, we've got options, so lets try to distill the details.
First, some of the other (perceived) benefits of an app folder are:
* we do a raw cp -r of the www/ folder, and so that should have only
platform agnostic and "necessary" files.
* merges folder was removed from www/ because it did not me
I think that this would be a good thing. It'd be nice to get a
released lined up for Conf-Month! (Adobe Max, Google IO, JSConf, etc).
On Tue, Apr 16, 2013 at 7:35 AM, Andrew Grieve wrote:
> Wanted to see what people thought of trying to get 2.7 out the door in time
> for Adobe Max. The main moti
Wanted to see what people thought of trying to get 2.7 out the door in time
for Adobe Max. The main motivation I see is to have a version that will
work the "future" branch of CLI. 2.6 is missing the plugin_loader.js code
required to load a plugin's JS.
You're right, it only looks at the host right now. We could change that
though.
On Mon, Apr 15, 2013 at 9:11 PM, Kevin Hawkins <
kevin.hawkins.cord...@gmail.com> wrote:
> Thanks Andrew. Content filtering may be a way to go, if that's possible.
> Is granular pattern-based whitelisting available
So, reading through the thread Braden linked to:
http://www.mail-archive.com/dev@cordova.apache.org/msg05775.html
There are two advantage that were brought up:
1. config.xml (configuration) does not live along side of app resources
2. It will make it easier to package apps
- E.g. zip the app/ di
+1 for adding Node in.
On Apr 15, 2013, at 1:33 PM, Brian LeRoux wrote:
> Yes, agree
>
>
> On Mon, Apr 15, 2013 at 10:12 AM, Filip Maj wrote:
>
>> The "free" maintenance is a compelling reason to add node as a dependency.
>>
>> I'll also flip and support this move but let's not focus on this
Hi,
On Tue, Apr 16, 2013 at 12:51 AM, Brian LeRoux wrote:
> Not totally sure why but I'm getting a message that we have a report for
> April (even though I don't think we do b/c we should be quarterly.)
It looks like the March report you submitted came too late for the
board to review it then, w
Hi,
On Mon, Apr 15, 2013 at 9:51 PM, Shazron wrote:
> But there is still a problem - I don't have access to these pages to add
> people:
> - http://wiki.apache.org/cordova/ContributorsGroup
> - http://wiki.apache.org/cordova/AdminGroup
>
> Thus, I think no one can edit/add any pages to the wiki a
55 matches
Mail list logo
