state of quicksilver development?

[Joshua Bronson]

The latest Quicksilver version available on blacktree.com is b54 (from
Dec. 2007), but I noticed more recent versions are available from
http://code.google.com/p/blacktree-alchemy/downloads/list. The home
page of the Google Code project says:

> A few notes about the source trees:
> * Trunk contains the most recent version of the source. It it still very experimental.
> * A B5X branch contains the most recent release versions, but it is only changed for critical issues. All major work happens on the trunk.


I'd love to know a bit more about what's been going on both in trunk
and on the B5X branch. I've just installed b56a7 to have a look and so
far I've just noticed fewer available plugins. (Speaking of which, I
really miss the Extra Scripts plugin. If there's work that needs to be
done to update it to work with b56, I might be able to help if you can
provide an outline of the status.)

Thanks,
Josh

[Kurt]

On the same subject... I'd love to have "Show Menu Items" working with
the new Galileo version of Eclipse, now that it is cocoa-friendly.

- kurt

On Jul 15, 12:10 pm, Joshua Bronson <jabron...@gmail.com> wrote:
> The latest Quicksilver version available on blacktree.com is b54 (from

> Dec. 2007), but I noticed more recent versions are available fromhttp://code.google.com/p/blacktree-alchemy/downloads/list. The home

[nontoppo]

Trunk is largely dead IIUC - alcor went off to work on QSB, and
etienne is maintaining B5X over trunk - though I noticed etienne
recently commiting lots to crucible, which is the new core library
that was going to go into QS trunk.

B5X has substantial fixes for Leopard (triggers etc.), folded in lots
of changes made to reduce memory use and "bloat". But etienne only has
partial access to plugin code so can only do so much; alcor still
hasn't released some of the plugin code. Some fixed plugins are
available here:

http://code.google.com/p/blacktree-elements-public/downloads/list

etienne is the only real person working on code at the moment,
including fixing things up for snow leopard etc.

[Joshua Bronson]

Thanks for the info. I'm not familiar with the alcor and etienne you speak of, but I take it alcor was a core developer who left the project to work on http://code.google.com/p/qsb-mac/, and that ettiene is the real name of http://code.google.com/u/tiennou7/ (whose activity on http://code.google.com/p/blacktree-quicksilver/ is apparent enough)? If you feel like providing a bit more of the Who's Who In Quicksilver (including yourself!), would be interested to know. :)

I just stumbled across http://lipidity.com/apple/cleaning-up-quicksilver/, and it seems like this Ankur is another player in this, or at least was... The most recent post, http://lipidity.com/apple/the-state-of-quicksilver/, is dated 11/28/08. Judging by the comments on his blog though, there seems like sufficient community interest in contributing code and/or money to keep the project going. Would be happy to contribute some or both myself!

Could anyone provide a bit more insight into Quicksilver's roadmap, so that e.g. someone interested in getting started contributing could have a sense of what needs to get done first to move the project forward? Or if it's a case of Just pick something on http://code.google.com/p/blacktree-quicksilver/issues/list and have at it, fair enough.

One thing I volunteer to do straight away if there is interest on the part of the project owners is to add some "Interested in contributing? Here's how..." mojo to the project's wiki. Once I figure that out. :)

Thanks,

Josh

[Jon Stovell (a.k.a. Sesquipedalian)]

Ankur did help out with some development for a while, but I don't
think he's been around much lately. If you can code, by all means send
an email to Etienne (tiennou7). I'm sure he'd be glad of the
contributions, and he really would be the one to talk to if you want
an orientation to the code.

As for the rest of us around here, Howard Melman (hmelman) is the
author of the unofficial user guide, and Howard and I moderate this
group together. Aside from Etienne and the occasional code
contributor, we are all just users helping users.

Alcor hasn't released the code for all the plugins, but has indicated
that he is willing to release the code for individual plugins when
requested. So if you want to work on improving a plugin, you can email
him about it.

Also, note that there are actually two Google Code pages related to
Quicksilver. http://code.google.com/p/blacktree-quicksilver/ is really
just a bug tracker. http://code.google.com/p/blacktree-alchemy/ is
where the real stuff happens.

On Jul 25, 9:10 pm, Joshua Bronson <jabron...@gmail.com> wrote:
> Thanks for the info. I'm not familiar with the alcor and etienne you speak
> of, but I take it alcor was a core developer who left the project to work

> onhttp://code.google.com/p/qsb-mac/, and that ettiene is the real name ofhttp://code.google.com/u/tiennou7/(whose activity onhttp://code.google.com/p/blacktree-quicksilver/is apparent enough)? If you

> feel like providing a bit more of the Who's Who In Quicksilver (including
> yourself!), would be interested to know. :)

> I just stumbled acrosshttp://lipidity.com/apple/cleaning-up-quicksilver/,

> and it seems like this Ankur is another player in this, or at least was...

> The most recent post,http://lipidity.com/apple/the-state-of-quicksilver/,

> is dated
> 11/28/08. Judging by the comments on his blog though, there seems like
> sufficient community interest in contributing code and/or money
> to keep the project going. Would be happy to contribute some or both myself!
>
> Could anyone provide a bit more insight into Quicksilver's roadmap, so that
> e.g. someone interested in getting started contributing could have a sense
> of what needs to get done first to move the project forward? Or if it's a

> case of Just pick something onhttp://code.google.com/p/blacktree-quicksilver/issues/listand have at it,

[nontoppo]

On Jul 26, 2:10 am, Joshua Bronson <jabron...@gmail.com> wrote:

> I just stumbled acrosshttp://lipidity.com/apple/cleaning-up-quicksilver/,

> and it seems like this Ankur is another player in this, or at least was...

These changes were already added to the B5X tree so they are included
in our current ß56a7.

I've raised the idea to set-up a war fund to help QS along, but I
think the devs who would contribute would then face a pretty big
pressure. The current info suggests ß56a7 works OK on Snow Leopard,
and so we at least know we have a future for the next couple of
years.

QSB is still far from the elegance and power of QS, and they seem to
have their priority which is an interface to google services rather
than a general purpose tool (there are a huge number of votes on the
three feature bugs for a third pane/action function, triggers etc.
which still aren't assigned to a developer).

[Joshua Bronson]

Thank you for the info and the intros. I'll get in touch with Etienne if I get a chance to start looking at the code at some point.

[Stefan Magdalinski]

The information in this thread is sufficiently useful that someone
should summarise it and stick it on

http://code.google.com/p/blacktree-alchemy/

If that page were a wiki, I'd do it.

stef

--
/*
Stefan Magdalinski
+447769 666528 (phone)
smagdali (IM/twitter/flickr/dopplr/skype/etc)
*/

[Joshua Bronson]

On Tue, Aug 4, 2009 at 2:27 AM, Stefan Magdalinski <ste...@whitelabel.org> wrote:

The information in this thread is sufficiently useful that someone
should summarise it and stick it on

http://code.google.com/p/blacktree-alchemy/

If that page were a wiki, I'd do it.

+1. Anyone on this list have write access to the project?