On Feb 13, 8:52 am, Etienne Samson <[email protected]> wrote: > Thanks ! Quick head up, I had a talk yesterday with Alcor, and > although he doesn't mind whatever we do with the QS code base, he told > me that my time would be better used on porting features to QSB than > trying to fix QS, which I do agree he's right stating this, since they > have a whole slew of developers working on the code, while I'm pretty > much alone here. Alcor also told me that he was planning to write a > "Porting plugins documentation", then he'll start converting QS > plugins to QSB.
Do you think you can get the core power features from QS *into* QSB? If so, I'd rather see that happen as QSB will have more momentum. My only issue with QSB is what Alcor via Google will and will not want let into QSB. If they don't want triggers and more advanced plugins as they deem it too complex, then QS should live. If you think you can get that stuff in, then we should all just accept the sad death of QS and the phoenix of QSB as a new paradigm. > Frankly, I'm unsure about completely selling my soul to Google, so I'm > not sure I'll ever switch from using QS (advantage from being a > developer, when it crashes, I fix it ;-)). But QSB is open-source, anyone can make custom builds stripping out anything that may be compromising privacy - this is already done for Chrome. I wouldn't worry about this. If the best QS II will come from QSB, then work from that base and benefit from help from others, otherwise if we can't get the features which make QS the best interface on the planet into QSB, then...: > This mean I could write a "Plugin porting guide" somewhere (this is > valid both for v1 and v2, since the slew of v1 plugins I got are in an > unknown state), and outsource this to those of you that have little > knowledge in development, so I can keep working on fixing bugs in QS > itself. I'll try to have a quickstart guide before the end of the month. ...it sounds as if working on Trunk is the way to go... > > I'd love to see some more Cocoa programmers willing to help you out, > > and as we've seaid many times before, I think we could get a paypal > > money pot set up to pay developer bounties on bugfixes and feature > > additions... > > About this, I guess this could be a motivating idea ;-). The issue I > have with this is that I'm unsure how much time I'll lead QS > development, since my time is pretty scarce, and the fact that I'm > improving an app alone, while QSB gets support from a full-fledged > Google team... Yes, I just don't know what Alcor feels about a bounty system... Etienne, thanks again for all your effort!!! :beer:
