On Feb 13, 3:52 am, Etienne Samson <[email protected]> wrote:
> Le 12 févr. 09 à 23:36, nontoppo a écrit :
> 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 ;-)).
Google is a great company, but QSB ain't QS, and I don't think we'll
be able to make it so.
>
> Frankly, there are only (IIRC) two fundamental changes in v2, this is
> the new plugin architecture, and the fact that triggers are outsourced
> to Catalyst. This means almost everything else is copied code from v1
> (without the changes I made), so I'm almost restarting from scratch,
> but with a much more robust plugin system. The problem I see with
> improving v1 is that I cannot fix some of the fundamental issues in
> the code :
> - the fact that QS model doesn't handle serialization nicely, which
> is shown by trying to make a trigger using an encapsulated command
> - the fact that the class named QSCommand (which is used by the
> trigger system) is a recent addition, and thus isn't used anywhere
> else, where it could be used in the command interface and allow for an
> arbitrary number of arguments, and some others I don't remember ;-).
>
> 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.
I'm a C & Ruby developer, but saving quicksilver is the kind of
project for which I'd be happy to learn a new language. I could start
with some plugins ports as soon as you have that guide available.
> 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...
>
> Etienne
I'm willing & able to assist the development however I can.
