• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Subclassing UIWebview a show-stopper?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subclassing UIWebview a show-stopper?


  • Subject: Re: Subclassing UIWebview a show-stopper?
  • From: Dave DeLong <email@hidden>
  • Date: Mon, 08 Aug 2011 22:58:52 -0700

Hi Arri,

Subclassing UIWebView is probably not going to get your app rejected (though I have no insight in to the approval process).  However from a architecture point-of-view, it "smells" bad.  UIWebView is one of those views that's not intended to be subclassed.  Sure you can, since you can declare anything as your superclass, but I'd be highly surprised if the UIWebView authors are even expecting people to subclass it.  If they're not, then that could mean that there's logic in there that operates on the assumption of none of the methods being overridden.  There are certainly classes like that in all of the Cocoa (Touch) frameworks.

This sounds like one of the things that I'd only go ahead with after I've proven that every other idea presented isn't possible.

Dave

On Aug 8, 2011, at 10:51 PM, arri wrote:

> Hello,
>
> After allot of writing test-cases, and googling for others'
> experiences, i found that the most easy and straightforward way of
> achieving what i want, is to simply subcass UIWebView and override
> UIViews' - hitTest:withEvent method.
> However, as everyone emphasize everywhere i look, the docs say i
> "should" not subclass UIWebView.
>
> Perhaps this is more about the english language than about software
> development or Apple, but what does "should" exactlty mean in this
> context.
> Will Apple possibly reject the app if i use a UIWebView subclass?
>
> Or does it mean how i've always understood the word "should" and i
> could read the docs as such: "…there shouldn't be a need to
> subclass…".
> In other words: subclassing UIWebview will not result in a rejection.
>
>
>
>
>
>
> thanks,
> arri
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Subclassing UIWebview a show-stopper? (From: arri <email@hidden>)

  • Prev by Date: Re: Decimation - NSBezierPath or something else?
  • Next by Date: Re: CFURLWriteDataAndPropertiesToResource as root?
  • Previous by thread: Subclassing UIWebview a show-stopper?
  • Next by thread: Re: Subclassing UIWebview a show-stopper?
  • Index(es):
    • Date
    • Thread