Bo-Keep - Tasks: task #11090, stand-alone shell
You are not allowed to post comments on this tracker with your current authentication level.
task #11090: stand-alone shell
| Submitter: | Mark Jenkins <markjenkins> | ||
| Submitted: | Fri 15 Apr 2011 12:17:40 PM UTC | ||
| Should Start On: | Fri 15 Apr 2011 05:00:00 AM UTC | Should be Finished on: | Tue 31 May 2011 05:00:00 AM UTC |
| Category: | None | Priority: | 5 - Normal |
| Status: | Done | Privacy: | Public |
| Percent Complete: | 0% | Assigned to: | markjenkins |
| Open/Closed: | Closed | Effort: | 15.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
Follow 2 latest changes.
| Date | Changed by | Updated Field | Previous Value | => | Replaced by |
|---|---|---|---|---|---|
| 2012-06-13 | markjenkins | Status | Postponed | Done | |
| Open/Closed | Open | Closed |
Powered by Savane 3.12.
Corresponding source code

We develop the ultimate idiot proof shell where you don't have the power to configure bo-keep, configure plugins, change books, change transaction type, navigate between transactions, and explicitly create or delete them. This one will operate plugins in a stand-alone mode where you are only responsible for one transaction of a particular type at a time. When you reach and signal some kind of "done point", your relationship with the transaction is "done" and you're then working on another new transaction of the specified type.
I envision this being most useful for folks using the "end of night cashout" example configuration that will be developed for the multi-page-glade plugin and the eventual port of the ParIT Cash Register (http://parit.ca/products/parit-cash-register) to being a Bo-Keep plugin.
And I imagine some variations for this -- at the "done" point we can either close the window and have the new transaction start once the shell is re-launched (cashout case) or keep the same window and continue operating on the same transaction there.
Further -- an idiot-proof stand-alone shell can be configured to be obtrusive on close or at the "done" point if it makes sense (cashout case) -- perhaps by checking get_financial_transactions() and saying "we don't have something book worthy yet, are you sure you want to leave me?"