Reputation: 481
I'm developing an App and I wanted to separate in 'subprojects', because, although some parts have the same name, they have distinct functionality... I've tried this feature (subproject), but it seems that I can't reference files (like storyboards) from a subproject... So, what's the point of a subproject if you can make it work together with the project base?
Thanks a lot...
Upvotes: 1
Views: 427
Reputation: 299345
Subprojects are generally used for independent, reusable code, mostly libraries and frameworks. They aren't usually used for organizing parts of a single project.
In Swift, subprojects can be useful for creating modules, but again this isn't commonly done except for independent, reusable code (mostly libraries and frameworks....)
If you're trying to access storyboards in another module, you've probably broken the "independent" part. It is rare to organize UI elements this way, and definitely isn't something you should do in your first project. Once you have some experience working in a larger project, you can explore novel ways of organizing it, but to start, just keep a single project.
This makes me a bit nervous:
although some parts have the same name, they have distinct functionality
They probably should have different names then.
Upvotes: 2