I want to add a new section to the "Get Info" panel in the Finder, but I don't know where to start.
Everything I have found about "App Extensions" seems to refer to adding extensions to apps/applications, not the finder.
There are these two questions that have been asked, but the newest one is two years old and was never answered.
I'll gladly accept examples in any language, or a pointer to docs on how to do this; I haven't been able to find anything.
I don't think what you are trying to do is possible. At least not using publics APIs provided by Apple. You may be able to do something with techniques like SIMBL, but that's not even sure, and it requires a solid knowledge of the Mac OS X environment.
If you are new to OS X development, this is probably not the best place to start...
Related
The most recent book about Cocoa that I was able to find is Aaron Hillegass, Adam Preble - Cocoa Programming for Mac OS X - 2012, however, it's outdated (based on Xcode 4.2; doesn't contain explanation of Auto Layout) and also it doesn't explain how to create UI completely in code. (Yes, Interface Builder is cool, but sometimes one needs to take control in his hands, to generate something at runtime, etc. — so this is an important topic, too)
Is there something which is more up-to-date, now, in 2014? (be it a book or an online resource — anything goes)
I think this is a good question but it will likely be killed because it is not a specific programming questions.
Here are some pointers to get you started though:
The book you mention is now actually still pretty relevant. I would most certainly go through it. Cocoa on the Mac has not evolved as quickly as Cocoa Touch has, so a lot of material from the past years is still very relevant.
Documentation at the Mac Dev Center - Specifically, filter on the Guides and check out the most recent ones. You most definitely want to read about AutoLayout, Bindings, Modern Objective-C, and the Mac Techology Overview.
WWDC Session Videos - Apple has put these online freely, going back to 2010. There are some great sessions there. Check out all the "What's new in Cocoa" ones. And sessions with a title like "Introduction to ..."
Ask lots of questions here :-)
I would like to see more pointers to more resources too. Specifically about 'modern app architecture'. I think that is a lot more clear on iOS than it is on OS X at this point.
I know this is a stupid question, but I want to be sure. I want the old one. I have Mountain Lion.
To answer your question as fully as possible: no.
Moving on, the direction Apple has chosen to follow involves merging the previously distinct NIB editing aspects of things into the rest of the IDE, which makes quite a bit of sense - especially as you can directly create outlets, etc. by dragging from the relevant control to the header file when using the assistant view.
If it's any consolation, you'll get used to it pretty quickly.
I'm surprised no one has asked this yet. What's the best way (if any) to get a Vi experience in Xcode? I know about ViMate but TextMate doesn't come close to Xcode in terms of integration and code completion.
BTW, I am using Xcode 4.
You might want to try out xVim which seems to be an active project. The currently indicate that it works with XCode 4.2, Espresso and Chocolat. Presumably you could selectively enable it with other applications.
Here's another plugin which I made a few weeks ago.
http://programming.jugglershu.net/softwares/xvim.html
This is currently developed for personal (my) use. So you may feel bad with some lack of implementation. Give me a feed back(feature request) then. I'll add some keybinds if I have enough time.
The closest you'll get is http://www.corsofamily.net/jcorso/vi/, or configuring an external editor. This has been a long-standing deficiency with XCode. (If you ask any vi user that is..)
OSX and XCode in general favors Emacs key bindings.
More info on general key-binding strategy for OSX: http://hints.macworld.com/article.php?story=20060317045211408
Right now, I productively use XVim†. I'll probably try $20 ViCiOUS, which seems more polished; I like having source access to my tool-chain, but this is for Xcode, so c'mon me.
† Not xVim, which I just discovered, but apparently face down in the pool. In the [Xx][Vv]im namespace, Xvim (à la Xcode) would have made more sense to me. There, I said it.
Here's another choice: KeyRemap4MacBook.
I'm taking my first steps toward learning to write desktop code for the Mac and, thinking it would be a baby step, I decided to write an Address Book plugin to "fix" something that's annoyed me for a long time. Embarrassingly, I can't even get the boilerplate plugin to work the way I think it's supposed to work.
My understanding from the Programming Guide is that creating a new Address Book Action Plugin actually creates a simple, but functional, plugin. If I create a build and copy the bundle to ~/Library/Address Book Plug-Ins/, I should be able to open Address Book and see a custom context menu item when right-clicking on a phone number. I don't see that.
I'm brand new to the entire Mac development ecosystem. I've never used XCode, never written any Objective-C, never worked within the Cocoa framework. It's entirely possible--maybe probable--that I'm missing the most obvious of answers because I simply don't know what I'm looking for. Unfortunately, there's quite the dearth of beginner tutorials on these things. The programming guide itself isn't particularly beginner-friendly.
Any guidance would be much appreciated.
Sounds like a 32/64 bit problem.
Find the Target in Xcode's sidebar that represents your plugin bundle. Click on it, then click Info in the toolbar. On the Build tab of the info window, you should find Architectures: change that to "64 bit intel".
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I recently got bored and fired up my old Mac OS Classic emulator, and then got nostalgic for writing old-school applications for the system. So, my question:
Where can I get dev tools that can still target Classic? (Ideally free, since this is just for fun, but if grabbing a used version of CodeWarrior on eBay is the best way to go, so be it.)
Where can I get at least reference materials so I don't have to guess-and-check my way around Carbon/the System Toolbox?
Are there any forums still running that would be open to answering old-school Mac questions for when I get stuck?
This is purely for fun, so don't worry about how impractical this is. I know.
Where can I get dev tools that can still target Classic?
You can get Apple's command-line (yes, for Classic) developer environment, MPW, from their FTP site: ftp://ftp.apple.com/developer/Tool_Chest/Core_Mac_OS_Tools/MPW_etc./MPW-GM_Images/MPW-GM.img.bin .
The shell is fairly UNIXish, except it uses a completely different punctuation alphabet. Your backslashes, bangs, and angle brackets are no good here. You generally should use Commando instead of trying to forge command lines yourself; type a command like “make” and hit option-return to get a GUI for it.
Note that you will have to run MPW inside your Classic environment; there is no native Mac OS X version. NeXT's Project Builder (now Xcode) replaced it in the move to Mac OS X.
Where can I get at least reference materials so I don't have to guess-and-check my way around Carbon/the System Toolbox?
Google search for site:developer.apple.com "inside macintosh. Good luck—they've started burying this stuff. Currently, Inside Macintosh matches will be nothing but PDF and will have titles like “IM: Text”.
There used to be web versions of Inside Macintosh, alongside the PDFs, but I think those got trashed/concealed-too-well-to-find in the last shuffle of the documentation on the site.
Carbon documentation is more available than Inside Macintosh, which refers to the old Toolbox documentation. Carbon docs will usually say whether something is only available on Mac OS X or not. If the docs don't say, the headers will. Note that Carbon requires CarbonLib on Classic, and the last version of that was 1.6.1, IIRC.
Are there any forums still running that would be open to answering old-school Mac questions for when I get stuck?
You could always ask on Stack Overflow.
There used to be web versions of Inside Macintosh, alongside the PDFs, but I think those got trashed/concealed-too-well-to-find in the last shuffle of the documentation on the site.
Nope, here is a link:
https://web.archive.org/web/20130111022302/http://developer.apple.com/legacy/mac/library/documentation/macos8/mac8.html
I know almost zero about Classic Mac programming, but there's quite a few members of the 68kMLA that are programmers specifically working on Classic programs in general and even some very early System 6 apps specifically.
The developer/maintainer of Clasilla (http://www.floodgap.com/software/classilla/) Mozilla port to OS 9 is a profilic poster there and that is perhaps the last major project targeting the Classic environment, for example.
The wiki also has some programming resources, eg. http://68kmla.net/wiki/C/C%2B%2B_Programming_for_68k
Not that great, but it has a download link for the MPW IDE.
Unfortunately, it is not specifically a programming forum but a Mac forum in general.
Good luck though!
The site URL is http://68kmla.net
I don't know where you can get CodeWarrior.
A lot of documentation is available in the Xcode documentation reader, though much is marked "legacy" etc. You might ask questions on Apple's carbon-dev mailing list; though classic questions may be considered off-topic, the list is pretty low traffic these days. You might also want to look at the wiki at carbondev.com.
You can get codewarrior at Macintosh Garden. There are more recent versions on the site, but this is the version used for developing Classilla, a browser for OS 9, so it is probably good. To find the more recent versions, just search for "CodeWarrior". I downloaded it myself, so can verify that it works.