David Overcash

Results 37 issues of David Overcash

Rely solely on $this->_data when it comes to API functions. As an example, the following lines should not exist: https://github.com/system76/beansbooks/blob/master/application/classes/beans/vendor/purchase/invoice.php#L41-L48 They should be replaced with local values in _execute() that...

Planning
Design Pattern

Include checks for various actions that cannot take place and properly notify the user rather than relying on eventual error messages from the API. Editing transactions in a closed FYE....

User Experience

Dash reports should not reflect starting balance entry. Best solution is probably to not start reports until after starting balance - but that would probably yield trying to split a...

The Account Journal needs to be updated to have the following features: - Jump to transaction goes to both the account and the transaction. - Jump to month should load...

Feature
User Experience

See #75

Feature
User Experience

See #75

Feature
User Experience

When printing checks, you must make sure that the browser / printer ignores any possible scaling. This is usually done by checking a box that says "Ignore scaling and print..."...

User Experience

BeansBooks currently records and encrypts all user actions that are taken, including the resulting data that is generated. The goal of this is two-fold: to be able to provide valuable...

Feature
Planning

Some form creations have incorrect parameters that don’t match their return types ( or the return types are incorrect as well ). As an example, Beans_Customer_Sale_Create accepts data->lines[]->sale_line_taxes - this...

Feature
Design Pattern
Documentation

Currently, several object types have both a _Delete and _Cancel - where the _Delete method will completely remove it from the database, and _Cancel will only reverse it in the...

Feature
Design Pattern
Documentation