Proposal: separate script interface
aaron.bentley at utoronto.ca
Fri Jun 10 18:01:57 BST 2005
-----BEGIN PGP SIGNED MESSAGE-----
John A Meinel wrote:
> I would make a few small points
> 1) For now, bzrlib *is* the scripting interface. It has all the
> functionality and everything exposed. It doesn't work quite as well for
> shell scripting, but it works great for python scripting.
The Tailor support for bzr and the Bugs Everywhere support for bzr are
implemented by invoking bzr, not by using bzrlib.
> 2) I vote for having a separate front-end. I'm also concerned about the
> difficulties in maintaining 2 code paths.
I don't agree, because the purpose of the Command classes is to
interpret the user input. The real work is (or should be) done
elsewhere. In my view, trying to handle two different input styles in
the same code would reduce its readability, and make it likely that
changes to the user UI could affect the scripting UI, and vice-versa.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar