development contribution (business-..)

[Rich Johnson]

On Tuesday, November 30, 2004, at 11:00 AM, Derek Atkins wrote:

> Rich Johnson <rjohnson at dogstar-interactive.com> writes:
>
>> Well, it's time to stop lurking and start contributing.
>
> Excellent!
>
>> My main complaint lies with the business UI dialogs.  I find them to
>> be clunky.  I'd like to see some(all) of the following:
>>   - pop-up lists of vendors (enter bills dialog)
>>   - pop-up list of vendors with unpaid bills (pay bills dialog)
>>   - amount owed to specific vendor in pay bills dialog
>>   - keystroke entry of vendor name in bill entry/payment dialogs
>>   - auto-completion of vendor name in bill entry/payment dialogs
>
> FYI, pop-up lists are going to be hard because, technically, you don't
> ever have a list of all vendors (or customers, or employees).  They
> are all database searches, and API-wise the only way to get a list is
> to perform a database search ...[snip]

Well, given that currently one must use either [Search...] or use data 
validation of a typed name; there's already a database search involved. 
    In any case I've got a learning curve to scale and I'm a long way 
from even thinking about implementations.

>
>> I propose to start by adding documentation for the functions in
>> business/business-core.   How about it?
>
> Are you looking at the HEAD branch in CVS?  Lots of the functions are
> already documented there.  If you're not working in HEAD, you probably
> should (or perhaps the G2 branch).  Docs should be updated in HEAD.
> UI work should probably be done in the g2 branch.
>
>> Anyone want to help me get off on the right foot?
>
> Do you have specific questions?
>
I'm starting with HEAD--and sticking to function descriptions for now.
I thought I'd start with gnc{Vendor,Customer,Business}.[ch] and play 
around with doxygen.  (You wouldn't happen to have a Doxygen 
config-file lying around somewhere, would you?)

No specific questions yet, but they'll come up.

First rule:  Break no code!
Second rule:  Don't assume semantics

--rich