← Back to team overview

bzr-explorer-dev team mailing list archive

Re: Integrating Plugins with Bzr-Explorer

 

2010/1/27 Ian Clatworthy <ian.clatworthy@xxxxxxxxxxxxx>:
> Simon Kersey wrote:
>> Further to my previous mail I have now fixed some ‘features’ of my
>> previous patches.  In particular I have stopped the crash when Explorer
>> is minimised and a working tree linked toolbar is displayed.
>
> Well done. I've reviewed these patches now and they generally look good.
> See my comments below. (I'm copying the main Bazaar list as some details
> below will most likely interest a wider audience than just the explorer
> devs.)
>
> Firstly though, here's an update on my thinking re custom toolbars ...
>
> I want to have different toolbars for different location kinds, e.g. the
> actions for a repository will be different to those to a branch,
> bound-branch or checkout. For example, 'switch' might be on the toolbar
> shown for checkouts while multi-pull might be on the toolbar for
> repositories.

This would certainly be useful: we use centralised operation with
heavyweight checkouts exclusively (partly for network latency reasons
and partly because bzr-externals doesn't work with the lightweight
ones) and it's a bit odd having "switch checkout" (which is used
regularly) hidden under the work button but "push" and "pull" (which
are rarely, if ever, used) at the top level.

> I want users to be able to tag locations with a "logical kind" as well.
> For example, you might want to say this is a "review branch",
> "pipeline", "packaging branch" or (bzr-builder) "recipe". A new dialog
> will be added (File --> Properties) that shows the name and kind of a
> location and lets you set/unset the logical kind. (BTW, logical kinds
> will have icons that are displayed in place of the actual kind's one on
> tabs, etc.)

Sounds like an interesting concept.  It would be nice if plugins could
also get involved with customising these (and other) settings.  It'd
also be nice if they could replace existing dialogs with custom ones
for workspace model specific operation.

I really like the new workspace model thing: being able to customise
Bazaar Explorer for the way we work without having to maintain _too_
many extra patches has got to be a good thing.  It would be nice to be
able to customise the _names_ of some of the commands as well as which
ones are present: this could help reduce the number of times I have to
explain terminology to people (e.g. "Use 'Switch Checkout' to create a
Branch and use 'Branch' with the 'Bind' option to create a Checkout).

Al

-- 
http://sites.google.com/site/abudden



References