Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

rds Pieter Van Poyer -Oorspronkelijk bericht- Van: Niklas Apache Verzonden: woensdag 28 april 2021 12:14 Aan: dev@cordova.apache.org Onderwerp: Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10 I would agree with Bryan and Julio that we should

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

> > Pieter Van Poyer > > > > > > -----Oorspronkelijk bericht- > > Van: Niklas Apache > > Verzonden: woensdag 28 april 2021 12:14 > > Aan: dev@cordova.apache.org > > Onderwerp: Re: [DISCUSS] Moving forward with the WebView on AndroidX > &g

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

s Apache > Verzonden: woensdag 28 april 2021 12:14 > Aan: dev@cordova.apache.org > Onderwerp: Re: [DISCUSS] Moving forward with the WebView on AndroidX > and cordova-android 10 > > I would agree with Bryan and Julio that we should use the opportunity > of this breaking rel

RE: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

regards Pieter Van Poyer -Oorspronkelijk bericht- Van: Niklas Apache Verzonden: woensdag 28 april 2021 12:14 Aan: dev@cordova.apache.org Onderwerp: Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10 I would agree with Bryan and Julio that we should use

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

I would agree with Bryan and Julio that we should use the opportunity of this breaking release to move the defaults to current Android best practices and remove deprecated settings. I just started a PR [1] that introduces a preference to allow the use file URLs with this release. This means the

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

My understanding is that file urls can technically continue working, but the defaults changed and some settings need to be enabled, and some of them are now deprecated and will stop working at some point in the future. I think defaulting to the old behavior is ok when doing minor releases (not

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

To counter a bit, all of my apps are using the standard Cordova Android WebView, and store all their data in the browser's indexedDB. I've had no issues with file URLs (although I expect that will change with API 30 enforcement). Losing data in an app update is unacceptable, and for many apps it

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

I also agree. I think we should move forward with these changes and use the WebViewAssetLoader by default. If must, we could write a blog post explaining how to use Norman's plugin for data migration. But I do not know if the plugin is complete to cover all data sources and fits this case. I

Re: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

I would vote for defaulting to WebViewAssetLoader but still allow using file:// from a config.xml preference for the people that are not ready to move on. But on cordova-ios 6 I think we ended up defaulting to file:// and use the schemes only as opt-in. About migrating data, I don't think that's

[DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

Hey folks, we recently merged a PR [1] which significantly changes how cordova- android loads web content in the webview and now need to decide how to move proceed. Google introduced the WebViewAssetLoader to make it possible to use web content from a standard http(s) scheme instead of file:.

Re: [DISCUSS] Moving JIRA issues to Github

ues: the Issues section on GitHub. We already > have a lot of triage work on JIRA as it is. I doubt this will go down. > That said, I don't think that's necessarily bad. Will we have more > work? Probably. Will we be able to more easily identify issues, and > earlier, and generally be also

Re: [DISCUSS] Moving JIRA issues to Github

/ plugins). What do we do with those? Separate discussion? On Wed, Aug 2, 2017 at 5:32 PM, Connor Pearson <cjp...@gmail.com> wrote: I have a few questions about moving issues to GitHub. I haven’t used Github issues much so these all may be easily solvable. * Since it looks like not all reposito

Re: [DISCUSS] Moving JIRA issues to Github

f time? Yes. Different topic: Shaz, based on your INFRA ticket / phase breakdown, the implication is that there will be leftover cordova repos in Apache Git (cordova-medic, weinre, deprecated platforms / plugins). What do we do with those? Separate discussion? On Wed, Aug 2, 2017 at 5:32 PM, Connor Pearson <cjp...@

Re: [DISCUSS] Moving JIRA issues to Github

will be leftover cordova repos in Apache Git (cordova-medic, weinre, deprecated platforms / plugins). What do we do with those? Separate discussion? On Wed, Aug 2, 2017 at 5:32 PM, Connor Pearson <cjp...@gmail.com> wrote: I have a few questions about moving issues to GitHub. I haven’t

Re: [DISCUSS] Moving JIRA issues to Github

e now have a more >> >>> > obvious place to file issues: the Issues section on GitHub. We >> already >> >>> > have a lot of triage work on JIRA as it is. I doubt this will go >> down. >> >>> > That said, I don't think that's necess

Re: [DISCUSS] Moving JIRA issues to Github

t; >>> > work? Probably. Will we be able to more easily identify issues, and > >>> > earlier, and generally be also more accessible to our community? I > >>> > would think yes. Double-edged sword. I say let's see how it goes. > >>> > >

Re: [DISCUSS] Moving JIRA issues to Github

't think that's necessarily bad. Will we have more >>> > work? Probably. Will we be able to more easily identify issues, and >>> > earlier, and generally be also more accessible to our community? I >>> > would think yes. Double-edged sword. I say let's see how it goes. >

Re: [DISCUSS] Moving JIRA issues to Github

ed issues end >> up? >> > >> > They would end up in GitHub, at which point we'd triage them within >> GitHub. >> > >> >> Also if we enable Github issues before phase 2 are we going to be using >> both Jira and Github Issues for a period of

Re: [DISCUSS] Moving JIRA issues to Github

un-triaged issues end > > up? > > > > > > They would end up in GitHub, at which point we'd triage them within > > GitHub. > > > > > >> Also if we enable Github issues before phase 2 are we going to be > using > > both Jira and Github Is

Re: [DISCUSS] Moving JIRA issues to Github

ld end up in GitHub, at which point we'd triage them within > GitHub. > > > >> Also if we enable Github issues before phase 2 are we going to be using > both Jira and Github Issues for a period of time? > > > > Yes. > > > > Different topic: Shaz, based on you

Re: [DISCUSS] Moving JIRA issues to Github

hat there will be leftover cordova repos in Apache > Git (cordova-medic, weinre, deprecated platforms / plugins). What do > we do with those? Separate discussion? > > On Wed, Aug 2, 2017 at 5:32 PM, Connor Pearson <cjp...@gmail.com> wrote: >> I have a few questions abou

Re: [DISCUSS] Moving JIRA issues to Github

d triage them within GitHub. >> >> > Also if we enable Github issues before phase 2 are we going to be using >> both Jira and Github Issues for a period of time? >> >> Yes. >> >> Different topic: Shaz, based on your INFRA ticket / phase breakdown, >>

Re: [DISCUSS] Moving JIRA issues to Github

cket / phase breakdown, > the implication is that there will be leftover cordova repos in Apache > Git (cordova-medic, weinre, deprecated platforms / plugins). What do > we do with those? Separate discussion? > > On Wed, Aug 2, 2017 at 5:32 PM, Connor Pearson <cjp...@gmail.co

Re: [DISCUSS] Moving JIRA issues to Github

Connor Pearson <cjp...@gmail.com> wrote: > I have a few questions about moving issues to GitHub. I haven’t used Github > issues much so these all may be easily solvable. > > * Since it looks like not all repositories will be migrated where should > their issues go? What abo

Re: [DISCUSS] Moving JIRA issues to Github

I have a few questions about moving issues to GitHub. I haven’t used Github issues much so these all may be easily solvable. * Since it looks like not all repositories will be migrated where should their issues go? What about issues for repositories that don’t yet exist or cross-cutting issues

Re: [DISCUSS] Moving JIRA issues to Github

t;> On 2 August 2017 at 12:38, Shazron <shaz...@apache.org> wrote: >> >>> Phase 1 of our move to Github is complete, see: >>> https://issues.apache.org/jira/browse/INFRA-14347 >>> >>> We need a migration plan for moving JIRA issues to Github Issue

Re: [DISCUSS] Moving JIRA issues to Github

e in > JIRA. > > On 2 August 2017 at 12:38, Shazron <shaz...@apache.org> wrote: > >> Phase 1 of our move to Github is complete, see: >> https://issues.apache.org/jira/browse/INFRA-14347 >> >> We need a migration plan for moving JIRA issues to Github Issu

Re: [DISCUSS] Moving JIRA issues to Github

an insurmountable chore leading to a worse backlog than we already have in JIRA. On 2 August 2017 at 12:38, Shazron <shaz...@apache.org> wrote: > Phase 1 of our move to Github is complete, see: > https://issues.apache.org/jira/browse/INFRA-14347 > > We need a migration plan for

[DISCUSS] Moving JIRA issues to Github

Phase 1 of our move to Github is complete, see: https://issues.apache.org/jira/browse/INFRA-14347 We need a migration plan for moving JIRA issues to Github Issues before we enable Github Issues on those repos. Once we figure those out, we can proceed with Phase 2: https

Re: Cloudapp CI is down, builds moving to Travis

Sent: Wednesday, June 21, 2017 7:49 PM > To: dev@cordova.apache.org > Subject: Re: Cloudapp CI is down, builds moving to Travis > > I know Sauce Connect pretty well from my days working at Sauce Labs :) > > Not sure if appropriate for the dev list - if not, message me on slack

RE: Cloudapp CI is down, builds moving to Travis

- From: Filip Maj [mailto:maj@gmail.com] Sent: Wednesday, June 21, 2017 7:49 PM To: dev@cordova.apache.org Subject: Re: Cloudapp CI is down, builds moving to Travis I know Sauce Connect pretty well from my days working at Sauce Labs :) Not sure if appropriate for the dev list - if not, message

Re: Cloudapp CI is down, builds moving to Travis

you have > any insight on that, I'd be glad to hear it. > > -Original Message- > From: Filip Maj [mailto:maj@gmail.com] > Sent: Wednesday, June 21, 2017 4:33 PM > To: dev@cordova.apache.org > Subject: Re: Cloudapp CI is down, builds moving to Travis > > Any JIRA i

RE: Cloudapp CI is down, builds moving to Travis

these builds, so if you have any insight on that, I'd be glad to hear it. -Original Message- From: Filip Maj [mailto:maj@gmail.com] Sent: Wednesday, June 21, 2017 4:33 PM To: dev@cordova.apache.org Subject: Re: Cloudapp CI is down, builds moving to Travis Any JIRA issues we should look

Re: Cloudapp CI is down, builds moving to Travis

Any JIRA issues we should look at to track progress? Alex, what can we do to assist? seems like a lot of work - let us know! On Wed, Jun 21, 2017 at 5:39 AM, wrote: > Our Plugins testing CI (Jenkins) is officially dead now. > We're migrating all the jobs to Travis and

Cloudapp CI is down, builds moving to Travis

Our Plugins testing CI (Jenkins) is officially dead now. We're migrating all the jobs to Travis and AppVeyor, but for the time being, all PRs to the plugin repos are not being tested. I'm working to enable Travis and AppVeyor builds as soon as possible, but there are some unexpected hassle with

Re: [NOTICE] Intent on moving to Github

I created this Discuss document regarding which platforms/plugins are moving: https://github.com/cordova/cordova-discuss/blob/master/proposals/GithubMove.md On Tue, Jun 13, 2017 at 12:57 PM, Shazron <shaz...@gmail.com> wrote: > Thanks Carlos. > > I just filed https://issues.

Re: [NOTICE] Intent on moving to Github

.@gmail.com> wrote: > >> > > > The Apache Cordova Project Management Committee (PMC) has > consensus > >> > that > >> > > we > >> > > > should move primary development of Apache Cordova to Github, from > >> &g

Re: [NOTICE] Intent on moving to Github

that >> > > we >> > > > should move primary development of Apache Cordova to Github, from >> > > Apache's >> > > > servers (role would be reversed, Apache would then be the mirror >> now). >> > > > >> > > >

Re: [NOTICE] Intent on moving to Github

pull requests through Github, although > > without > > > > write access we couldn't label, or close PRs directly. Enabling of > > Issues > > > > in Github (to replace JIRA) would be a separate matter, and would > > likely > > > be > >

Re: [NOTICE] Intent on moving to Github

t > > > write access we couldn't label, or close PRs directly. Enabling of > Issues > > > in Github (to replace JIRA) would be a separate matter, and would > likely > > be > > > on a per-repo basis. > > > > > > Moving is achieved

Re: [NOTICE] Intent on moving to Github

> > write access we couldn't label, or close PRs directly. Enabling of Issues > > in Github (to replace JIRA) would be a separate matter, and would likely > be > > on a per-repo basis. > > > > Moving is achieved by invitation to the Apache Gitbox project: > >

Re: [NOTICE] Intent on moving to Github

d, Apache would then be the mirror now). > > We are already processing pull requests through Github, although without > write access we couldn't label, or close PRs directly. Enabling of Issues > in Github (to replace JIRA) would be a separate matter, and would likely be > o

[NOTICE] Intent on moving to Github

write access we couldn't label, or close PRs directly. Enabling of Issues in Github (to replace JIRA) would be a separate matter, and would likely be on a per-repo basis. Moving is achieved by invitation to the Apache Gitbox project: https://gitbox.apache.org/ (don't get excited if you can log

Moving towards cordova 7

We are getting a pretty big collection of tooling PRs [1] that are related to cordova-7 [2] Over the next couple days we'll be working on merging these and resolving any conflicts, so expect master to be occasionally broken, and you may need to rebase some of your work. Cheers, Jesse [1]

Re: [WEBSITE] Moving from SVN to Git

https://issues.apache.org/jira/browse/CB-12229 On Thu, Dec 8, 2016 at 1:55 PM, Steven Gill wrote: > sweet! I'm always down for us to move away from svn to git based services. > > On Thu, Dec 8, 2016 at 10:16 AM, Shazron wrote: > > >

Re: [WEBSITE] Moving from SVN to Git

sweet! I'm always down for us to move away from svn to git based services. On Thu, Dec 8, 2016 at 10:16 AM, Shazron wrote: > https://blogs.apache.org/infra/entry/git_based_websites_available > > Apparently this option was available. Currently we have cordova-docs, where > we

[WEBSITE] Moving from SVN to Git

https://blogs.apache.org/infra/entry/git_based_websites_available Apparently this option was available. Currently we have cordova-docs, where we generate, then copy over to our svn repo. Not super efficient.

[GitHub] cordova-plugin-camera pull request: Moving message in PR template ...

Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-plugin-camera/pull/215#issuecomment-219137585 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] cordova-plugin-camera pull request: Moving message in PR template ...

Github user riknoll commented on the pull request: https://github.com/apache/cordova-plugin-camera/pull/215#issuecomment-219136559 I wonder if we should shorten the commit message bullet so that it doesn't wrap lines like that? Maybe we can link to

[GitHub] cordova-plugin-camera pull request: Moving message in PR template ...

Github user riknoll commented on the pull request: https://github.com/apache/cordova-plugin-camera/pull/215#issuecomment-219136048 @nikhilkh please review --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] cordova-plugin-camera pull request: Moving message in PR template ...

GitHub user riknoll opened a pull request: https://github.com/apache/cordova-plugin-camera/pull/215 Moving message in PR template to a comment ### Platforms affected None! ### What does this PR do? Change the template that I am currently filling out so

[GitHub] cordova-docs pull request: Moving analytics script to head

Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/596 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] cordova-docs pull request: Moving analytics script to head

Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-docs/pull/596#issuecomment-217948218 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] cordova-docs pull request: Moving analytics script to head

GitHub user riknoll opened a pull request: https://github.com/apache/cordova-docs/pull/596 Moving analytics script to head It looks like it got moved in a refactor. It needs to be in the head of every page to work properly according to this: https://support.google.com/analytics

Re: Discuss: Moving current 'dev' documentation to 6.x

Tweet: https://twitter.com/apachecordova/status/707280829299302400 On Tue, Mar 8, 2016 at 10:25 AM, Shazron wrote: > +++1 Excellent work > Kudos to the team that did this! > > On Tue, Mar 8, 2016 at 8:41 AM, Carlos Santana > wrote: > > Can someone tweet

Re: Discuss: Moving current 'dev' documentation to 6.x

+++1 Excellent work Kudos to the team that did this! On Tue, Mar 8, 2016 at 8:41 AM, Carlos Santana wrote: > Can someone tweet the blog post [1] for the new doc improvements from the > @apachecordova twitter account ? > > New Docs improvements are amazing +100 :-) > > [1]:

Re: Discuss: Moving current 'dev' documentation to 6.x

Can someone tweet the blog post [1] for the new doc improvements from the @apachecordova twitter account ? New Docs improvements are amazing +100 :-) [1]: http://cordova.apache.org/announcements/2016/03/03/docs-improvement.html On Fri, Mar 4, 2016 at 7:56 PM Dmitry Blotsky

[GitHub] cordova-docs pull request: Moving dev to 6.x

Github user rakatyal commented on the pull request: https://github.com/apache/cordova-docs/pull/537#issuecomment-193443047 Yup this will make them access the platform guides for other languages as well. --- If your project is set up for it, you can reply to this email and have your

[GitHub] cordova-docs pull request: Moving dev to 6.x

Github user rakatyal commented on the pull request: https://github.com/apache/cordova-docs/pull/537#issuecomment-193441996 They were added to dev and now they are being added to 6.x --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] cordova-docs pull request: Moving dev to 6.x

Github user dblotsky commented on the pull request: https://github.com/apache/cordova-docs/pull/537#issuecomment-193441267 @rakatyal if they were part of a previous commit then please rebase this branch on top of master so that they don't show up in this PR. --- If your project is

[GitHub] cordova-docs pull request: Moving dev to 6.x

Github user rakatyal commented on the pull request: https://github.com/apache/cordova-docs/pull/537#issuecomment-192542631 Yes. They were added as part of [this](https://github.com/apache/cordova-docs/pull/507/files) commit. We added landing pages for guides which we didn't make

[GitHub] cordova-docs pull request: Moving dev to 6.x

Github user dblotsky commented on the pull request: https://github.com/apache/cordova-docs/pull/537#issuecomment-192540964 @rakatyal it looks like some pages were added to other languages than English. Was this intentional? --- If your project is set up for it, you can reply to this

[GitHub] cordova-docs pull request: Moving dev to 6.x

Github user dblotsky commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/537#discussion_r55110503 --- Diff: www/docs/de/6.x/guide/platforms/blackberry10/home.md --- @@ -0,0 +1,29 @@ +--- +license: > +Licensed to the Apache Software

Re: Discuss: Moving current 'dev' documentation to 6.x

Hey folks, Just bringing up an important note: this change is only coming to English. Other languages will not get the change and they will still have older content that looks different even though the version is the same (6.x). Are we okay with this change in user experience? Kindly, Dmitry

Re: Discuss: Moving current 'dev' documentation to 6.x

+1 On Thu, Mar 3, 2016 at 3:15 PM, Raghav Katyal wrote: > Hi everyone! > > I am planning to move the current dev version of our documentation to > 6.x(latest) version. We have done a significant amount of work to improve our > documentation and I have also written a

Re: Discuss: Moving current 'dev' documentation to 6.x

Looks great! Awesome job Raghav and everyone else who was involved in this initiative! Big improvement! On Thu, Mar 3, 2016 at 3:15 PM, Raghav Katyal wrote: > Hi everyone! > > I am planning to move the current dev version of our documentation to > 6.x(latest) version. We

Discuss: Moving current 'dev' documentation to 6.x

Hi everyone! I am planning to move the current dev version of our documentation to 6.x(latest) version. We have done a significant amount of work to improve our documentation and I have also written a blog post summarizing them. Please review them if you would like. Blog PR:

[GitHub] cordova-docs pull request: Moving dev to 6.x

GitHub user rakatyal opened a pull request: https://github.com/apache/cordova-docs/pull/537 Moving dev to 6.x You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs raghav-dev Alternatively you can review

Re: [iOS 8] WKWebView moving forward

I would certainly like to see a test to see what the lag is like... --  tommy-carlos williams On 11 June 2015 at 02:01:35, Shazron (shaz...@gmail.com) wrote: Safari View Controller video: https://developer.apple.com/videos/wwdc/2015/?id=504 What's New in Web Development in WebKit and

Re: [iOS 8] WKWebView moving forward

I don't see moving the files to document out from bundle to documents on first lunch as terrible thing. It can be implemented in the mean while. In our downstream district of cordova this is how we handle dynamic app update from server since bundle is read only. But agree best solution

Re: [iOS 8] WKWebView moving forward

Could maybe try creating symlinks / hardlinks to save on space / creation time? On Wed, Jun 10, 2015 at 12:00 PM, Shazron shaz...@gmail.com wrote: Safari View Controller video: https://developer.apple.com/videos/wwdc/2015/?id=504 What's New in Web Development in WebKit and Safari video:

RE: [iOS 8] WKWebView moving forward

a potential issue if platforms are referenced in package.json.) -Chuck -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Thursday, June 11, 2015 11:27 AM To: dev Subject: Re: [iOS 8] WKWebView moving forward Could maybe try creating

Re: [iOS 8] WKWebView moving forward

I've already tried both sym and hard links. They result in errors, which is to be expected (if not there's some 'splaining to do) :P GOOD news though today! They are fixing the app bundle loadFileURL bug: https://twitter.com/grorgwork/status/609052546179530752 Apparently you can also UI test in

Re: [iOS 8] WKWebView moving forward

Yeah, I was just about to say that I was pretty sure that sym/hard links was going to error. But that tweet looks promising! I hope that means the fix makes it in time for Beta 2 so we can play with it. :-) On June 11, 2015 at 1:55:58 PM, Shazron (shaz...@gmail.com) wrote: I've already

Re: [iOS 8] WKWebView moving forward

Safari View Controller video: https://developer.apple.com/videos/wwdc/2015/?id=504 What's New in Web Development in WebKit and Safari video: https://developer.apple.com/videos/wwdc/2015/?id=501 On Tue, Jun 9, 2015 at 3:59 PM, Shazron shaz...@gmail.com wrote: I definitely will watch. Just

Re: [iOS 8] WKWebView moving forward

Yay ! There is also a new Safari View Controller, don't know if it's applicable to replace wkwebview but at least I think it can be use to build the next gen inappbrowser since its beats a makeup in iOS anyway. The session is in 30 minutes so I'm planning attending. On Mon, Jun 8, 2015 at 2:33 PM

Re: [iOS 8] WKWebView moving forward

We could use it for InAppBrowser but we might lose some features that we have possibly. Anyways, one piece of bad news for WKWebView iOS 9 - you can load file urls in Library and Documents, but not the app bundle. https://twitter.com/wkwebview/status/608359163299819521 On Tue, Jun 9, 2015 at

Re: [iOS 8] WKWebView moving forward

Here's the juicy Safari iOS 9 bits, including new javascript and css features, including SFSafariViewController: https://developer.apple.com/library/prerelease/mac/releasenotes/General/WhatsNewInSafari/Articles/Safari_9.html On Tue, Jun 9, 2015 at 1:22 PM, Shazron shaz...@gmail.com wrote: We

Re: [iOS 8] WKWebView moving forward

IndexedDB news is looking a bit bleak: https://gist.github.com/nolanlawson/08eb857c6b17a30c1b26 On 9 June 2015 at 13:28, Shazron shaz...@gmail.com wrote: Here's the juicy Safari iOS 9 bits, including new javascript and css features, including SFSafariViewController:

Re: [iOS 8] WKWebView moving forward

Speaking as a user who has an iPhone that’s always running near the storage limit: I’d hate to see files be duplicate out of the bundle into another location… my phone might cry. I think we went over that when WKWebview was first released. Copying files was discussed, but it adds an awful lot

Re: [iOS 8] WKWebView moving forward

+1 to what Kerri said. If we did it, it would be in Library/Caches since that is not backed up by iTunes: https://developer.apple.com/library/ios/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html#//apple_ref/doc/uid/TP40010672-CH2-SW1 On

Re: [iOS 8] WKWebView moving forward

I hadn’t considered the space issue. Mind you, my apps are like 1.7MB. Not exactly space hogs. At least the camera and downloads issues would be fixed :( --  tommy-carlos williams On 10 June 2015 at 07:04:00, Shazron (shaz...@gmail.com) wrote: +1 to what Kerri said. If we did it, it would be

Re: [iOS 8] WKWebView moving forward

Would it be a horrible idea to copy files into one of those folders? On Tue, Jun 9, 2015 at 3:22 PM, Shazron shaz...@gmail.com wrote: We could use it for InAppBrowser but we might lose some features that we have possibly. Anyways, one piece of bad news for WKWebView iOS 9 - you can load file

Re: [iOS 8] WKWebView moving forward

I definitely will watch. Just read about ODR https://developer.apple.com/library/prerelease/ios/documentation/FileManagement/Conceptual/On_Demand_Resources_Guide/Chapters/IntroToODR.html#//apple_ref/doc/uid/TP40015083-CH2-SW1 So we could still use the copy method (fast, small app bundle) and have

Re: [iOS 8] WKWebView moving forward

What do we loose, I just attended the session. I think for most uses is a win at least in the security aspect Watch the session when the video is available and we can discuss later. On Tue, Jun 9, 2015 at 1:23 PM Shazron shaz...@gmail.com wrote: We could use it for InAppBrowser but we might

Re: [iOS 8] WKWebView moving forward

Any news on IndexedDB bug fixes? Or working URL interceptors? On 8 June 2015 at 13:13, Shazron shaz...@gmail.com wrote: Cordova developers rejoice, iOS 9 includes the API to load pages from file:// urls https://twitter.com/wkwebview/status/608002548151119872 On Mon, Feb 9, 2015 at 2:19 PM,

Re: [iOS 8] WKWebView moving forward

Moar news https://twitter.com/wkwebview/status/608005652720451584 On Monday, June 8, 2015, Shazron shaz...@gmail.com wrote: Cordova developers rejoice, iOS 9 includes the API to load pages from file:// urls https://twitter.com/wkwebview/status/608002548151119872 On Mon, Feb 9, 2015 at 2:19

Re: [iOS 8] WKWebView moving forward

Cordova developers rejoice, iOS 9 includes the API to load pages from file:// urls https://twitter.com/wkwebview/status/608002548151119872 On Mon, Feb 9, 2015 at 2:19 PM, Shazron shaz...@gmail.com wrote: Also Xcode 6.3 now *requires* Yosemite. Fair warning to upgrade I suppose for your dev

Re: [iOS 8] WKWebView moving forward

There is a WWDC session: Safari Extensibility: Content Blocking and Shared Links. So I'm hopeful for whitelisting On Mon, Jun 8, 2015 at 1:22 PM, Shazron shaz...@gmail.com wrote: Moar news https://twitter.com/wkwebview/status/608005652720451584 On Monday, June 8, 2015, Shazron

Re: [iOS 8] WKWebView moving forward

No idea yet Darryl On Monday, June 8, 2015, Darryl Pogue dar...@dpogue.ca wrote: Any news on IndexedDB bug fixes? Or working URL interceptors? On 8 June 2015 at 13:13, Shazron shaz...@gmail.com javascript:; wrote: Cordova developers rejoice, iOS 9 includes the API to load pages from

Re: [iOS 8] WKWebView moving forward

Why am I hearing the Hallelujah chorus? I’m dong my happy dance now! :-) On June 8, 2015 at 3:14:14 PM, Shazron (shaz...@gmail.com) wrote: Cordova developers rejoice, iOS 9 includes the API to load pages from file:// urls https://twitter.com/wkwebview/status/608002548151119872 On Mon,

Re: [DISCUSS] Moving Rat Excludes closer to source

sgtm! On Fri, May 29, 2015 at 9:05 PM, Dmitry Blotsky dblot...@microsoft.com wrote: Hi all, Right now coho stores rat excludes inside its source code, which often goes out of date and we end up with a lot of noise in coho audit-license-headers”. Do you think it would be a good idea to

Re: [DISCUSS] Moving Rat Excludes closer to source

+1 @purplecabbage risingj.com On Mon, Jun 1, 2015 at 11:13 AM, Steven Gill stevengil...@gmail.com wrote: Do it! On Jun 1, 2015 7:28 AM, Andrew Grieve agri...@chromium.org wrote: sgtm! On Fri, May 29, 2015 at 9:05 PM, Dmitry Blotsky dblot...@microsoft.com wrote: Hi all,

Re: [DISCUSS] Moving Rat Excludes closer to source

Do it! On Jun 1, 2015 7:28 AM, Andrew Grieve agri...@chromium.org wrote: sgtm! On Fri, May 29, 2015 at 9:05 PM, Dmitry Blotsky dblot...@microsoft.com wrote: Hi all, Right now coho stores rat excludes inside its source code, which often goes out of date and we end up with a lot of

[DISCUSS] Moving Rat Excludes closer to source

Hi all, Right now coho stores rat excludes inside its source code, which often goes out of date and we end up with a lot of noise in coho audit-license-headers”. Do you think it would be a good idea to instead add a “.ratignore” file in each repo, much like .npmignore and .gitignore? Kindly,

Re: Also moving to a new team

LeRoux b...@brian.io wrote: really appreciate the level headed contributions to our community and code Marcel Staci; glad to have had the chance to work with you both! On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard cmarc...@gmail.com wrote: Staci Cooper and I are also moving to new

Re: FYI - Moving to new team, seeing me less around here

-Original Message- From: Andrey Kurdumov [mailto:kant2...@googlemail.com] Sent: Monday, May 4, 2015 7:40 PM To: dev@cordova.apache.org Subject: Re: FYI - Moving to new team, seeing me less around here Congratulations, Physical Web sounds promising,enjoy you new project! 2015-05-05 3

Re: Also moving to a new team

Staci Cooper and I are also moving to new positions. There already are backfills here coming up to speed: Karen Tran and James Dubee. You'll be seeing more of them here as time moves forward, joining Edna Morales. Awe, no Marcel! You've had a huge impact on this project and brought a level

Re: Also moving to a new team

Staci Cooper and I are also moving to new positions. There already are backfills here coming up to speed: Karen Tran and James Dubee. You'll be seeing more of them here as time moves forward, joining Edna Morales. This has been an absolutely awesome group to work with. You're smart, talented

Re: Also moving to a new team

Sorry to see you moving on Marcel, and Staci. Your presence will be missed, you have done a lot here. Best of luck in your new roles. btw, you each deserve your own threads! Cheers, Jesse @purplecabbage risingj.com On Thu, May 7, 2015 at 11:36 AM, Michael Brooks mich...@michaelbrooks.ca

  1   2   3   >