3 ms·
I love the immediate feedback and the ease with which you can layout views in the IB, but it can be a nightmare for teams. Any time a storyboard is touched, the
by wille92 11y ago
I love the immediate feedback and the ease with which you can layout views in the IB, but it can be a nightmare for teams. Any time a storyboard is touched, the file is updated in some way. The diffs are large and unintuitive, and merging is tedious. If Apple wants to continue to push the IB, they need to make it more compatible with teams and source control.
- natch 11y agoSuch misinformation here. First, the merges usually happen automagically. The automatically added diffs, if any, are usually tiny and targeted. If it's a nightmare for a particular team, that team just needs to learn how to use IB. One person (or one pair if you're doing that) should work on a scene at a time. And it's really easy to have storyboards broken up into multiple storyboards, which makes most of these red herring issues go away anyway. I think people get fooled by the fact that the UI is visual. There it is, in front of you, so you think you should be able to add multiple interdependent constraints while another person with their own copy of the same file is adding conflicting interdependent constraints to the same scene. Note, I didn't say "independent" I said "interdependent." That will never work, ever, in any system. It won't even work if you do things programmatically, with different people changing interdependent constraints at the same time and then expecting them all to merge and work without pain. It's not even really an IB issue; you just see it in IB because the visual UI makes you think it should just work like magic.