• 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: Storyboard weakness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Storyboard weakness


  • Subject: Re: Storyboard weakness
  • From: Rick Mann <email@hidden>
  • Date: Wed, 09 Mar 2016 15:57:30 -0800

Because I want all the benefits the specific view controller gives me, namely the ability to build the cells right in the view.

I guess I have to give up on that. One small silver lining is I can break those into NIBs and not duplicate them (I have three different collection views that all reuse the  same cells).

But the other reason is that I'VE ALREADY BUILT THIS. The requirement to add views came much later. If Apple had just done it right from the start, I wouldn't be suffering like this.

> On Mar 9, 2016, at 15:46 , Daniel Stenmark <email@hidden> wrote:
>
> Why are you locking yourself into a heavily customized UICollectionViewController?  Why not just use a generic UIViewController and hook up your view elements the old fashioned way?
>
> Dan
>
>> On Mar 9, 2016, at 3:04 PM, Rick Mann <email@hidden> wrote:
>>
>> There's a severe weakness in Storyboards for which I'm hoping a better solution exists.
>>
>> When you create a scene for say, a UICollectionView, the Storyboard makes it very easy, but it also imposes a severe limitation. In my case, my UICollectionViewController subclass lives inside a UINavigationController. It manages the controls in the toolbar and the title, as well as the content.
>>
>> But inevitably I want to add additional views beneath the UINavigationBar that are NOT CONTAINED within the UICollectionView (in this case, a UISegmentedControl for sorting the contents). The only way I see how to do this with Storyboards is to create two view controllers, one that embeds the UICollectionViewController subclass. But now its impossible to wire up UINavigationBar items to it. I've been forced to split up view control across two view controllers that really should be one.
>>
>> This is solved by having the UICollectionView controller subclass have its view property point to a generic containing view, and its collectionView property point to the collectionView subview. But it's not really designed to work this way, and Storyboards definitely doesn't support this.
>>
>> The Apple-provided way imposes a HUGE burden.
>>
>> Is there any happy middle ground?
>>
>> I've written this bug before, but Apple doesn't care.
>>
>> --
>> Rick Mann
>> 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
>


--
Rick Mann
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


  • Follow-Ups:
    • Re: Storyboard weakness
      • From: Daniel Stenmark <email@hidden>
References: 
 >Storyboard weakness (From: Rick Mann <email@hidden>)
 >Re: Storyboard weakness (From: Daniel Stenmark <email@hidden>)

  • Prev by Date: Re: Apple Bug no response
  • Next by Date: Re: Storyboard weakness
  • Previous by thread: Re: Storyboard weakness
  • Next by thread: Re: Storyboard weakness
  • Index(es):
    • Date
    • Thread