故事板中的视图过多-Xcode运行缓慢

Question

I'm helping someone out with an xcode project but it's almost impossible. They have around 100 View controllers on their storyboard and it's just running really slow. I've followed all of the guides on making Xcode faster but they just don't help for this situation. Outside of that storyboard, when we're working in the .h and .m files it runs perfectly fine, it's just inside the storyboard that it runs slow. Has anyone had any experience with a project like this? What did you do? Or what can I do to make it possible to work in the storyboard? Thanks

Answer 1

My solution is: Open a new Window from the Storyboard and minimize it. So it stays in RAM and won't reload. Working with the storyboard keeps quick and easy now.

Answer 2

I faced the same issue when I was working on an Enterprise App. In the Project I had only one storyboard and all views in a single storyboard. Opening the storyboard caused Xcode to get very slow.

So I divided the storyboard into multiple storyboards as module-wise and load a separate storyboard per module like in the code below:

If I want to push a view controller:

UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"storyboardName" 
                                                     bundle:nil];
UIViewController *viewController = 
 [storyboard instantiateViewControllerWithIdentifier:@"Members_ViewController"];

[self.navigationController pushViewController:viewController animated:YES];

Answer 3

We're having the same issue, and commonly recommended performance tweaks didn't help. On a MacBook Pro with SSD I see CPU utilization go to 80-90% when in storyboard view and navigation lag is incredibly frustrating. Simulator can take up to a minute to display, and Xcode often won't close, requiring a force quit.

These symptoms all disappear if not viewing the storyboard, or if storyboard is open as source code.

UPDATE: We split our project up into multiple storyboards, and life is good again - CPU utilization is back to single digits and performance is on par with Xcode 4.6.3. There is definitely an issue with larger storyboards; the only change made to our code in the process was updating references to the main storyboard to a storyboardWithName call instead.

One of the view controllers in our project has a container view, and it appeared that the utilization issue stopped when that controller and its container view were moved to a separate storyboard. It may have been a coincidence, and we broke up the rest of the storyboard for consistency, but if I were dealing with this issue again, I'd first move any view controllers with container views to a separate storyboard.

Answer 4

If you are using Xcode 7, Storyboard References are a quick way to create multiple storyboards and will definitely help this issue. The great side about using Storyboard References is it does not involve any extra code whatsoever! See the stackoverflow link below for a full description on how to set it up.

https://stackoverflow.com/a/30772789/3316842

Answer 5

I'm facing the same problem. Massively frustrating. My storyboard has only 41 views. And I'm running a Mac Min i7 running at 2.3Ghz. With the storyboard open, it takes ages to do very simple tasks like move a UILABEL? Then, in counterpart view, editing code is like being back on a ZX81. It's all very well and good banging "intelligence" into the storyboard, but not at the cost of development efficiency. In so far as storyboard "size" guidelines are concerned, I don't ever remember reading that storyboards have to be split beyond a certain size. Maybe I need to read more.

To make the changes required, ie split the storyboard up, slap some VC's on several storyboards, will require a bit of a faff. I suppose if that's the new best-practice, fine. But I could do with more than conjecture.

Answer 6

I also agree with organizing your views across multiple story boards. It becomes very handy when you have a view that is called from several other views. Then the storyboard can become like pasta, unclear. In my case I had a camera view that could be called from several views, I put this on a new storyboard and this works great. Since the camera view was also pointing to the search order view, I had to put the search order view also on a separate storyboard. Again my main story board got simpler.

So have a main story board, and separate as much as you can onto separate storyboards. I made a general class StoryBoardNavigation where I centralized all functions to call child storyboards.

Here is an example of this:

This function navigates to the storyboard called OrderLookupStoryboard and opens the view in start position.

+(void) NavigateToOrderLookupFrom:(UIViewController *)vc
{
    UIStoryboard * sb = [UIStoryboard storyboardWithName:@"OrderLookupStoryboard" bundle:nil];
    UIViewController * vcTo = [sb instantiateInitialViewController];

    [UIView transitionWithView:vc.view duration:0.8     options:UIViewAnimationOptionTransitionCrossDissolve
                animations:^{
                    [vc.navigationController pushViewController:vcTo animated:NO];
                }
                completion:NULL];

}

This function passes some parameters to the storyboard.

+(void) NavigateToCameraFrom:(UIViewController *)vc WithSelectedZone:(int)selectedZone
{
    UIStoryboard * sb = [UIStoryboard storyboardWithName:@"CameraStoryboard" bundle:nil];
    MediaCapture * vcTo = [sb instantiateInitialViewController];
    vcTo.selectedZone = selectedZone;
    vcTo.zoneSet = YES;
    [UIView transitionWithView:vc.view duration:0.8 options:UIViewAnimationOptionTransitionCrossDissolve
                animations:^{
                    [vc.navigationController pushViewController:vcTo animated:NO];
                }
                completion:NULL];

}

This function opens the view in module transition style:

+(void) NavigateToSignatureFrom:(UIViewController *)vc withSignee:(NSString *) Signee
{
   UIStoryboard * sb = [UIStoryboard storyboardWithName:@"SignatureStoryboard" bundle:nil];
   UIViewController * vcTo = [sb instantiateInitialViewController];

   ((SignatureVC *) vcTo).Signee = Signee;

   [vcTo setModalTransitionStyle:UIModalTransitionStylePartialCurl];
   [vc presentViewController:vcTo animated:YES completion:nil];
}

Answer 7

I wanted to add that I was having a problem with my storyboard responding slowly when utilizing a container view with a navigation controller inside it. I even tried putting it in its own storyboard and it still was so slow i was unable to even use it. It seems that the when container view was resizes the navigation controller, the navigation bar was causing the issue.

I was able to work around this problem by selecting the navigation controller in the storyboard, hiding the navigation bar by unchecking "shows navigation bar" in the attributes inspector and using "isNavigationBarHidden = false" in either viewDidLoad or viewWillAppear of my view controller class.