Sorting data by multiple criteria can be complex, but Swift's built-in tuple comparison feature simplifies the process. Using tuple comparison, we can efficiently sort and organize data by various fields. Check out my new post to learn how: https://nilcoalescing.com/blog/MultiCriteriaDataSortingWithTuples
Check out the talk I had to cancel at #DeepDishSwift There might be a nugget here that would surprise you. Check out the links in the description to go directly to a specific #Swift or #SwiftUI nugget
@StewartLynch I watched the talk and it was very insightful! My favorite part was the Bindable technique right at the start. When I first started learning about Observation, I also thought the Bindable thing was some sort of an oversight… regardless, thanks for the great talk 😉
Does anyone know of a tool that analyses Xcode projects and then provides me with statistics on lines of code etc.? In any case, it should also take into account Swift packages used.
Thanks to @dimitribouniol and @glacials, we're much closer to the next Cork release! I was finally able to implement the first version of a self-compiled check, which was the only requirement left for the next release.
As promised, both Dimitri and Ben will be getting either a free Cork license or the cash equivalent, as well as a special shoutout in the contributors sections once the feature is fully implemented.
I used to use GitHub sponsors, but I ran into massive limitations. What I’d recommend is to use an automation system like n8n to react to webhooks that Stripe sends to add users, then also using a different n8n workflow for the verification (which is also what I use) (2/3)
You can hit up the n8n workflow every time the user tries generating something, the workflow will then check a database for the relevant user info (like the number of tokens) and maybe even generate the response. Then, you can use another workflow to update the database.
That’s about an overview of what I’d do 🤔 Tell me if you have any other questions 😊 I’m far from an expert though (3/3)
As for having the service name in the button, I’ve read somewhere that it’s better to be explicit in the buttons so that the user doesn’t have to look up at the service name and then back to the button to figure out which service that button will actually modify. All the buttons in Cork follow this system; maybe it’s a bit awkward and noticeable due to the two buttons being next to each other, so let’s see what can be done about that (2/3)
@arnan@troz Impossible, right? 😂 Anyway, I created Cork so that you could do everything in Homebrew without the terminal. It’s written in SwiftUI for macOS 13+. It using SwiftUI is sometimes a bit awkward, but I do my best to make it work.
There’s a quick overview of the features on the website: https://corkmac.app
We’re having trouble with the “Somehow bypass this licensing scheme if the user compiled Cork themselves” part
Do you have any ideas on how to solve this? If you do and you help implement it, you’ll get a spot in the “Special thanks” section of the readme and within the app itself, as well as a free license or cash equivalent of the license
All the tips in the book are focused on Swift and Swift Standard Library, so they can be applied to any platform, from iOS and macOS to Swift on the server.
Voxel editor coming along nicely now. Video is taken on the Mac but it also works on the iPad.
I've spent surprisingly little time on this. 20 hours total tops. Its amazing what you can get done with good quality tools, consistency (I normally do an hour pre and post dog walk), and a good set of fundamentals (its really making use of things I've learned in the last year or so). #swift#swiftui#metal
@ctietze I’ve been working on voxel buildings for a city builder and wanted something a bit more to my tastes for creating them so figured I’d see what I could do! Hopefully useful to others too.
#Eventim-Nutzer sollen #Passwörter ändern - Daten aus dem #Darknet wurden eingesetzt, um Ticketverkäufe für #Taylor#Swift-Konzert in Deutschland zu manipulieren:
"Wie die Ticket-Plattform Eventim mitteilt, hätten in den letzten Tagen unbekannte Kriminelle versucht, sich unautorisiert Zugang zu Konten von Nutzerinnen und Nutzer zu verschaffen, um in den Besitz von Karten für Swifts "The Eras Tour" zu gelangen - und diese dann weiterzuverkaufen."
Alright, might be time to abstract #SwiftData in my app. Who has the best example? Should I use a ModelActor? Would a class holding a ModelContainer be sufficient if I create a new ModelContext inside the CRUD functions? #iosdev#swift
@davidbures Lol I’m mostly trying to extract my reliance on SwiftData everywhere. If something causes the ModelContainer to fail to initialize, my app still has functionality to offer. In fact, free users don’t even access the database at all. So, doesn’t make sense to fatalError or block the entire app loading. “Abstraction” is probably a step past what I need though, so maybe I should ask for examples of moving SwiftData out of SwiftUI first.