Hey Ankur, Good to see you're still about and would like to help some more!
We're just in the process of moving the Quicksilver code over to a new repository at: https://github.com/quicksilver/Quicksilver so as to make things easier for people to know what's where. We'll be using this and the corresponding /Plugins repo for our QS work now. The QSApp.com site will have some dev documentation, basically what we can take from Alcor's blacktree.com site (there may be a bit there, but the site seems to be extremely iffy/not working at the moment). Another good place to look (although it's more directed to creating plugins, but does have some info on QS itself) is Rob's Development Reference: https://github.com/quicksilver/Plugins/tree/master/PluginDevelopmentReference I'll add you to the two 'new' repos if you have a Github account (let me know what it is). I'm also looking at setting up (or using the existing) developer mailing list so we can start sharing our info. Patrick On 5 December 2010 20:20, Ankur Oberoi <[email protected]> wrote: > just joining this group now because i really miss quicksilver, and now > that i have SOME obj-c development skills, i'd like to see if theres > anything i can do. > > will qsapp.com have room for any developer documentation? is there > developer documentation that exists? im not really great with git and > it seems like theres a few diff projects (not just branches of > projects) with the codebase for quicksilver. this is quite confusing. > anyway i may be able to dedicate some time to this project so i'm > wondering where i can help. > > On Nov 19, 6:54 am, Patrick Robertson <[email protected]> > wrote: > > From QS's point of view, it needs to make something like this: > > > > http://qs0.blacktree.com/quicksilver/plugins/plugininfo.php?qsversion... > > > > i.e. a .plist / xml file that QS can then parse to get the list of > plugins. > > > > On 19 November 2010 20:26, <[email protected]> wrote: > > > > > > > > > > > > > > > > > out if interest, are there any requirements of the plugin page from > > > quicksilver’s point-of-view? > > > does it need some generated xml representation or ? > > > > > On 19 Nov 2010, at 04:25, Patrick Robertson wrote: > > > > > > @Brett > > > > > > The plugin repository I made was just a quick/rough 'test', the idea > is > > > to make a much more full proof version with descriptions like you get > in > > > Quicksilver itself. > > > > > > We need to work on building this new repo, and adding information. > > > > > > If you want to start making e.g. a spreadsheet with a list of all the > > > plugins, their version numbers, dates and descriptions that would be an > > > awesome start! > > > > > > The 3rd party plugins have come from various sources - people > emailing me > > > stuff, and stuff that's already available as open source by Alcor. I > guess > > > tracking down and finding where everything's come from would be another > good > > > idea. > > > > > > ( > > >https://spreadsheets.google.com/ccc?key=0Ah_3obKwBvxsdGxxSVIyVm93OG5w.. > .) > > > > > > I've installed a wiki at: > > > > > >http://qsapp.com/wikifor the exact idea of a place for everything to > be > > > stored. > > > > If you want to start editing that as well then go for it! > > > > > > * The plugins repo wouldn't be a replacement to Howard's manual of > > > course, only the descriptions would be included. > > > > There would be plenty of links to the awesome manual though :) > > > > > > On 19 November 2010 14:25, Howard Melman <[email protected]> wrote: > > > > That's why I wrote this manual: > > > >http://mysite.verizon.net/hmelman/Quicksilver.pdf > > > > Though it's current to B54 only. > > > > > > Howard > > > > > > On Nov 18, 2010, at 9:01 PM, Brett wrote: > > > > > > > Perhaps I'm missing something, but what would be great would be to > > > > > have some sort of a more detailed description included in the > plugins > > > > > repository. Maybe I'm slow, but "Event Triggers" tells me very > little > > > > > about what the plugin actually does. > > > > > > > As part of this ambitious project, perhaps a wiki (or github, or > right > > > > > here in googgroups, etc) could be used to provide documentation for > > > > > all plugins. Would be a huge effort of course, but at the moment, > > > > > determining what each plugin does, and how to configure it or > utilize > > > > > it in QS is sometimes a bit mystifying. > > > > > > > I'd be willing to help with this effort - > > > > > Patrick: for your QSApp.com repository of plugins, do you have info > on > > > > > the authors/URLs where each 3rd party plugin came from? > > > > > > > On Nov 14, 2:17 pm, strug <[email protected]> wrote: > > > > >> Good timing:) The blacktree.com site has been suspended. Would be > > > very > > > > >> cool if we already have the possibility to tell QS to use your > plugins > > > > >> repository. > > > > > > >> For the time being it might be helpful to describe what is > necessary > > > > >> to use your plugins. E.g. s.th. like: > > > > > > >> - download your plugin > > > > >> - unzip it > > > > >> - move the *.qsplugin file to /Users/<you>/Library/Application > > > Support/ > > > > >> Quicksilver/PlugIns > > > > >> - restart QS > > > > >> - select plugin > > > > > > >> Thanks for saving my night, leif >
