Re: WKWebView and iOS 9
Welp, screwed up -- asked for commits to be sent to dev@ instead of commits@! sorry! On Tue, Sep 8, 2015 at 12:17 PM, Shazron wrote: > Requested new repo: https://issues.apache.org/jira/browse/INFRA-10392 > > On Thu, Aug 27, 2015 at 2:13 PM, Shazron wrote: > >> Awesome! >> >> Filed: >> https://issues.apache.org/jira/browse/CB-9566 >> https://issues.apache.org/jira/browse/CB-9567 >> >> Overall board: >> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=76 >> >> >> On Wed, Aug 26, 2015 at 8:02 AM, Kerri Shotts >> wrote: >> >>> No objections at all. :) >>> >>> Kerri Shotts , photoKandy Studios LLC >>> >>> http://www.photokandy.com/ • @photokandy >>> >>> → CONFIDENTIAL ← >>> >>> This email and any attachments may be confidential. If you are not the >>> intended recipient, please let us know by replying to this message, and >>> then remove the message and its attachments from your system. You should >>> not disseminate, distribute, or otherwise copy or release the information >>> contained herein, nor can we accept any liability for any loss or damages >>> resulting from the use, abuse, or mis-use of the information contained >>> herein. >>> >>> → SECURITY ← >>> >>> Computer viruses can be distributed via email. It is the recipient’s >>> responsibility to check this email and any attachments for viruses. Email >>> transmission cannot be guaranteed to be secure or error-free as the email >>> could have been intercepted, corrupted, delayed, and/or re-transmitted. The >>> sender does not accept any liability for errors or omissions within this >>> message or its attachments, nor for any viruses which may be present. >>> >>> Note: We do our very best to ensure that nothing we send contains >>> viruses. However, because of the nature of email and the way it is sent, we >>> can’t promise that some other party hasn’t intercepted our email and added >>> malicious content. Due to the nature of email, we can’t accept any >>> liability for any damage or loss arising from the use, abuse, or mis-use of >>> this email and any of its attachments. >>> >>> → PRIVACY ← >>> >>> Email is not a secure communications medium. When replying to this or >>> any message, you should not include any information that you do not want >>> the entire world to be capable of seeing. In other words, don’t send >>> financial accounts (CC#s, Bank Account #s, etc.), passwords, social >>> security numbers, or the like, even when asked directly. photoKandy Studios >>> LLC will never ask you for this information. >>> >>> Information transmitted via email may be intercepted and retransmitted >>> by any number of other entities. This is the nature of email, and as such, >>> we can’t be held liable for any loss or damage incurred by replying to this >>> message with compromising information. Review your message prior to sending >>> it, and ensure that there is no information you wouldn’t be comfortable >>> with the entire world knowing. >>> >>> >>> >>> >>> >>> >>> On Tue, Aug 25, 2015 at 2:20 PM -0700, "Shazron" >>> wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I'm going to move onto the 2 plugin idea if there are no objections. This >>> will preserve the existing plugin into a newly named plugin. >>> >>> On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana >>> wrote: >>> >>> > I like much better your naming suggestions for the plugins >>> > >>> > - Carlos >>> > Sent from my iPhone >>> > >>> > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: >>> > > >>> > > I like the two plugin idea. >>> > > >>> > > Using file:// would be the recommended and default, iOS 9 only -- and >>> > this >>> > > should be wkwebview-engine >>> > > Using the local webserver -- and this could be >>> > > wkwebview-engine-local-webserver >>> > > >>> > > >>> > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana >>> > > wrote: >>> > > >>> > >> What about 2 plugins? >>> > >> >>> > >> Maybe more clear for the developer can add one or the other >>> > >> >>> > >> wkengine-file (only supported on iOS 9+) >>> > >> wkengine-webserver (only supported iOS8, iOS9 and higher) >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> People that don't want to use the webserver might be annoyed to >>> have >>> > dead >>> > >> code link. >>> > >> >>> > >> - Carlos >>> > >> Sent from my iPhone >>> > >> >>> > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: >>> > >>> >>> > >>> Ok re-capping the proposal, we need to move on this: >>> > >>> >>> > >>> 1. Recommend UIWebView usage on iOS 8 and below >>> > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) >>> and >>> > >> the >>> > >>> plugin will support this >>> > >>> 3. WKWebView usage using local web server supported through a >>> > preference >>> > >>> (will only work on iOS 8 and above) >>> > >>> >>> > >>> As a consequence of #3: >>> > >>> a) The local webserver plugin will always be installed when you >>> install >>> > >> the >>> > >>> wkwebview-engine plugin >>> > >>> b) The local webserver plugin code will be always be lin
Re: WKWebView and iOS 9
Requested new repo: https://issues.apache.org/jira/browse/INFRA-10392 On Thu, Aug 27, 2015 at 2:13 PM, Shazron wrote: > Awesome! > > Filed: > https://issues.apache.org/jira/browse/CB-9566 > https://issues.apache.org/jira/browse/CB-9567 > > Overall board: > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=76 > > > On Wed, Aug 26, 2015 at 8:02 AM, Kerri Shotts > wrote: > >> No objections at all. :) >> >> Kerri Shotts , photoKandy Studios LLC >> >> http://www.photokandy.com/ • @photokandy >> >> → CONFIDENTIAL ← >> >> This email and any attachments may be confidential. If you are not the >> intended recipient, please let us know by replying to this message, and >> then remove the message and its attachments from your system. You should >> not disseminate, distribute, or otherwise copy or release the information >> contained herein, nor can we accept any liability for any loss or damages >> resulting from the use, abuse, or mis-use of the information contained >> herein. >> >> → SECURITY ← >> >> Computer viruses can be distributed via email. It is the recipient’s >> responsibility to check this email and any attachments for viruses. Email >> transmission cannot be guaranteed to be secure or error-free as the email >> could have been intercepted, corrupted, delayed, and/or re-transmitted. The >> sender does not accept any liability for errors or omissions within this >> message or its attachments, nor for any viruses which may be present. >> >> Note: We do our very best to ensure that nothing we send contains >> viruses. However, because of the nature of email and the way it is sent, we >> can’t promise that some other party hasn’t intercepted our email and added >> malicious content. Due to the nature of email, we can’t accept any >> liability for any damage or loss arising from the use, abuse, or mis-use of >> this email and any of its attachments. >> >> → PRIVACY ← >> >> Email is not a secure communications medium. When replying to this or any >> message, you should not include any information that you do not want the >> entire world to be capable of seeing. In other words, don’t send financial >> accounts (CC#s, Bank Account #s, etc.), passwords, social security numbers, >> or the like, even when asked directly. photoKandy Studios LLC will never >> ask you for this information. >> >> Information transmitted via email may be intercepted and retransmitted by >> any number of other entities. This is the nature of email, and as such, we >> can’t be held liable for any loss or damage incurred by replying to this >> message with compromising information. Review your message prior to sending >> it, and ensure that there is no information you wouldn’t be comfortable >> with the entire world knowing. >> >> >> >> >> >> >> On Tue, Aug 25, 2015 at 2:20 PM -0700, "Shazron" >> wrote: >> >> >> >> >> >> >> >> >> >> >> I'm going to move onto the 2 plugin idea if there are no objections. This >> will preserve the existing plugin into a newly named plugin. >> >> On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana >> wrote: >> >> > I like much better your naming suggestions for the plugins >> > >> > - Carlos >> > Sent from my iPhone >> > >> > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: >> > > >> > > I like the two plugin idea. >> > > >> > > Using file:// would be the recommended and default, iOS 9 only -- and >> > this >> > > should be wkwebview-engine >> > > Using the local webserver -- and this could be >> > > wkwebview-engine-local-webserver >> > > >> > > >> > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana >> > > wrote: >> > > >> > >> What about 2 plugins? >> > >> >> > >> Maybe more clear for the developer can add one or the other >> > >> >> > >> wkengine-file (only supported on iOS 9+) >> > >> wkengine-webserver (only supported iOS8, iOS9 and higher) >> > >> >> > >> >> > >> >> > >> >> > >> People that don't want to use the webserver might be annoyed to have >> > dead >> > >> code link. >> > >> >> > >> - Carlos >> > >> Sent from my iPhone >> > >> >> > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: >> > >>> >> > >>> Ok re-capping the proposal, we need to move on this: >> > >>> >> > >>> 1. Recommend UIWebView usage on iOS 8 and below >> > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) >> and >> > >> the >> > >>> plugin will support this >> > >>> 3. WKWebView usage using local web server supported through a >> > preference >> > >>> (will only work on iOS 8 and above) >> > >>> >> > >>> As a consequence of #3: >> > >>> a) The local webserver plugin will always be installed when you >> install >> > >> the >> > >>> wkwebview-engine plugin >> > >>> b) The local webserver plugin code will be always be linked into >> your >> > app >> > >>> executable, so the symbols will always be there. There will be no >> > >>> runtime/memory impact if the pref is off >> > >>> c) we can't make local-webserver dependency depend on iOS 8 only, >> some >> > >>> would want to use #3 for iOS 8 and above, f
Re: WKWebView and iOS 9
Awesome! Filed: https://issues.apache.org/jira/browse/CB-9566 https://issues.apache.org/jira/browse/CB-9567 Overall board: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=76 On Wed, Aug 26, 2015 at 8:02 AM, Kerri Shotts wrote: > No objections at all. :) > > Kerri Shotts , photoKandy Studios LLC > > http://www.photokandy.com/ • @photokandy > > → CONFIDENTIAL ← > > This email and any attachments may be confidential. If you are not the > intended recipient, please let us know by replying to this message, and > then remove the message and its attachments from your system. You should > not disseminate, distribute, or otherwise copy or release the information > contained herein, nor can we accept any liability for any loss or damages > resulting from the use, abuse, or mis-use of the information contained > herein. > > → SECURITY ← > > Computer viruses can be distributed via email. It is the recipient’s > responsibility to check this email and any attachments for viruses. Email > transmission cannot be guaranteed to be secure or error-free as the email > could have been intercepted, corrupted, delayed, and/or re-transmitted. The > sender does not accept any liability for errors or omissions within this > message or its attachments, nor for any viruses which may be present. > > Note: We do our very best to ensure that nothing we send contains viruses. > However, because of the nature of email and the way it is sent, we can’t > promise that some other party hasn’t intercepted our email and added > malicious content. Due to the nature of email, we can’t accept any > liability for any damage or loss arising from the use, abuse, or mis-use of > this email and any of its attachments. > > → PRIVACY ← > > Email is not a secure communications medium. When replying to this or any > message, you should not include any information that you do not want the > entire world to be capable of seeing. In other words, don’t send financial > accounts (CC#s, Bank Account #s, etc.), passwords, social security numbers, > or the like, even when asked directly. photoKandy Studios LLC will never > ask you for this information. > > Information transmitted via email may be intercepted and retransmitted by > any number of other entities. This is the nature of email, and as such, we > can’t be held liable for any loss or damage incurred by replying to this > message with compromising information. Review your message prior to sending > it, and ensure that there is no information you wouldn’t be comfortable > with the entire world knowing. > > > > > > > On Tue, Aug 25, 2015 at 2:20 PM -0700, "Shazron" > wrote: > > > > > > > > > > > I'm going to move onto the 2 plugin idea if there are no objections. This > will preserve the existing plugin into a newly named plugin. > > On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana > wrote: > > > I like much better your naming suggestions for the plugins > > > > - Carlos > > Sent from my iPhone > > > > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: > > > > > > I like the two plugin idea. > > > > > > Using file:// would be the recommended and default, iOS 9 only -- and > > this > > > should be wkwebview-engine > > > Using the local webserver -- and this could be > > > wkwebview-engine-local-webserver > > > > > > > > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana > > > wrote: > > > > > >> What about 2 plugins? > > >> > > >> Maybe more clear for the developer can add one or the other > > >> > > >> wkengine-file (only supported on iOS 9+) > > >> wkengine-webserver (only supported iOS8, iOS9 and higher) > > >> > > >> > > >> > > >> > > >> People that don't want to use the webserver might be annoyed to have > > dead > > >> code link. > > >> > > >> - Carlos > > >> Sent from my iPhone > > >> > > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: > > >>> > > >>> Ok re-capping the proposal, we need to move on this: > > >>> > > >>> 1. Recommend UIWebView usage on iOS 8 and below > > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) > and > > >> the > > >>> plugin will support this > > >>> 3. WKWebView usage using local web server supported through a > > preference > > >>> (will only work on iOS 8 and above) > > >>> > > >>> As a consequence of #3: > > >>> a) The local webserver plugin will always be installed when you > install > > >> the > > >>> wkwebview-engine plugin > > >>> b) The local webserver plugin code will be always be linked into your > > app > > >>> executable, so the symbols will always be there. There will be no > > >>> runtime/memory impact if the pref is off > > >>> c) we can't make local-webserver dependency depend on iOS 8 only, > some > > >>> would want to use #3 for iOS 8 and above, for example > > >>> > > >>> > > >>> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > > >> jcesarmob...@gmail.com> > > >>> wrote: > > >>> > > You are right, sorry, I haven't looked into the pluggable webviews > > yet. > > > > After looking into the WKWebVie
Re: WKWebView and iOS 9
No objections at all. :) Kerri Shotts , photoKandy Studios LLC http://www.photokandy.com/ • @photokandy → CONFIDENTIAL ← This email and any attachments may be confidential. If you are not the intended recipient, please let us know by replying to this message, and then remove the message and its attachments from your system. You should not disseminate, distribute, or otherwise copy or release the information contained herein, nor can we accept any liability for any loss or damages resulting from the use, abuse, or mis-use of the information contained herein. → SECURITY ← Computer viruses can be distributed via email. It is the recipient’s responsibility to check this email and any attachments for viruses. Email transmission cannot be guaranteed to be secure or error-free as the email could have been intercepted, corrupted, delayed, and/or re-transmitted. The sender does not accept any liability for errors or omissions within this message or its attachments, nor for any viruses which may be present. Note: We do our very best to ensure that nothing we send contains viruses. However, because of the nature of email and the way it is sent, we can’t promise that some other party hasn’t intercepted our email and added malicious content. Due to the nature of email, we can’t accept any liability for any damage or loss arising from the use, abuse, or mis-use of this email and any of its attachments. → PRIVACY ← Email is not a secure communications medium. When replying to this or any message, you should not include any information that you do not want the entire world to be capable of seeing. In other words, don’t send financial accounts (CC#s, Bank Account #s, etc.), passwords, social security numbers, or the like, even when asked directly. photoKandy Studios LLC will never ask you for this information. Information transmitted via email may be intercepted and retransmitted by any number of other entities. This is the nature of email, and as such, we can’t be held liable for any loss or damage incurred by replying to this message with compromising information. Review your message prior to sending it, and ensure that there is no information you wouldn’t be comfortable with the entire world knowing. On Tue, Aug 25, 2015 at 2:20 PM -0700, "Shazron" wrote: I'm going to move onto the 2 plugin idea if there are no objections. This will preserve the existing plugin into a newly named plugin. On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana wrote: > I like much better your naming suggestions for the plugins > > - Carlos > Sent from my iPhone > > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: > > > > I like the two plugin idea. > > > > Using file:// would be the recommended and default, iOS 9 only -- and > this > > should be wkwebview-engine > > Using the local webserver -- and this could be > > wkwebview-engine-local-webserver > > > > > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana > > wrote: > > > >> What about 2 plugins? > >> > >> Maybe more clear for the developer can add one or the other > >> > >> wkengine-file (only supported on iOS 9+) > >> wkengine-webserver (only supported iOS8, iOS9 and higher) > >> > >> > >> > >> > >> People that don't want to use the webserver might be annoyed to have > dead > >> code link. > >> > >> - Carlos > >> Sent from my iPhone > >> > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: > >>> > >>> Ok re-capping the proposal, we need to move on this: > >>> > >>> 1. Recommend UIWebView usage on iOS 8 and below > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and > >> the > >>> plugin will support this > >>> 3. WKWebView usage using local web server supported through a > preference > >>> (will only work on iOS 8 and above) > >>> > >>> As a consequence of #3: > >>> a) The local webserver plugin will always be installed when you install > >> the > >>> wkwebview-engine plugin > >>> b) The local webserver plugin code will be always be linked into your > app > >>> executable, so the symbols will always be there. There will be no > >>> runtime/memory impact if the pref is off > >>> c) we can't make local-webserver dependency depend on iOS 8 only, some > >>> would want to use #3 for iOS 8 and above, for example > >>> > >>> > >>> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > >> jcesarmob...@gmail.com> > >>> wrote: > >>> > You are right, sorry, I haven't looked into the pluggable webviews > yet. > > After looking into the WKWebView engine plugin I've seen that the > local > webserver is a dependency, I thought it was included inside the plugin > >> (as > the one from Eddy). > > So, the way to go is remove the dependency and make it only available > >> for > iOS 9? and if the user want to use it on iOS 8 then he install the > webserver plugin manually and maybe add a preference on the WKWebView > engine plugin? or is there a way that the preference (or an instal
Re: WKWebView and iOS 9
+1 - Carlos Sent from my iPhone > On Aug 26, 2015, at 1:48 AM, julio cesar sanchez > wrote: > > +1 > > 2015-08-26 7:39 GMT+02:00 tommy-carlos williams : > >> +1 >> >> >> On 26 August 2015 at 07:20:18, Shazron (shaz...@gmail.com) wrote: >> >> I'm going to move onto the 2 plugin idea if there are no objections. This >> will preserve the existing plugin into a newly named plugin. >> >> On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana >> wrote: >> >>> I like much better your naming suggestions for the plugins >>> >>> - Carlos >>> Sent from my iPhone >>> On Aug 24, 2015, at 4:17 PM, Shazron wrote: I like the two plugin idea. Using file:// would be the recommended and default, iOS 9 only -- and >>> this should be wkwebview-engine Using the local webserver -- and this could be wkwebview-engine-local-webserver On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana wrote: > What about 2 plugins? > > Maybe more clear for the developer can add one or the other > > wkengine-file (only supported on iOS 9+) > wkengine-webserver (only supported iOS8, iOS9 and higher) > > > > > People that don't want to use the webserver might be annoyed to have >>> dead > code link. > > - Carlos > Sent from my iPhone > >> On Aug 20, 2015, at 3:11 PM, Shazron wrote: >> >> Ok re-capping the proposal, we need to move on this: >> >> 1. Recommend UIWebView usage on iOS 8 and below >> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) >> and > the >> plugin will support this >> 3. WKWebView usage using local web server supported through a >>> preference >> (will only work on iOS 8 and above) >> >> As a consequence of #3: >> a) The local webserver plugin will always be installed when you >> install > the >> wkwebview-engine plugin >> b) The local webserver plugin code will be always be linked into your >>> app >> executable, so the symbols will always be there. There will be no >> runtime/memory impact if the pref is off >> c) we can't make local-webserver dependency depend on iOS 8 only, >> some >> would want to use #3 for iOS 8 and above, for example >> >> >> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > jcesarmob...@gmail.com> >> wrote: >> >>> You are right, sorry, I haven't looked into the pluggable webviews >>> yet. >>> >>> After looking into the WKWebView engine plugin I've seen that the >>> local >>> webserver is a dependency, I thought it was included inside the >> plugin > (as >>> the one from Eddy). >>> >>> So, the way to go is remove the dependency and make it only >> available > for >>> iOS 9? and if the user want to use it on iOS 8 then he install the >>> webserver plugin manually and maybe add a preference on the >> WKWebView >>> engine plugin? or is there a way that the preference (or an install > param) >>> can install the webserver plugin with a hook or something? >>> >>> >>> 2015-08-05 8:30 GMT+02:00 Shazron : >>> I don't think that is a good idea. The reason why WKWebView is a >>> plugin >>> is the faster update cycle. This is the total point of the new 4.x > release: pluggable webviews. If the current UIWebView implementation is >> buggy, someone could *potentially* update that also. On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < jcesarmob...@gmail.com> wrote: > My idea: > > Make iOS 9 use WKWebView as default without plugin and iOS 8 and >>> previous > use UIWebView, then if people want WKWebView on iOS 8 they install >>> the > existing plugin with the webserver > > 2015-08-05 5:54 GMT+02:00 Shazron : > >> +1 Carlos >> >>> On Wednesday, August 5, 2015, Carlos Santana < >>> csantan...@gmail.com> >> wrote: >> >>> I would like to see by default or configuration setting be able >> to have >>> that combination "WKWebView plugin only works on iOS 9 and older iOSes >>> fallback to UIWebView" >>> >>> I can already hear customers asking too many questions about >>> running a >>> webserver inside their app (i.e. security, energy, old hacks on their >> own >>> custom plugins, etc). I prefer to have the option to tell them >>> it's a >>> choice it's very easy to select to not have a webserver at all. >>> >>> - Carlos >>> Sent from my iPhone >>> On Aug 4, 2015, at 8:16 PM, Shazron > >>> wrote: My thinking -- It'll be a hybrid approach - iOS 8 uses >> local-web >>>
Re: WKWebView and iOS 9
+1 2015-08-26 7:39 GMT+02:00 tommy-carlos williams : > +1 > > > On 26 August 2015 at 07:20:18, Shazron (shaz...@gmail.com) wrote: > > I'm going to move onto the 2 plugin idea if there are no objections. This > will preserve the existing plugin into a newly named plugin. > > On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana > wrote: > > > I like much better your naming suggestions for the plugins > > > > - Carlos > > Sent from my iPhone > > > > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: > > > > > > I like the two plugin idea. > > > > > > Using file:// would be the recommended and default, iOS 9 only -- and > > this > > > should be wkwebview-engine > > > Using the local webserver -- and this could be > > > wkwebview-engine-local-webserver > > > > > > > > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana > > > wrote: > > > > > >> What about 2 plugins? > > >> > > >> Maybe more clear for the developer can add one or the other > > >> > > >> wkengine-file (only supported on iOS 9+) > > >> wkengine-webserver (only supported iOS8, iOS9 and higher) > > >> > > >> > > >> > > >> > > >> People that don't want to use the webserver might be annoyed to have > > dead > > >> code link. > > >> > > >> - Carlos > > >> Sent from my iPhone > > >> > > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: > > >>> > > >>> Ok re-capping the proposal, we need to move on this: > > >>> > > >>> 1. Recommend UIWebView usage on iOS 8 and below > > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) > and > > >> the > > >>> plugin will support this > > >>> 3. WKWebView usage using local web server supported through a > > preference > > >>> (will only work on iOS 8 and above) > > >>> > > >>> As a consequence of #3: > > >>> a) The local webserver plugin will always be installed when you > install > > >> the > > >>> wkwebview-engine plugin > > >>> b) The local webserver plugin code will be always be linked into your > > app > > >>> executable, so the symbols will always be there. There will be no > > >>> runtime/memory impact if the pref is off > > >>> c) we can't make local-webserver dependency depend on iOS 8 only, > some > > >>> would want to use #3 for iOS 8 and above, for example > > >>> > > >>> > > >>> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > > >> jcesarmob...@gmail.com> > > >>> wrote: > > >>> > > You are right, sorry, I haven't looked into the pluggable webviews > > yet. > > > > After looking into the WKWebView engine plugin I've seen that the > > local > > webserver is a dependency, I thought it was included inside the > plugin > > >> (as > > the one from Eddy). > > > > So, the way to go is remove the dependency and make it only > available > > >> for > > iOS 9? and if the user want to use it on iOS 8 then he install the > > webserver plugin manually and maybe add a preference on the > WKWebView > > engine plugin? or is there a way that the preference (or an install > > >> param) > > can install the webserver plugin with a hook or something? > > > > > > 2015-08-05 8:30 GMT+02:00 Shazron : > > > > > I don't think that is a good idea. The reason why WKWebView is a > > plugin > > is > > > the faster update cycle. This is the total point of the new 4.x > > >> release: > > > pluggable webviews. If the current UIWebView implementation is > buggy, > > > someone could *potentially* update that also. > > > > > > On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > > > jcesarmob...@gmail.com> > > > wrote: > > > > > >> My idea: > > >> > > >> Make iOS 9 use WKWebView as default without plugin and iOS 8 and > > previous > > >> use UIWebView, then if people want WKWebView on iOS 8 they install > > the > > >> existing plugin with the webserver > > >> > > >> 2015-08-05 5:54 GMT+02:00 Shazron : > > >> > > >>> +1 Carlos > > >>> > > On Wednesday, August 5, 2015, Carlos Santana < > > csantan...@gmail.com> > > >>> wrote: > > >>> > > I would like to see by default or configuration setting be able > to > > > have > > that combination "WKWebView plugin only works on iOS 9 and older > > > iOSes > > fallback to UIWebView" > > > > I can already hear customers asking too many questions about > > running > > > a > > webserver inside their app (i.e. security, energy, old hacks on > > > their > > >>> own > > custom plugins, etc). I prefer to have the option to tell them > > it's a > > choice it's very easy to select to not have a webserver at all. > > > > - Carlos > > Sent from my iPhone > > > > > On Aug 4, 2015, at 8:16 PM, Shazron > >> > > > wrote: > > > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses > local-web > > >>> server, > > > iOS 9 doesn't. We'll
Re: WKWebView and iOS 9
+1 On 26 August 2015 at 07:20:18, Shazron (shaz...@gmail.com) wrote: I'm going to move onto the 2 plugin idea if there are no objections. This will preserve the existing plugin into a newly named plugin. On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana wrote: > I like much better your naming suggestions for the plugins > > - Carlos > Sent from my iPhone > > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: > > > > I like the two plugin idea. > > > > Using file:// would be the recommended and default, iOS 9 only -- and > this > > should be wkwebview-engine > > Using the local webserver -- and this could be > > wkwebview-engine-local-webserver > > > > > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana > > wrote: > > > >> What about 2 plugins? > >> > >> Maybe more clear for the developer can add one or the other > >> > >> wkengine-file (only supported on iOS 9+) > >> wkengine-webserver (only supported iOS8, iOS9 and higher) > >> > >> > >> > >> > >> People that don't want to use the webserver might be annoyed to have > dead > >> code link. > >> > >> - Carlos > >> Sent from my iPhone > >> > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: > >>> > >>> Ok re-capping the proposal, we need to move on this: > >>> > >>> 1. Recommend UIWebView usage on iOS 8 and below > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and > >> the > >>> plugin will support this > >>> 3. WKWebView usage using local web server supported through a > preference > >>> (will only work on iOS 8 and above) > >>> > >>> As a consequence of #3: > >>> a) The local webserver plugin will always be installed when you install > >> the > >>> wkwebview-engine plugin > >>> b) The local webserver plugin code will be always be linked into your > app > >>> executable, so the symbols will always be there. There will be no > >>> runtime/memory impact if the pref is off > >>> c) we can't make local-webserver dependency depend on iOS 8 only, some > >>> would want to use #3 for iOS 8 and above, for example > >>> > >>> > >>> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > >> jcesarmob...@gmail.com> > >>> wrote: > >>> > You are right, sorry, I haven't looked into the pluggable webviews > yet. > > After looking into the WKWebView engine plugin I've seen that the > local > webserver is a dependency, I thought it was included inside the plugin > >> (as > the one from Eddy). > > So, the way to go is remove the dependency and make it only available > >> for > iOS 9? and if the user want to use it on iOS 8 then he install the > webserver plugin manually and maybe add a preference on the WKWebView > engine plugin? or is there a way that the preference (or an install > >> param) > can install the webserver plugin with a hook or something? > > > 2015-08-05 8:30 GMT+02:00 Shazron : > > > I don't think that is a good idea. The reason why WKWebView is a > plugin > is > > the faster update cycle. This is the total point of the new 4.x > >> release: > > pluggable webviews. If the current UIWebView implementation is buggy, > > someone could *potentially* update that also. > > > > On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > > jcesarmob...@gmail.com> > > wrote: > > > >> My idea: > >> > >> Make iOS 9 use WKWebView as default without plugin and iOS 8 and > previous > >> use UIWebView, then if people want WKWebView on iOS 8 they install > the > >> existing plugin with the webserver > >> > >> 2015-08-05 5:54 GMT+02:00 Shazron : > >> > >>> +1 Carlos > >>> > On Wednesday, August 5, 2015, Carlos Santana < > csantan...@gmail.com> > >>> wrote: > >>> > I would like to see by default or configuration setting be able to > > have > that combination "WKWebView plugin only works on iOS 9 and older > > iOSes > fallback to UIWebView" > > I can already hear customers asking too many questions about > running > > a > webserver inside their app (i.e. security, energy, old hacks on > > their > >>> own > custom plugins, etc). I prefer to have the option to tell them > it's a > choice it's very easy to select to not have a webserver at all. > > - Carlos > Sent from my iPhone > > > On Aug 4, 2015, at 8:16 PM, Shazron >> > > wrote: > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > >>> server, > > iOS 9 doesn't. We'll have to support both if the dev deploys to > an > >>> older > > target (the final fallback is UIWebView) > > > > Either that or WKWebView plugin only works on iOS 9 and older > iOSe
Re: WKWebView and iOS 9
I'm going to move onto the 2 plugin idea if there are no objections. This will preserve the existing plugin into a newly named plugin. On Mon, Aug 24, 2015 at 3:24 PM, Carlos Santana wrote: > I like much better your naming suggestions for the plugins > > - Carlos > Sent from my iPhone > > > On Aug 24, 2015, at 4:17 PM, Shazron wrote: > > > > I like the two plugin idea. > > > > Using file:// would be the recommended and default, iOS 9 only -- and > this > > should be wkwebview-engine > > Using the local webserver -- and this could be > > wkwebview-engine-local-webserver > > > > > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana > > wrote: > > > >> What about 2 plugins? > >> > >> Maybe more clear for the developer can add one or the other > >> > >> wkengine-file (only supported on iOS 9+) > >> wkengine-webserver (only supported iOS8, iOS9 and higher) > >> > >> > >> > >> > >> People that don't want to use the webserver might be annoyed to have > dead > >> code link. > >> > >> - Carlos > >> Sent from my iPhone > >> > >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: > >>> > >>> Ok re-capping the proposal, we need to move on this: > >>> > >>> 1. Recommend UIWebView usage on iOS 8 and below > >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and > >> the > >>> plugin will support this > >>> 3. WKWebView usage using local web server supported through a > preference > >>> (will only work on iOS 8 and above) > >>> > >>> As a consequence of #3: > >>> a) The local webserver plugin will always be installed when you install > >> the > >>> wkwebview-engine plugin > >>> b) The local webserver plugin code will be always be linked into your > app > >>> executable, so the symbols will always be there. There will be no > >>> runtime/memory impact if the pref is off > >>> c) we can't make local-webserver dependency depend on iOS 8 only, some > >>> would want to use #3 for iOS 8 and above, for example > >>> > >>> > >>> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > >> jcesarmob...@gmail.com> > >>> wrote: > >>> > You are right, sorry, I haven't looked into the pluggable webviews > yet. > > After looking into the WKWebView engine plugin I've seen that the > local > webserver is a dependency, I thought it was included inside the plugin > >> (as > the one from Eddy). > > So, the way to go is remove the dependency and make it only available > >> for > iOS 9? and if the user want to use it on iOS 8 then he install the > webserver plugin manually and maybe add a preference on the WKWebView > engine plugin? or is there a way that the preference (or an install > >> param) > can install the webserver plugin with a hook or something? > > > 2015-08-05 8:30 GMT+02:00 Shazron : > > > I don't think that is a good idea. The reason why WKWebView is a > plugin > is > > the faster update cycle. This is the total point of the new 4.x > >> release: > > pluggable webviews. If the current UIWebView implementation is buggy, > > someone could *potentially* update that also. > > > > On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > > jcesarmob...@gmail.com> > > wrote: > > > >> My idea: > >> > >> Make iOS 9 use WKWebView as default without plugin and iOS 8 and > previous > >> use UIWebView, then if people want WKWebView on iOS 8 they install > the > >> existing plugin with the webserver > >> > >> 2015-08-05 5:54 GMT+02:00 Shazron : > >> > >>> +1 Carlos > >>> > On Wednesday, August 5, 2015, Carlos Santana < > csantan...@gmail.com> > >>> wrote: > >>> > I would like to see by default or configuration setting be able to > > have > that combination "WKWebView plugin only works on iOS 9 and older > > iOSes > fallback to UIWebView" > > I can already hear customers asking too many questions about > running > > a > webserver inside their app (i.e. security, energy, old hacks on > > their > >>> own > custom plugins, etc). I prefer to have the option to tell them > it's a > choice it's very easy to select to not have a webserver at all. > > - Carlos > Sent from my iPhone > > > On Aug 4, 2015, at 8:16 PM, Shazron >> > > wrote: > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > >>> server, > > iOS 9 doesn't. We'll have to support both if the dev deploys to > an > >>> older > > target (the final fallback is UIWebView) > > > > Either that or WKWebView plugin only works on iOS 9 and older > iOSes > > fallback to UIWebView. > > > >> On Wednesday, August 5, 2015, Edna Y Morales < > eymor...@us.ibm.com > > wrote: > >> > >> > >> Hi all, > >>
Re: WKWebView and iOS 9
I like much better your naming suggestions for the plugins - Carlos Sent from my iPhone > On Aug 24, 2015, at 4:17 PM, Shazron wrote: > > I like the two plugin idea. > > Using file:// would be the recommended and default, iOS 9 only -- and this > should be wkwebview-engine > Using the local webserver -- and this could be > wkwebview-engine-local-webserver > > > On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana > wrote: > >> What about 2 plugins? >> >> Maybe more clear for the developer can add one or the other >> >> wkengine-file (only supported on iOS 9+) >> wkengine-webserver (only supported iOS8, iOS9 and higher) >> >> >> >> >> People that don't want to use the webserver might be annoyed to have dead >> code link. >> >> - Carlos >> Sent from my iPhone >> >>> On Aug 20, 2015, at 3:11 PM, Shazron wrote: >>> >>> Ok re-capping the proposal, we need to move on this: >>> >>> 1. Recommend UIWebView usage on iOS 8 and below >>> 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and >> the >>> plugin will support this >>> 3. WKWebView usage using local web server supported through a preference >>> (will only work on iOS 8 and above) >>> >>> As a consequence of #3: >>> a) The local webserver plugin will always be installed when you install >> the >>> wkwebview-engine plugin >>> b) The local webserver plugin code will be always be linked into your app >>> executable, so the symbols will always be there. There will be no >>> runtime/memory impact if the pref is off >>> c) we can't make local-webserver dependency depend on iOS 8 only, some >>> would want to use #3 for iOS 8 and above, for example >>> >>> >>> On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < >> jcesarmob...@gmail.com> >>> wrote: >>> You are right, sorry, I haven't looked into the pluggable webviews yet. After looking into the WKWebView engine plugin I've seen that the local webserver is a dependency, I thought it was included inside the plugin >> (as the one from Eddy). So, the way to go is remove the dependency and make it only available >> for iOS 9? and if the user want to use it on iOS 8 then he install the webserver plugin manually and maybe add a preference on the WKWebView engine plugin? or is there a way that the preference (or an install >> param) can install the webserver plugin with a hook or something? 2015-08-05 8:30 GMT+02:00 Shazron : > I don't think that is a good idea. The reason why WKWebView is a plugin is > the faster update cycle. This is the total point of the new 4.x >> release: > pluggable webviews. If the current UIWebView implementation is buggy, > someone could *potentially* update that also. > > On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > jcesarmob...@gmail.com> > wrote: > >> My idea: >> >> Make iOS 9 use WKWebView as default without plugin and iOS 8 and previous >> use UIWebView, then if people want WKWebView on iOS 8 they install the >> existing plugin with the webserver >> >> 2015-08-05 5:54 GMT+02:00 Shazron : >> >>> +1 Carlos >>> On Wednesday, August 5, 2015, Carlos Santana >>> wrote: >>> I would like to see by default or configuration setting be able to > have that combination "WKWebView plugin only works on iOS 9 and older > iOSes fallback to UIWebView" I can already hear customers asking too many questions about running > a webserver inside their app (i.e. security, energy, old hacks on > their >>> own custom plugins, etc). I prefer to have the option to tell them it's a choice it's very easy to select to not have a webserver at all. - Carlos Sent from my iPhone > On Aug 4, 2015, at 8:16 PM, Shazron > > wrote: > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web >>> server, > iOS 9 doesn't. We'll have to support both if the dev deploys to an >>> older > target (the final fallback is UIWebView) > > Either that or WKWebView plugin only works on iOS 9 and older iOSes > fallback to UIWebView. > >> On Wednesday, August 5, 2015, Edna Y Morales < eymor...@us.ibm.com > wrote: >> >> >> Hi all, >> >> Since the file:// url loading bug was fixed for WKWebView in iOS > 9, >>> are we >> going to move away from the local webserver solution? >> >> Thanks, >> Edna Morales - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >>> For additional commands, e-mail: dev-h...@cordova.apache.org >> >> ---
Re: WKWebView and iOS 9
I like the two plugin idea. Using file:// would be the recommended and default, iOS 9 only -- and this should be wkwebview-engine Using the local webserver -- and this could be wkwebview-engine-local-webserver On Thu, Aug 20, 2015 at 2:42 PM, Carlos Santana wrote: > What about 2 plugins? > > Maybe more clear for the developer can add one or the other > > wkengine-file (only supported on iOS 9+) > wkengine-webserver (only supported iOS8, iOS9 and higher) > > > > > People that don't want to use the webserver might be annoyed to have dead > code link. > > - Carlos > Sent from my iPhone > > > On Aug 20, 2015, at 3:11 PM, Shazron wrote: > > > > Ok re-capping the proposal, we need to move on this: > > > > 1. Recommend UIWebView usage on iOS 8 and below > > 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and > the > > plugin will support this > > 3. WKWebView usage using local web server supported through a preference > > (will only work on iOS 8 and above) > > > > As a consequence of #3: > > a) The local webserver plugin will always be installed when you install > the > > wkwebview-engine plugin > > b) The local webserver plugin code will be always be linked into your app > > executable, so the symbols will always be there. There will be no > > runtime/memory impact if the pref is off > > c) we can't make local-webserver dependency depend on iOS 8 only, some > > would want to use #3 for iOS 8 and above, for example > > > > > > On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez < > jcesarmob...@gmail.com> > > wrote: > > > >> You are right, sorry, I haven't looked into the pluggable webviews yet. > >> > >> After looking into the WKWebView engine plugin I've seen that the local > >> webserver is a dependency, I thought it was included inside the plugin > (as > >> the one from Eddy). > >> > >> So, the way to go is remove the dependency and make it only available > for > >> iOS 9? and if the user want to use it on iOS 8 then he install the > >> webserver plugin manually and maybe add a preference on the WKWebView > >> engine plugin? or is there a way that the preference (or an install > param) > >> can install the webserver plugin with a hook or something? > >> > >> > >> 2015-08-05 8:30 GMT+02:00 Shazron : > >> > >>> I don't think that is a good idea. The reason why WKWebView is a plugin > >> is > >>> the faster update cycle. This is the total point of the new 4.x > release: > >>> pluggable webviews. If the current UIWebView implementation is buggy, > >>> someone could *potentially* update that also. > >>> > >>> On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > >>> jcesarmob...@gmail.com> > >>> wrote: > >>> > My idea: > > Make iOS 9 use WKWebView as default without plugin and iOS 8 and > >> previous > use UIWebView, then if people want WKWebView on iOS 8 they install the > existing plugin with the webserver > > 2015-08-05 5:54 GMT+02:00 Shazron : > > > +1 Carlos > > > >> On Wednesday, August 5, 2015, Carlos Santana > > wrote: > > > >> I would like to see by default or configuration setting be able to > >>> have > >> that combination "WKWebView plugin only works on iOS 9 and older > >>> iOSes > >> fallback to UIWebView" > >> > >> I can already hear customers asking too many questions about > >> running > >>> a > >> webserver inside their app (i.e. security, energy, old hacks on > >>> their > > own > >> custom plugins, etc). I prefer to have the option to tell them > >> it's a > >> choice it's very easy to select to not have a webserver at all. > >> > >> - Carlos > >> Sent from my iPhone > >> > >>> On Aug 4, 2015, at 8:16 PM, Shazron > > >> wrote: > >>> > >>> My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > > server, > >>> iOS 9 doesn't. We'll have to support both if the dev deploys to > >> an > > older > >>> target (the final fallback is UIWebView) > >>> > >>> Either that or WKWebView plugin only works on iOS 9 and older > >> iOSes > >>> fallback to UIWebView. > >>> > On Wednesday, August 5, 2015, Edna Y Morales < > >> eymor...@us.ibm.com > >> > wrote: > > > Hi all, > > Since the file:// url loading bug was fixed for WKWebView in iOS > >>> 9, > > are > >> we > going to move away from the local webserver solution? > > Thanks, > Edna Morales > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > >> For additional commands, e-mail: dev-h...@cordova.apache.org > >> > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: WKWebView and iOS 9
What about 2 plugins? Maybe more clear for the developer can add one or the other wkengine-file (only supported on iOS 9+) wkengine-webserver (only supported iOS8, iOS9 and higher) People that don't want to use the webserver might be annoyed to have dead code link. - Carlos Sent from my iPhone > On Aug 20, 2015, at 3:11 PM, Shazron wrote: > > Ok re-capping the proposal, we need to move on this: > > 1. Recommend UIWebView usage on iOS 8 and below > 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and the > plugin will support this > 3. WKWebView usage using local web server supported through a preference > (will only work on iOS 8 and above) > > As a consequence of #3: > a) The local webserver plugin will always be installed when you install the > wkwebview-engine plugin > b) The local webserver plugin code will be always be linked into your app > executable, so the symbols will always be there. There will be no > runtime/memory impact if the pref is off > c) we can't make local-webserver dependency depend on iOS 8 only, some > would want to use #3 for iOS 8 and above, for example > > > On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez > wrote: > >> You are right, sorry, I haven't looked into the pluggable webviews yet. >> >> After looking into the WKWebView engine plugin I've seen that the local >> webserver is a dependency, I thought it was included inside the plugin (as >> the one from Eddy). >> >> So, the way to go is remove the dependency and make it only available for >> iOS 9? and if the user want to use it on iOS 8 then he install the >> webserver plugin manually and maybe add a preference on the WKWebView >> engine plugin? or is there a way that the preference (or an install param) >> can install the webserver plugin with a hook or something? >> >> >> 2015-08-05 8:30 GMT+02:00 Shazron : >> >>> I don't think that is a good idea. The reason why WKWebView is a plugin >> is >>> the faster update cycle. This is the total point of the new 4.x release: >>> pluggable webviews. If the current UIWebView implementation is buggy, >>> someone could *potentially* update that also. >>> >>> On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < >>> jcesarmob...@gmail.com> >>> wrote: >>> My idea: Make iOS 9 use WKWebView as default without plugin and iOS 8 and >> previous use UIWebView, then if people want WKWebView on iOS 8 they install the existing plugin with the webserver 2015-08-05 5:54 GMT+02:00 Shazron : > +1 Carlos > >> On Wednesday, August 5, 2015, Carlos Santana > wrote: > >> I would like to see by default or configuration setting be able to >>> have >> that combination "WKWebView plugin only works on iOS 9 and older >>> iOSes >> fallback to UIWebView" >> >> I can already hear customers asking too many questions about >> running >>> a >> webserver inside their app (i.e. security, energy, old hacks on >>> their > own >> custom plugins, etc). I prefer to have the option to tell them >> it's a >> choice it's very easy to select to not have a webserver at all. >> >> - Carlos >> Sent from my iPhone >> >>> On Aug 4, 2015, at 8:16 PM, Shazron >>> > >> wrote: >>> >>> My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > server, >>> iOS 9 doesn't. We'll have to support both if the dev deploys to >> an > older >>> target (the final fallback is UIWebView) >>> >>> Either that or WKWebView plugin only works on iOS 9 and older >> iOSes >>> fallback to UIWebView. >>> On Wednesday, August 5, 2015, Edna Y Morales < >> eymor...@us.ibm.com >> > wrote: Hi all, Since the file:// url loading bug was fixed for WKWebView in iOS >>> 9, > are >> we going to move away from the local webserver solution? Thanks, Edna Morales >> - >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> For additional commands, e-mail: dev-h...@cordova.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: WKWebView and iOS 9
Ok re-capping the proposal, we need to move on this: 1. Recommend UIWebView usage on iOS 8 and below 2. Recommend WKWebView usage on iOS 9 only (using file:// loading) and the plugin will support this 3. WKWebView usage using local web server supported through a preference (will only work on iOS 8 and above) As a consequence of #3: a) The local webserver plugin will always be installed when you install the wkwebview-engine plugin b) The local webserver plugin code will be always be linked into your app executable, so the symbols will always be there. There will be no runtime/memory impact if the pref is off c) we can't make local-webserver dependency depend on iOS 8 only, some would want to use #3 for iOS 8 and above, for example On Wed, Aug 5, 2015 at 3:15 PM, julio cesar sanchez wrote: > You are right, sorry, I haven't looked into the pluggable webviews yet. > > After looking into the WKWebView engine plugin I've seen that the local > webserver is a dependency, I thought it was included inside the plugin (as > the one from Eddy). > > So, the way to go is remove the dependency and make it only available for > iOS 9? and if the user want to use it on iOS 8 then he install the > webserver plugin manually and maybe add a preference on the WKWebView > engine plugin? or is there a way that the preference (or an install param) > can install the webserver plugin with a hook or something? > > > 2015-08-05 8:30 GMT+02:00 Shazron : > > > I don't think that is a good idea. The reason why WKWebView is a plugin > is > > the faster update cycle. This is the total point of the new 4.x release: > > pluggable webviews. If the current UIWebView implementation is buggy, > > someone could *potentially* update that also. > > > > On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > > jcesarmob...@gmail.com> > > wrote: > > > > > My idea: > > > > > > Make iOS 9 use WKWebView as default without plugin and iOS 8 and > previous > > > use UIWebView, then if people want WKWebView on iOS 8 they install the > > > existing plugin with the webserver > > > > > > 2015-08-05 5:54 GMT+02:00 Shazron : > > > > > > > +1 Carlos > > > > > > > > On Wednesday, August 5, 2015, Carlos Santana > > > wrote: > > > > > > > > > I would like to see by default or configuration setting be able to > > have > > > > > that combination "WKWebView plugin only works on iOS 9 and older > > iOSes > > > > > fallback to UIWebView" > > > > > > > > > > I can already hear customers asking too many questions about > running > > a > > > > > webserver inside their app (i.e. security, energy, old hacks on > > their > > > > own > > > > > custom plugins, etc). I prefer to have the option to tell them > it's a > > > > > choice it's very easy to select to not have a webserver at all. > > > > > > > > > > - Carlos > > > > > Sent from my iPhone > > > > > > > > > > > On Aug 4, 2015, at 8:16 PM, Shazron > > > > > > > > wrote: > > > > > > > > > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > > > > server, > > > > > > iOS 9 doesn't. We'll have to support both if the dev deploys to > an > > > > older > > > > > > target (the final fallback is UIWebView) > > > > > > > > > > > > Either that or WKWebView plugin only works on iOS 9 and older > iOSes > > > > > > fallback to UIWebView. > > > > > > > > > > > >> On Wednesday, August 5, 2015, Edna Y Morales < > eymor...@us.ibm.com > > > > > > wrote: > > > > > >> > > > > > >> > > > > > >> Hi all, > > > > > >> > > > > > >> Since the file:// url loading bug was fixed for WKWebView in iOS > > 9, > > > > are > > > > > we > > > > > >> going to move away from the local webserver solution? > > > > > >> > > > > > >> Thanks, > > > > > >> Edna Morales > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > > > > > > > > > > > > >
Re: WKWebView and iOS 9
You are right, sorry, I haven't looked into the pluggable webviews yet. After looking into the WKWebView engine plugin I've seen that the local webserver is a dependency, I thought it was included inside the plugin (as the one from Eddy). So, the way to go is remove the dependency and make it only available for iOS 9? and if the user want to use it on iOS 8 then he install the webserver plugin manually and maybe add a preference on the WKWebView engine plugin? or is there a way that the preference (or an install param) can install the webserver plugin with a hook or something? 2015-08-05 8:30 GMT+02:00 Shazron : > I don't think that is a good idea. The reason why WKWebView is a plugin is > the faster update cycle. This is the total point of the new 4.x release: > pluggable webviews. If the current UIWebView implementation is buggy, > someone could *potentially* update that also. > > On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez < > jcesarmob...@gmail.com> > wrote: > > > My idea: > > > > Make iOS 9 use WKWebView as default without plugin and iOS 8 and previous > > use UIWebView, then if people want WKWebView on iOS 8 they install the > > existing plugin with the webserver > > > > 2015-08-05 5:54 GMT+02:00 Shazron : > > > > > +1 Carlos > > > > > > On Wednesday, August 5, 2015, Carlos Santana > > wrote: > > > > > > > I would like to see by default or configuration setting be able to > have > > > > that combination "WKWebView plugin only works on iOS 9 and older > iOSes > > > > fallback to UIWebView" > > > > > > > > I can already hear customers asking too many questions about running > a > > > > webserver inside their app (i.e. security, energy, old hacks on > their > > > own > > > > custom plugins, etc). I prefer to have the option to tell them it's a > > > > choice it's very easy to select to not have a webserver at all. > > > > > > > > - Carlos > > > > Sent from my iPhone > > > > > > > > > On Aug 4, 2015, at 8:16 PM, Shazron > > > > > > wrote: > > > > > > > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > > > server, > > > > > iOS 9 doesn't. We'll have to support both if the dev deploys to an > > > older > > > > > target (the final fallback is UIWebView) > > > > > > > > > > Either that or WKWebView plugin only works on iOS 9 and older iOSes > > > > > fallback to UIWebView. > > > > > > > > > >> On Wednesday, August 5, 2015, Edna Y Morales > > > > wrote: > > > > >> > > > > >> > > > > >> Hi all, > > > > >> > > > > >> Since the file:// url loading bug was fixed for WKWebView in iOS > 9, > > > are > > > > we > > > > >> going to move away from the local webserver solution? > > > > >> > > > > >> Thanks, > > > > >> Edna Morales > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > > > > > >
Re: WKWebView and iOS 9
I don't think that is a good idea. The reason why WKWebView is a plugin is the faster update cycle. This is the total point of the new 4.x release: pluggable webviews. If the current UIWebView implementation is buggy, someone could *potentially* update that also. On Wed, Aug 5, 2015 at 1:44 PM, julio cesar sanchez wrote: > My idea: > > Make iOS 9 use WKWebView as default without plugin and iOS 8 and previous > use UIWebView, then if people want WKWebView on iOS 8 they install the > existing plugin with the webserver > > 2015-08-05 5:54 GMT+02:00 Shazron : > > > +1 Carlos > > > > On Wednesday, August 5, 2015, Carlos Santana > wrote: > > > > > I would like to see by default or configuration setting be able to have > > > that combination "WKWebView plugin only works on iOS 9 and older iOSes > > > fallback to UIWebView" > > > > > > I can already hear customers asking too many questions about running a > > > webserver inside their app (i.e. security, energy, old hacks on their > > own > > > custom plugins, etc). I prefer to have the option to tell them it's a > > > choice it's very easy to select to not have a webserver at all. > > > > > > - Carlos > > > Sent from my iPhone > > > > > > > On Aug 4, 2015, at 8:16 PM, Shazron > > > > wrote: > > > > > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > > server, > > > > iOS 9 doesn't. We'll have to support both if the dev deploys to an > > older > > > > target (the final fallback is UIWebView) > > > > > > > > Either that or WKWebView plugin only works on iOS 9 and older iOSes > > > > fallback to UIWebView. > > > > > > > >> On Wednesday, August 5, 2015, Edna Y Morales > > > wrote: > > > >> > > > >> > > > >> Hi all, > > > >> > > > >> Since the file:// url loading bug was fixed for WKWebView in iOS 9, > > are > > > we > > > >> going to move away from the local webserver solution? > > > >> > > > >> Thanks, > > > >> Edna Morales > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > >
Re: WKWebView and iOS 9
My idea: Make iOS 9 use WKWebView as default without plugin and iOS 8 and previous use UIWebView, then if people want WKWebView on iOS 8 they install the existing plugin with the webserver 2015-08-05 5:54 GMT+02:00 Shazron : > +1 Carlos > > On Wednesday, August 5, 2015, Carlos Santana wrote: > > > I would like to see by default or configuration setting be able to have > > that combination "WKWebView plugin only works on iOS 9 and older iOSes > > fallback to UIWebView" > > > > I can already hear customers asking too many questions about running a > > webserver inside their app (i.e. security, energy, old hacks on their > own > > custom plugins, etc). I prefer to have the option to tell them it's a > > choice it's very easy to select to not have a webserver at all. > > > > - Carlos > > Sent from my iPhone > > > > > On Aug 4, 2015, at 8:16 PM, Shazron > > > wrote: > > > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web > server, > > > iOS 9 doesn't. We'll have to support both if the dev deploys to an > older > > > target (the final fallback is UIWebView) > > > > > > Either that or WKWebView plugin only works on iOS 9 and older iOSes > > > fallback to UIWebView. > > > > > >> On Wednesday, August 5, 2015, Edna Y Morales > > wrote: > > >> > > >> > > >> Hi all, > > >> > > >> Since the file:// url loading bug was fixed for WKWebView in iOS 9, > are > > we > > >> going to move away from the local webserver solution? > > >> > > >> Thanks, > > >> Edna Morales > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > >
Re: WKWebView and iOS 9
+1 Carlos On Wednesday, August 5, 2015, Carlos Santana wrote: > I would like to see by default or configuration setting be able to have > that combination "WKWebView plugin only works on iOS 9 and older iOSes > fallback to UIWebView" > > I can already hear customers asking too many questions about running a > webserver inside their app (i.e. security, energy, old hacks on their own > custom plugins, etc). I prefer to have the option to tell them it's a > choice it's very easy to select to not have a webserver at all. > > - Carlos > Sent from my iPhone > > > On Aug 4, 2015, at 8:16 PM, Shazron > > wrote: > > > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web server, > > iOS 9 doesn't. We'll have to support both if the dev deploys to an older > > target (the final fallback is UIWebView) > > > > Either that or WKWebView plugin only works on iOS 9 and older iOSes > > fallback to UIWebView. > > > >> On Wednesday, August 5, 2015, Edna Y Morales > wrote: > >> > >> > >> Hi all, > >> > >> Since the file:// url loading bug was fixed for WKWebView in iOS 9, are > we > >> going to move away from the local webserver solution? > >> > >> Thanks, > >> Edna Morales > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > >
Re: WKWebView and iOS 9
I would like to see by default or configuration setting be able to have that combination "WKWebView plugin only works on iOS 9 and older iOSes fallback to UIWebView" I can already hear customers asking too many questions about running a webserver inside their app (i.e. security, energy, old hacks on their own custom plugins, etc). I prefer to have the option to tell them it's a choice it's very easy to select to not have a webserver at all. - Carlos Sent from my iPhone > On Aug 4, 2015, at 8:16 PM, Shazron wrote: > > My thinking -- It'll be a hybrid approach - iOS 8 uses local-web server, > iOS 9 doesn't. We'll have to support both if the dev deploys to an older > target (the final fallback is UIWebView) > > Either that or WKWebView plugin only works on iOS 9 and older iOSes > fallback to UIWebView. > >> On Wednesday, August 5, 2015, Edna Y Morales wrote: >> >> >> Hi all, >> >> Since the file:// url loading bug was fixed for WKWebView in iOS 9, are we >> going to move away from the local webserver solution? >> >> Thanks, >> Edna Morales - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: WKWebView and iOS 9
My thinking -- It'll be a hybrid approach - iOS 8 uses local-web server, iOS 9 doesn't. We'll have to support both if the dev deploys to an older target (the final fallback is UIWebView) Either that or WKWebView plugin only works on iOS 9 and older iOSes fallback to UIWebView. On Wednesday, August 5, 2015, Edna Y Morales wrote: > > Hi all, > > Since the file:// url loading bug was fixed for WKWebView in iOS 9, are we > going to move away from the local webserver solution? > > Thanks, > Edna Morales
WKWebView and iOS 9
Hi all, Since the file:// url loading bug was fixed for WKWebView in iOS 9, are we going to move away from the local webserver solution? Thanks, Edna Morales
