The branch for current QS releases is "branches/B5X" "trunk" holds the next big thing with significant API chances and therefore all B5X plugins are incompatible for the trunk version.
Main classes are QSApp, QSObject, QSAction. etc. But if you wrote plugins you most likely know all that. A "trick" which helped me to get a better picture of the whole is to let Xcode build a Data Quick Model of each of the QS frameworks. To do that: 1. In Xcode select all header and implentation files which belong to a framework (e.g. group "Code-QuickStepCore" for QSCore.framework) in their respective Xcode group. 2. With the selection chose Design > Class Model > Quick Model from the Xcode menu. 3. Explore DAG of the complete object hierarchy. To get it to build you will need to open in Xcode the group "Configuration" and find the file "Developer.xcconfig". You need to adjust the path given for QS_SOURCE_ROOT in that file. That's absolutely crucial. It also doesn't hurt to define the same path setting in Xcode's Source Trees (via Preferences) again for a variable named "QS_SOURCE_ROOT". You can check if Xcode got the path (s) right if you open build prefs and look at the User-Defined Settings. Two entries should be visible: QS_SOURCE_ROOT and QS_APP_CONTENTS_FOLDER which both should take the path you have set for QS_SOURCE_ROOT into account. Also, if you get weird build results sometimes it's needed to open the build prefs on both project and target level and adjust the "based on" setting in the lower right corner of the build prefs pane. Pick one of the build styles provided by the xcconfig files. (Debug for devlopement, Release for distribution, QSPlugIn_Debug/Release for plugin development). Be aware that the Quicksilver target has a run script phase which uses rsync to overwrite /Applications/Quicksilver.app with the build product! Hope everything works out for you. Nice to see more devs are jumping on board :) Cheers, André On 29 Aug., 22:27, Jordan Kay <[email protected]> wrote: > And by Twitter, I mean Quicksilver. :)
