3 ms·
I’m sorry to knock down OP here but I’ve been doing Mac development for a long long time. A default app to me as a bare minimum involves: • Custom Application
by julius_set 7y ago
I’m sorry to knock down OP here but I’ve been doing Mac development for a long long time.
A default app to me as a bare minimum involves:
• Custom Application class
• URI specifications
• Custom NSDocument
• Custom window controller
• Customized NSToolbar
• CoreData support
• “Feature” targets / I.e. Todo target
I’ve written a script which sets and generates all this for me:
macapp new —with-ui —styles
- tylerhall 7y agoOP here. I think we're aiming for the same thing - though with slightly different priorities. Of your list of minimums that DefaultApp omits: Not every app adheres to a Document-based pattern. The apps I personally build typically fall into a "shoebox" style where explicit documents aren't used. And there are other data layers than CoreData, which is why I didn't add that - especially since even with CoreData everyone has their own favorite library/framework. So that's easy enough to drop-in for those who want it. (That said: probably 95% of the apps I write use CoreData, so ) A customized NSToolbar would be great, but, again, there are so many implementations out there, which one would you pick that would satisfy the majority of apps/developers? Anyway, like the accompanying blog post says, this project is "highly opinionated". It's just what I've cobbled together over the years. I'm not going to die on a hill for any of my particular choices. Do what works best for you.