For the record, the setup is made easier by the xcconfig files. 1) Go grab QS source code from GitHub. 2) Build. It will create /tmp/QS/Configuration, which is an rsync-ed copy of the one in your working copy. 3) Create a new project wherever you like. 4) Drag the /tmp/QS/Configuration folder in your new project (don't "add files to target") 5) Set the project configurations to be dependent on the xcconfig files. *Delete everything that show up in bold* 6) Create a new bundle target in Xcode 7) Set your bundle configuration to the QSPlugin xcconfig files. *Delete everything that show up in bold* EXCEPT the Product Name 8) Build. You should end up with a *.qsplugin in /tmp/QS/build/Debug/ (depending on configuration).
If your plugin is to provide objects (things that appear in the Catalog pref pane), go read around QSObjectSource (mainly), QSCatalog and QSObject. If your plugin is to provide actions (things that perform things ;-)), go read around QSActionProvider (mainly), QSAction Also take a look at the existing plugins Info.plist files, most of the stuff you need to start can be inferred from them. HTH Le 22 déc. 2009 à 14:58, Patrick Robertson a écrit : > I'd also have a look at the Blacktree site: > > http://docs.blacktree.com/quicksilver/development/development > > 2009/12/22 Rob McBroom <[email protected]> > On Dec 14, 2009, at 1:46 PM, Rob McBroom wrote: > > > I’d like to attempt writing a plugin. I’m assuming the instructions at > > blacktree.com are not 100% correct any more, and the link for the template > > doesn’t seem to work anyway. > > > > Does anyone have a “blank” template? Is there such a thing? > > For the archives, this info was a good start. > > http://lipidity.com/apple/quicksilver-plugins-in-objective-c > > Looking at examples in the source of others should get me the rest of the way. > > http://github.com/tiennou/blacktree-elements > > -- > Rob McBroom > <http://www.skurfer.com/> > >
