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 ([email protected]) 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:  
https://developer.apple.com/videos/wwdc/2015/?id=501  


On Tue, Jun 9, 2015 at 3:59 PM, Shazron <[email protected]> wrote:  

> 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 a  
> solution in Cordova for ODR for app bundles that are huge. For example, in  
> the CLI prepare step.  
>  
> Of course this won't be a universal solution and is more complicated.  
>  
> On Tuesday, June 9, 2015, Carlos Santana <[email protected]> wrote:  
>  
>> 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 <[email protected]> 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  
>> urls  
>> > in Library and Documents, but not the app bundle.  
>> > https://twitter.com/wkwebview/status/608359163299819521  
>> >  
>> > On Tue, Jun 9, 2015 at 1:02 PM, Carlos Santana <[email protected]>  
>> > wrote:  
>> >  
>> > > 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 Shazron <[email protected]> wrote:  
>> > >  
>> > > > 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 <[email protected]> wrote:  
>> > > >  
>> > > > > Moar news https://twitter.com/wkwebview/status/608005652720451584  
>> > > > >  
>> > > > >  
>> > > > > On Monday, June 8, 2015, Shazron <[email protected]> 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, Shazron <[email protected]>  
>> wrote:  
>> > > > >>  
>> > > > >>> Also Xcode 6.3 now *requires* Yosemite. Fair warning to upgrade  
>> I  
>> > > > >>> suppose for your dev machines and build servers...  
>> > > > >>>  
>> > > > >>>  
>> > > > >>> On Mon, Feb 9, 2015 at 2:13 PM, tommy-carlos williams  
>> > > > >>> <[email protected]> wrote:  
>> > > > >>> > Oh, FFS.  
>> > > > >>> >  
>> > > > >>> > I give up on Apple solving this, personally. Most apps don’t  
>> > > > >>> *actually* need it (they think they do, but they don’t). I am  
>> going  
>> > > to  
>> > > > find  
>> > > > >>> another way to solve it for our apps… maybe I will actually  
>> have to  
>> > > > write a  
>> > > > >>> native plugin for the crypto :(  
>> > > > >>> >  
>> > > > >>> > --  
>> > > > >>> > tommy-carlos williams  
>> > > > >>> >  
>> > > > >>> > On 10 February 2015 at 08:18:31, Shazron ([email protected])  
>> > > wrote:  
>> > > > >>> >  
>> > > > >>> > In other news -- the new Xcode 6.3 beta (iOS 8.3) does *not*  
>> > > contain  
>> > > > >>> > the loadFileURL:readAccessURL: selector that we are all  
>> waiting  
>> > for  
>> > > > >>> > :'(  
>> > > > >>> > https://twitter.com/wkwebview/status/564865657225756672  
>> > > > >>>  
>> > > > >>  
>> > > > >>  
>> > > >  
>> > >  
>> >  
>>  
>  

Reply via email to