Thanks for the points. I'm checking out the source code now and I'll
take a look. My biggest reservation is the fact that I don't know
much about the dev environment QS was written in. I'll poke around
and see if I can figure anything out.
It would be nice if I could at least get a local build running on my
box(es).
- Griffin
On Jun 2, 2008, at 2:03 AM, nontoppo wrote:
On Jun 2, 1:51 am, Griffin Caprio <[EMAIL PROTECTED]> wrote:
Does anyone have any information about the current state of both
branches? Both source locations as well as what's broken ?
http://code.google.com/p/blacktree-alchemy/source/list
QS II on trunk (for want of a title) had a heap of activity over
christmas. It is a restructuring of QS, from the readme:
Trunk contains the source for the experimental version of Quicksilver.
It differs from the released version in the following ways:
* Triggers are moving to a separate product, called Catalyst
* All the little frameworks are being joined into one big one called
Crucible. This includes extensions and core functionality that most
apps and plugins will use. This is currently called QSBase.framework
* The preferences are going to get MUCH simpler. There will be
Extras-style advanced prefs for the fiddly options.
* Plugins are going to be hidden from most users, they'll activate
themselves automatically or be installable from the web
* B5X Plugins are incompatible, mostly because that architecture was
a mess.
--------------------------------
Crucible
A framework with extension to AppKit and tools common to all Alchemy
apps
Elements
A framework supporting the plugin architecture
Quicksilver
Command window driven launcher
Catalyst
Triggers preference pane
B5X is the branch which the curent QS is built from. Ankur did some
work on it (a build off rev76) and has claimed he has done a bunch
more (reducing QS's memory consumption, though hasn't merged it yet),
though has no time until the end of this year to take things further:
http://lipidity.com/apple/quicksilver/quicksilver-cleaned/
http://lipidity.com/software/quicksilver/
That branch is working though with the leopard bugs and crashes we've
all noted. Fixing up the leopard bugs seems entirely reasonable with
B5X and would be an enormous boost for all QS users.
It seems as though "Stepping on Alcors shoes" is almost a non-
possibility at this moment because he doesn't have the interest /
time
to take QS further.
No idea, there was lots of activity on QS II and we don't know if it
will pick up again as he hasn't said one way or the other.
Rather than working on the B5X branch (depends on Alcor to accept your
work?), I think people should just branch off and do what they can
(ideally several devs working together). A legion of QS users will be
in your debt (and willing to beta test extensively) :-)
