I have fixed some formatting in the area of the fix. This will
probably create an svn conflict when you svn up. Just be aware and
resolve the conflict in favor of the patch I have committed.
Best Wishes,
Chris Travers
On Thu, May 19, 2011 at 12:51 PM, Erik Huelsmann wrote:
> When selecting:
>
When selecting:
Cash -> Receipts
and clicking on Continue on the subsequent screen, I'm presented with
3 lines (I have 3 companies defined in my testing database) and 3
columns: a line number in the first, a radio button in the last and an
empty column in the middle.
The middle column should con
On Thu, May 19, 2011 at 8:27 PM, Erik Huelsmann wrote:
> Hi Chris,
>
> I'd like to change the AR screen to say "To receive" instead of "To
> pay" and replace all occurrances of "Vendor" to "Customer" and send a
> patch with that change.
>
> However, there are 3 files called payment.pl... where do
On Thu, May 19, 2011 at 12:02 PM, Luke wrote:
>> The API reference currently covers the perl modules, but not the
>> workflow scripts, or the SQL functions. The workflow scripts it isn't
>> clear to me what sorts of documentation on the functions there is
>> helpful. The SQL functions are usual
On Thu, 19 May 2011, Chris Travers wrote:
> One thing that a tremendous amount of effort has gone into in 1.3 is
> code documentation both with the old code routines and the new ones.
> This documentation is subject to its own set of tests to determine
> coverage within certain parameters, and so
Hi all;
One thing that a tremendous amount of effort has gone into in 1.3 is
code documentation both with the old code routines and the new ones.
This documentation is subject to its own set of tests to determine
coverage within certain parameters, and so forth, but it will need to
be reviewed aga
Hi Chris,
I'd like to change the AR screen to say "To receive" instead of "To
pay" and replace all occurrances of "Vendor" to "Customer" and send a
patch with that change.
However, there are 3 files called payment.pl... where do I start?
Bye,
Erik.
On Thu, 19 May 2011, Chris Bennett wrote:
> Installation is too difficult
> Since 1.3 is really just a development phase, I think this issue can be
> put at a lower priority
> than documentation, but not too low.
I think I disagree with that, at least somewhat, from two prospectives:
First, whi
Hi Chris,
Thanks for stepping up!
> >From reading this thread, and not having looked at 1.3, it seems that some
> >very particular issues
> are desperately needing to be fixed. These issues seem to be fairly unrelated
> as far as what skills
> are needed.
>
> Documentation - both for usage, ins
I was lightly involved a good while back, but I had to basically close down my
business for a while
to care for my handicapped mother.
>From reading this thread, and not having looked at 1.3, it seems that some
>very particular issues
are desperately needing to be fixed. These issues seem to be
10 matches
Mail list logo
