I seem to somehow lost my commit privileges to the subversion repository, or did that all move to git? I lost track.
Anyway I have a number of patches for the Xcode bundle:
• "Build With Xcode" window title can now be customized via TM_XCODE_WTITLE • "BUILD LEGACY TARGET" are now hidden by default • Xcode 3.2 produces large amounts of nt very informative lines containing "{standard input}", these are now ignored • Generate correct paths for subprojects • expand "$HOME" in the product_path
Could someone apply them please?
Thanks
Gerd
On 14 Oct 2009, at 01:27, Gerd Knops wrote:
I seem to somehow lost my commit privileges to the subversion repository, or did that all move to git? I lost track.
You should have access to the repository (no path restrictions).
But in applying your patch I moved the Xcode bundle to GitHub.
Anyway I have a number of patches for the Xcode bundle:
• "Build With Xcode" window title can now be customized via TM_XCODE_WTITLE
I changed this to TM_XCODE_WINDOW_TITLE — I don’t think there is value in being short.
Curious though why you want this?
• "BUILD LEGACY TARGET" are now hidden by default • Xcode 3.2 produces large amounts of nt very informative lines containing "{standard input}", these are now ignored • expand "$HOME" in the product_path
I have applied the above five patches (for the GitHub version).
• Generate correct paths for subprojects
I wasn’t comfortable with this patch. It contained an info line which was commented, some commented puts, and an ‘isa’ comparison against PBXContainerItemProxy changed to PBXContainerItemProxyXX.
Would be nice if you would resubmit this patch and be sure that it only touch the things required for the sub-project paths.
Also would be good if you’d try to use the same style as the surrounding code. It looks really slobby when e.g. whether there are spaces around the equal character in assignments change from line to line ;)
Btw: preferably the patch should be done against http://github.com/textmate/xcode.tmbundle
On Nov 17, 2009, at 11:48 AM, Allan Odgaard wrote:
On 14 Oct 2009, at 01:27, Gerd Knops wrote:
I seem to somehow lost my commit privileges to the subversion repository, or did that all move to git? I lost track.
You should have access to the repository (no path restrictions).
But in applying your patch I moved the Xcode bundle to GitHub.
OK.
Anyway I have a number of patches for the Xcode bundle:
• "Build With Xcode" window title can now be customized via TM_XCODE_WTITLE
I changed this to TM_XCODE_WINDOW_TITLE — I don’t think there is value in being short.
Agreed.
Curious though why you want this?
I am working on a suite of applications. Often I run application "A", then use the run log to fix something in "B". When I then run "B", it re-uses the output window from "A" and I loose the run log.
All those apps are targets in the same Xcode project. I use a custom "Build & Run" script which determines the target based on the currently edited file (or if that is shared the last target that was used), and it also set's the window title. Now I have a run log for each target.
• "BUILD LEGACY TARGET" are now hidden by default • Xcode 3.2 produces large amounts of nt very informative lines containing "{standard input}", these are now ignored • expand "$HOME" in the product_path
I have applied the above five patches (for the GitHub version).
Thanks!
• Generate correct paths for subprojects
I wasn’t comfortable with this patch. It contained an info line which was commented, some commented puts, and an ‘isa’ comparison against PBXContainerItemProxy changed to PBXContainerItemProxyXX.
Would be nice if you would resubmit this patch and be sure that it only touch the things required for the sub-project paths.
Also would be good if you’d try to use the same style as the surrounding code. It looks really slobby when e.g. whether there are spaces around the equal character in assignments change from line to line ;)
Sorry about that, I am quite illiterate when it comes to Ruby nor do I really want to know anymore about the Xcode project structure... That being said, these patches are necessary.
Ever since Xcode3 the whole "PBXContainerItemProxy" block causes many exceptions for me in the run log. I have not seen any ill-effects in disabling it. But since I am not sure what exactly it does I feel uncomfortable removing it completely.
The other patches allow the bundle to properly identify source files and make them "clickable" in projects that have multiple targets.
Btw: preferably the patch should be done against http://github.com/textmate/xcode.tmbundle
I'll clean up that patch and send you a "pull request".
Gerd
-
Allan Odgaard -
Gerd Knops