API issues

[Scott James Remnant]

Hey Martin,

A few bzrlib API issues that have made implementing something based on
top of it a little tricky.


smart_add_branch() is great, we can pass in a branch object and a
reporter callback function and get the feedback we need.  Though it
feels wrong calling a separate function -- could this not be bzrlib.add
itself?

Could we have something like this interface for .remove() as well?
Right now we're having to do half the work ourselves to figure out what
to pass to Branch.remove() and what it's likely to actually remove.
Being able to have a reporter function for this would be a god-send.

Same for branch.commit(), as well as having verbose off by default --
perhaps implementing that for bzr as a reporter function instead?

It'd also be kinda cool if the reporter function happened before the
event, so you could raise an exception there if something's about to
happen that you don't want.

Thanks,

Scott
-- 
Scott James Remnant
scott at ubuntu.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050915/1ce16905/attachment.pgp