Thanks for the feedback here, folks ;-)
I'll cherry-pick stuff from your replies, and reply again.
Dorian said :
One idea they use in there version releases is ditching the old code
and starting over with the key parts. I think the same should be
applied here. Just focus on development of v2 of QS. (which has
started already).
Yes, this is what I had been planning to do, because trying to fix v1
(fix in the sense of fixing QS) means I'm likely to break people's
existing installations. I agree we should be able to make some bugfix
releases for the v1 branch (which is what I started to do, but then do
dragged by the amount of stuff that looked wierd to me, and thus
required a more consistent rework).
That said, as someone who has no knowledge of programing am more
concerned with testing out the bleeding edge of QS. First we need some
method of a lot people test out the current builds without effecting
there current setup (much). Using the current builds seems to be hit
or miss with people. Basic funcations such as activation QS just don't
work for some people. I would like to know if the current plugin
system ready to have plugins? if so, i think documention is in order.
Triggers would be the next to that would needing solidifying.
IIRC, v2 is able to recieve plugin, but as you say, it requires
documentation. It's not completely different from the old system
(which stores plugin stuff in Info.plist), because I've been able to
slacking port old plugin to the new architecture without much trouble
(means I just had to write the element.xml file, converting it from
the data in Info.plist, and it was at least partially working.
For triggers, this is another kind of problem, but I guess I'll have
to redive into the trunk code to remember what was the point...
Summer of Code should a great place to get some more talent apart of
the comunity. We really should look into that once it's annouced this
year.
We could do that, but frankly, the issue I have is that no one (even
me) knows the full intricacies of the code base. And there is stuff in
there that are badly in a need of rewrite (IMHO, all the view stuff).
Another thing is we need more information on the code base landing/
homepage about Quicksilver. Speaking of documentation, what is our
standing with the current Quicksilver documentation page on Alcher's
site? Alot of it is out of date now. Maybe we should look in starting
our own page but linked from Blacktree's page?
I think most of the docs out there still applies, but I haven't
checked it thorougly...
Finally, we do have an IRC chat room, but is mostly dead.
irc://irc.freenode.net/quicksilver I'll be there under ErifNeerg. I
really think that should help start talking more. (if you looking for
a client, I've been happy with Colloquy)
I do agree having some dedicated chat place would be a great thing,
the main problem is Earth's curvature ;-). I'm in France (GMT+1), so
most of you won't be online when I will. I had this issue with Alcor
too.
Howard said :
To me, the most annoying thing about QSB is that while I thought the
QS main trunk was the future of QS, it seems it really is QSB unless
some dev group forms to take over either of the QS code bases.
Let's not let this happen then ;-).
Now, I will make a few updates to both codebases so that everyone can
build, starting from scratch. The last thing I was trying to do was
consolidating the build system again, so I could easily integrate the
slew of plugins Alcor gifted us with, and trying to prevent it from
rebuilding everything as soon as I changed one file. But this has been
fraught with hazards and was boring as hell ;-).
More on development later.
Etienne
