Facts:
1. #Github #Copilot for #Xcode supports setting a proxy.
2. Proxyman creates a proxy that can intercept and "massage" calls.
3. (Free) Copilot for Xcode only has a handful of models.
4. I happily pay for OpenRouter already, don't want to pay for Copilot, too.
5. I should really go to bed now.
Hypothesis:
1. It might be possible to rewrite Copilot calls in Proxyman so they go to #OpenRouter instead.
…TOMORROW
So basically the only way to browse the project in #Xcode is to full-on duplicate (clone, download zip, etc) the entire project to another location, just so I can open the damn thing to see how things are being used.
NEVER MIND that there's already an entire copy in the source checkouts. NEVER MIND that I don't want to change anything.
I used to be #Apple's Developer Tools Evangelist and I am anxiously yearning for the day when other IDEs become viable daily drivers for building apps. #Shame
It's another one of those days where #Xcode is making me want to throw my computer through the window and go become a hermit.
Today it's the fact that if you open a project from an unwritable location, Xcode will pop up this alert EVERY THREE SECONDS UNTIL YOU CLOSE THE PROJECT.
There is absolutely no way to browse code. No way to see how things are being used. No way to stop Xcode from trying to *write data* just for OPENING THE PROJECT. Absolute utter insanity.
Well, fine then, don't tell me. #Xcode
That feeling when you finally recall how to resolve that nagging #Xcode console warning that's been there for months.
hey! Got something to talk about for #macOS or #iOS? Or one of Apple’s other platforms? Submit a talk to our awesome conference in #Naarm #Melbourne!
Dear #Xcode:
1. Yes, I told you to open double-clicked files in a new window
2. No, if the click brought the window to front and you did not adjust the selection and show the file in the current window, then the second click I do (which selects the item) is just that, a click to select it and show it in my window, *not* a double-click. You can't ignore the front click and count it towards a double click at the same time.
Auch wenn es mich selbst schon nervt, ich muss euch nochmal belaestigen...
Ich suche ab sofort einen neuen Job als #iOS und/oder #macOS Software-Entwickler. Ich hab viele Jahre Erfahrung auf dem Gebiet, kenne #ObjectiveC, #Swift, #SwiftUI, #Git, #Xcode und... naja, die ganze Toolchain drumherum eben.
Ich suche eine Remote-Only Festanstellung, keinen Freelance-Job (Vorzugsweise in Österreich, Deutschland geht aber auch). Wenn es in der Naehe von #Bregenz oder #Dornbirn ist, dann auch gerne Onsite.
Wenn ihr jemanden kennt, der jemanden kennt... ihr wisst schon.
Ich danke euch fuers rege Teilen/Boosten.
Show / Hide Debug Area
Have you tried Instruments but gave up because you couldn’t interpret the data?
If so, I’m writing a book on Instruments that shows you how to interpret the data and find the code causing problems. Learn more about the book at the following link:
Apple's Instruments Tutorials are actually a great introduction. Over the years I've used Instruments from time to time to investigate issues, but never felt I had a good system of how to approach problems.
Okay Xcode’s predictive code model, who is Nick Lockwood? And why are you suggesting this in my project?
Yes I did search the web and found a Nick Lockwood on GitHub. However I didn’t see anything in their repos that was this line of code. Curious.
Did you know you can buy the DocC package of 104 Xcode Tips? After downloading the archive, you can install it in Xcode. This means you have 104 handpicked Xcode Tips right at your fingertips.
What are you waiting for?
FYI if your SwiftUI previews give you problems your project name should be a prime suspect.
Mine started breaking because of an apostrophe (fixed now). They also broke when I named a project inout (for learning about inout).
Lena had an umlaut as the culprit.