-----Stefan Küng <email@example.com> wrote: -----
> But of course you're right that we can't add a button (or whatever)
> for every possible custom functionality.
I totally agree so I suggest implementing it sufficiently generic that it
will work for more than just what I want to use it for, just in a way that
does not throw me back at the hooks, I don't like them for this ;-)
> There is some space left right of the "Recent messages" button.
I would like to use that space. For myself I'd be happy with one button
only, but making it more generic I can imagine that people can come up with
more things they want to add a button for, let's say up to three buttons
(that's the number I'm going with, below).
So this is now my proposal:
Introduce three properties:
where x is 1, 2, 3; this allowing for multiple buttons to be
added through this feature
first line: path and filename to an executable file
second line, optional: button caption
Properties being set will make the corresponding buttons become available.
We could do smart things with this as in nicely filling the available room
based on the number of buttons that have their properties set and should be
A button will obviously execute the file that is configured for the button.
It should be possible for this to be either an executable binary (file://)
or some web page (http://). This would work for my companion software but
also for opening your whatever-web-based-bugtracker.
To make this really work the first line of the property value must allow
for some escape characters to be used. I make a suggestion below, the
formatting with percentage signs I took from the existing BUGID.
%REPOS% (the repository URL)
You may think of many other escape characters. Please add ;-)
Once I get some agreement that this might indeed be a good feature, can I
code it and contribute, or how does that work? (Sure, you code it if you
want to, but I'd be happy to contribute, since I am the one asking.)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Aug 24 18:54:12 2006