Otherwise you’ll have to hunt for them with the “Add Other” button. If you got copied the growl frameworks into the right folder, they will show up in the list. ![]() Pick one of the framework groups (I chose “Other” for no apparent reason), right click and “Add Existing Framework”. Open Xcode and your project, and locate Frameworks in the project tree view. This will make them easier to find from within Xcode.Īdding The Growl Framework To Your Project Paste these into /Library/Frameworks on your OSX drive. Open the disk image, and in the Frameworks folder, copy both the “amework” and “amework”. Go download the Growl SDK from the Growl website. A few google searches later and I realized Growl delivers a nice framework package from their website. Xcode comes with several examples of how to work with Growl, but I found them all to be difficult and couldn’t get them working correctly. Start up Xcode and create a new MacRuby project. ![]() Getting Started – Xcode And The Growl Frameworksįirst, you need a Mac and you need to install the latest and greatest Xcode. So, in an effort to help the community a little more, I am going to try and post a complete tutorial on creating a MacRuby app with Growl notifications. I found a few tutorials, various forums and even a few bug tickets that generally gave me the information I needed, but I had to put it all together myself. One of the goals of the app that I want to build is to show Growl notifications at various times, so I started digging into what this would take. I was able to find some simple tutorials to get me moving and started putting together some simple native OSX UIs pretty quickly, with UI elements that actually do things. I have to say, I’m quite happy with it so far. In an effort to get up and running on XCode and Cocoa as quickly as possible, a number of people suggested I check out MacRuby. I’ve been wanting an excuse to learn how to code for OSX for a while now, and I finally thought of a project worth trying. Creating Growl Notifications From A MacRuby App 21 January, 2011.
0 Comments
Leave a Reply. |