On May 18, 2017, at 6:37 PM, Quincey Morris < email@hidden> wrote:
On May 18, 2017, at 15:23 , Bryce Glover < email@hidden> wrote: There are multiple things to keep in mind.
OK.
…
— Remember that when you create a project from a template, there are several identifiers that are derived (at creation time) from the single Project Name field. The in-Xcode project rename dialog is a convenience that “knows” where it originally used the project name, and so knows which places need to be changed.
All right, that makes sense. I agree that it would be a pain to try and fix all of those identifiers up manually, too, though, in theory, it could be done (not that I’d want to torture myself like that if I ended up messing up following the instructions you provided for the workaround to my original issue, of course…)
…
— The problem with renaming the project externally may have been a bug that’s fixed. Nasty-detail bugs are fixed in Xcode all the time, and it’s easy to condemn the current Xcode for bugs in the previous versions. (OTOH there are plenty of bugs that don’t get fixed over a long span of versions, so there’s that too.)
Ugh, it’d be enough to make one’s head spin if they went back to the change logs and spent too much mental energy trying to piece together what changes happened when. I think I’ll just stick to looking at the release notes for newer versions (wt least for the version of OS X/macOS I’m stuck on, though I’ve been eyeing the Sierra releases with just a hint of envy against my better judgement) as they come out for now to keep my sanity intact.
…
— Xcode is much better about tracking file change activity and knowing what effect is has on the repository. This is definitely one area that used to suck, and is currently much improved. I was kind of shocked yesterday to see a build warning telling me that a file from the repository was missing. That was new.
That’s good to hear! Talk about a pleasant surprise, eh?
…
— Historically, Xcode has had difficulty tracking changes to directory names in the paths to files tracking in a git repository. …
Wait, do you mean, “…paths to files [its] tracking…,” here? …When you rename the project in the Finder, you’re actually renaming a directory that’s a couple of levels above the actual project file. Doing this outside Xcode may well mess up the repository. The project is inside the repository, not the other way around.
So I’d have to store my base project — what I would like to store as a template, that is — somewhere completely different from where I would want my derived projects to end up. Then I’d have to make sure that, after copying the base project again to make a new derived one, I renamed it, immediately, from inside Xcode to avoid problems. Then I’d lather, rinse, and repeat for each new project I’d want to create. I could probably remember all of that, especially if I documented it somewhere, but I say that now hoping not to jinx myself in the future and…it still sounds…brittle and possibly prone to error due to its complexity. Granted, the fact that custom project templates aren’t officially supported doesn’t make them that much better since one has to do some tinkering to make them work properly consistently, but they’d sure be a better solution to this than your workaround. (Say, you wouldn’t happen to know what things I could try changing in what I’ve already got to solve the problems I described as having with it in my OP, would any of you…?)
Resigned to either trial and error or tedium, Bryce Glover
|