The current state of storyboards and multi member dev teams.
The current state of storyboards and multi member dev teams.
- Subject: The current state of storyboards and multi member dev teams.
- From: Alex Zavatone <email@hidden>
- Date: Tue, 15 Apr 2014 11:25:57 -0400
Hi all. There's been much discussion on using storyboards in iOS teams with multiple developers over the past few years and I wanted to ask the list what the current state of the universe with regards to this topic.
What do you guys do?
What works for you? What have you tried but didn't?
Based on my research yesterday with two of us messing with Xcode 5.1 and a project checked into SVN, both of us being bad citizens and changing the same scene in a storyboard, it was obvious that Filemerge isn't context aware.
If I add a label to one storyboard scene there is an XML structure that is added in the Storyboard file and if my other team member also adds something else, there is another XML structure added to his file. When seeing this and attempting to commit, Xcode simply reports that one storyboard file is out of date.
As expected.
Using Filemerge to see if it can handle this, it really can't. Filemerge isn't context sensitive to know what UILabels are and what other UI class definitions are, so using a storyboard, it's pretty easy to get conflicts if people end up editing the same scene in a storyboard.
Since Apple wants us to use storyboards, you'd expect we'd have tome some UIKit aware context awareness in a storyboard friendly filemerge tool, but I don't think we have that.
So, I'm wondering. Does it make sense to lay out the storyboard as simply a skeleton and use XIBs for each scene? Should we just resign ourselves to one person working in a storyboard at a time? Am I being overly concerned about an issue that really doesn't crop up?
What do you guys do who are on multiple developer iOS teams?
Cheers,
- Alex
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden