monotone - Bugs: bug #15995, Expanded automate command set
You are not allowed to post comments on this tracker with your current authentication level.
bug #15995: Expanded automate command set
Submitter: | Thomas Keller <tommyd> | ||
Submitted: | Sat 04 Mar 2006 09:50:18 PM UTC | ||
Category: | command line UI | Severity: | 3 - Normal |
Item Group: | feature request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: |
|
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2006-03-04 | tommyd | Carbon-Copy | - | Added tommyd |
Powered by Savane 3.13-f8d8.
Corresponding source code
Hi!
I'm currently working on a Qt-GUI for monotone, named "guitone". Well, this is not very far as of now, but I'm working on it quite hard to get something reasonable out there.
To communicate with monotone I wrote a wrapper around "monotone automate stdio", with which I can do basic things like checking the inventory (and the state of each item). Now, to do more advanced things like adding/dropping/renaming/committing items I can't use "automate" at all since the functionality does not exists in the interface yet. I could, of course, use the normal UI functionality to do these things, but
a) these are (will be?) language dependent and hard to parse therefor
b) I don't like to built two wrappers, one for stdio and one for all other calls...
So it would be really, REALLY nice if the automation interface would reflect the actual command set available through monotone, or, as a starting point, at least those things which are most-often used.
Tommy.