[Ledger-smb-devel] PGObject framework todo's to be ready for use in 1.5

2014-02-15 Thread Chris Travers
Hi;

I will be releasing PGObject::Simple 1.5 shortly which will support a
contextual return, so if you $ref = $object-call_dbmethod(...) it will
return the of the result set.  This will then be supported in
PGObject::Simple::Role.

At this point, for a stable framework there I only have one other todo
item, namely to modify PGObject::Simple::Role so that it handles lazy
attributes properly.  Handling lazy attributes (i.e. attributes which are
first set when they are requested) is something that the current 1.4
framework doesn't do so well.  This would eliminate one significant
headache.

The other thing I want to do is remove the dbmethod() syntax entirely from
PGObject::Simple::Role.  This has been moved into PGObject;:Util::DBMethod,
which has a significant number of advantages.  Classes can simply use this
class and then be able to:

dbmethod save = (funcname = 'save');

instead of a more cumbersome

sub save {
my ($self) = @_;
return $self-call_dbmethod(funcname = 'save');
}

Or for more features:

dbmethod save_as_new (funcname = 'save', strict_args = 1, args = {id =
undef});

Once these are done, I will release PGObject::Simple::Role 1.0  I think the
API we are looking at can be reasonably guaranteed for the foreseeable
future.

There are a bunch more things this framework supports including:

1.  multi-schema
2.  function name prefixes
3.  Overriding named arguments
4.  Running aggregates over return values from the functions.
5.  Registered types which grab columns of specific types and convert to
Perl objects of named types.
6.  Everything our current DBObject framework supports
7.  Classes, if needed (for integration purposes) can override the default
database connection.

All with a lot less boilerplate and a lot less cruft.  The syntax is mostly
compatible with what we have now, so I don't expect to spend more than a
day or two moving code over after we branch.

I am actually extremely happy with my forays into it currently.  It isn't a
major paradigm shift, but it smooths out a lot of rough corners.

-- 
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor
lock-in.
http://www.efficito.com/learn_more.shtml
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel


[Ledger-smb-devel] 1.3.38-rc1 on Monday?

2014-02-15 Thread Chris Travers
Hi;

Any objection to me releasing 1.3.38-rc1 on Monday my time?  The changelog
is currently fairly long, and this would give some time for review and
adding anythng that may have been missed.  I would expect that all
currently open 1.3 bugs would be fixed for 1.3.39.

The complete, current changelog is:

Changelog for 1.3.38
* Fixed AR/AP transactions resetting currency/exchange rate (Chris T)
* Reports all default to detail instead of summary (Erik H)
* Fixed adding vouchers not checking for locked/approved batches (Chris T
1025)
* Fixed can't delete pricematrix entries from customer screen (Chris T, 893)
* Fixed language change on order to invoice conversion (Chris T, 896)
* Fixed ar/ap tax check inconsistency (Chris T, 919)
* Fixed inputs ignored for email addresses sending statements (Chris T, 920)
* Fixed negative overpayments showing as positive (Chris T, 926)
* Fixed permission denied errors after upgrading copied db (Chris T, 956)
* Fixed access denied when deleting unused tax account (Chris T, 967)
* Fixed GL Report fails before entering transactions (Chris T, 977)
* Fixed start and end dates not shown on contact screen (Chris T, 979)
* Fixed employee showing up several times on search list (Chris T, 980)
* Fixed contact description not preserved on edit (Chris T, 981)
* Fixed useless buttons on credit div when no account active (Chris T, 1001)
* Backported requires() and requires_series() APIs from 1.4 (Chris T)
* Updated INSTALL to reflect better instructions for Apache 2.4 (Chris T)
* Fixed printed invoice not matching posted when 0 manual tax (Nick P, 1051)
* Updated Hungarian translation (P. Isvan)

Chris T is Chris Travers
Erik H is Erik Huelsmann
Nick P is Nick Prater
P. Isvan is Pongracz Istvan

Any commiters who note anything is missing please let me know.

-- 
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor
lock-in.
http://www.efficito.com/learn_more.shtml
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel


Re: [Ledger-smb-devel] 1.3.38-rc1 on Monday?

2014-02-15 Thread John Locke

What is the rationale for:

* Reports all default to detail instead of summary (Erik H)

... I noticed this change on our production instance, and I'm actually 
finding it a bit annoying, most of the time I would prefer a summary by 
default, at least on the open invoice reports, which we run 10 times as 
much as all the rest of them...


Cheers,
John Locke
http://www.freelock.com

On 02/15/2014 05:44 AM, Erik Huelsmann wrote:


Hi Chris,

No testing from my side yet, but looking at the list, I'd say this 
makes a nice release.


Erik

sent from my phone

On Feb 15, 2014 2:17 PM, Chris Travers chris.trav...@gmail.com 
mailto:chris.trav...@gmail.com wrote:


Hi;

Any objection to me releasing 1.3.38-rc1 on Monday my time?  The
changelog is currently fairly long, and this would give some time
for review and adding anythng that may have been missed.  I would
expect that all currently open 1.3 bugs would be fixed for 1.3.39.

The complete, current changelog is:

Changelog for 1.3.38
* Fixed AR/AP transactions resetting currency/exchange rate (Chris T)
* Reports all default to detail instead of summary (Erik H)
* Fixed adding vouchers not checking for locked/approved batches
(Chris T 1025)
* Fixed can't delete pricematrix entries from customer screen
(Chris T, 893)
* Fixed language change on order to invoice conversion (Chris T, 896)
* Fixed ar/ap tax check inconsistency (Chris T, 919)
* Fixed inputs ignored for email addresses sending statements
(Chris T, 920)
* Fixed negative overpayments showing as positive (Chris T, 926)
* Fixed permission denied errors after upgrading copied db (Chris
T, 956)
* Fixed access denied when deleting unused tax account (Chris T,
967)
* Fixed GL Report fails before entering transactions (Chris T, 977)
* Fixed start and end dates not shown on contact screen (Chris T, 979)
* Fixed employee showing up several times on search list (Chris T,
980)
* Fixed contact description not preserved on edit (Chris T, 981)
* Fixed useless buttons on credit div when no account active
(Chris T, 1001)
* Backported requires() and requires_series() APIs from 1.4 (Chris T)
* Updated INSTALL to reflect better instructions for Apache 2.4
(Chris T)
* Fixed printed invoice not matching posted when 0 manual tax
(Nick P, 1051)
* Updated Hungarian translation (P. Isvan)

Chris T is Chris Travers
Erik H is Erik Huelsmann
Nick P is Nick Prater
P. Isvan is Pongracz Istvan

Any commiters who note anything is missing please let me know.

-- 
Best Wishes,

Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No
vendor lock-in.
http://www.efficito.com/learn_more.shtml


--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
mailto:Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel

!DSPAM:52ff6f6d180851001410076!


--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk

!DSPAM:52ff6f6d180851001410076!


___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel


!DSPAM:52ff6f6d180851001410076!


--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel


Re: [Ledger-smb-devel] 1.3.38-rc1 on Monday?

2014-02-15 Thread Erik Huelsmann
Hi John,


On Sat, Feb 15, 2014 at 8:03 PM, John Locke m...@freelock.com wrote:

  What is the rationale for:


 * Reports all default to detail instead of summary (Erik H)

 ... I noticed this change on our production instance, and I'm actually
 finding it a bit annoying, most of the time I would prefer a summary by
 default, at least on the open invoice reports, which we run 10 times as
 much as all the rest of them...


The reason I made this change is really *because* of the summary open
invoice report. For a number of reasons:

1. There is no way to click through to the details report on the summary,
which confuses new users (they can't find their invoices)
2. The numbers on the open invoice summary are off: the amounts of all
invoices (even the closed ones) are included.
3. The change didn't seem too invasive from where I stand: my bookkeeper
and I only select the summary by accident (ie we only use details).

However, if this change breaks workflow for a large number of people, I'm
not against adding a drill down into the details in some column. However,
than still leaves the issue of the numbers of the summary being off (which
has thrown me off more than once).

That's the rationale. Now, with the above on the table, how do you want to
proceed? Do you want it removed from the release? Do you see other options
to address the issues above?

Thanks for bringing up the discussion before the release! :-)

-- 
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel


Re: [Ledger-smb-devel] 1.3.38-rc1 on Monday?

2014-02-15 Thread John Locke

Hi, Eric,

Oh, interesting. I think you and I are after exactly the same thing, but 
we're starting with a different report.


I use AR - Reports - Transactions (summary).

I'm guessing you use AR - Reports - Outstanding (detail).

A summary report on the first is almost exactly the same as a details 
report on the second. Almost, but not quite...



So yes, I see AR - Reports - Outstanding - summary as not something I 
need all the time -- and if it's misleading, that should get fixed.


AR - Reports - Transactions - detail has too much detail -- it 
expands all of the line items on invoices, so it's now much longer.



I'm seeing one difference between the two: Transactions is showing 
transactions that are out of balance by a fraction of a cent (the old 
invoices with calculated sales tax) while Outstanding omits them.


Otherwise we often are using Transactions to get a customer invoice 
history, by selecting the closed checkbox. For that reason alone, I 
would like to preserve the summary default there, though I can have 
people switch to the Outstanding report for the more typical use...



I wonder if it might make sense to actually split these into 3 reports? 
Seems like it would be confusing to have two reports lead to pretty much 
the same thing -- both with summary and detail options that do 
different things. What we have here are four different reports with two 
that are the same. How about splitting into something like:


- Invoices/Transactions (with options for open and closed, the report 
both you and I use)
- Customer outstanding totals (outstanding summary, hopefully fixed to 
only include open transactions)

- Items (Transaction detail report)

Not sure the second one is necessary, with the aging report also 
available...


Cheers,
John Locke
http://www.freelock.com



On 02/15/2014 12:56 PM, Erik Huelsmann wrote:

Hi John,


On Sat, Feb 15, 2014 at 8:03 PM, John Locke m...@freelock.com 
mailto:m...@freelock.com wrote:


What is the rationale for:


* Reports all default to detail instead of summary (Erik H)

... I noticed this change on our production instance, and I'm
actually finding it a bit annoying, most of the time I would
prefer a summary by default, at least on the open invoice reports,
which we run 10 times as much as all the rest of them...


The reason I made this change is really *because* of the summary open 
invoice report. For a number of reasons:


1. There is no way to click through to the details report on the 
summary, which confuses new users (they can't find their invoices)
2. The numbers on the open invoice summary are off: the amounts of all 
invoices (even the closed ones) are included.
3. The change didn't seem too invasive from where I stand: my 
bookkeeper and I only select the summary by accident (ie we only use 
details).


However, if this change breaks workflow for a large number of people, 
I'm not against adding a drill down into the details in some column. 
However, than still leaves the issue of the numbers of the summary 
being off (which has thrown me off more than once).


That's the rationale. Now, with the above on the table, how do you 
want to proceed? Do you want it removed from the release? Do you see 
other options to address the issues above?


Thanks for bringing up the discussion before the release! :-)

--
Bye,

Erik.

http://efficito.com http://efficito.com/ -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
!DSPAM:52ffd4a318811706712176!


--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk

!DSPAM:52ffd4a318811706712176!


___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel


!DSPAM:52ffd4a318811706712176!


--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk___
Ledger-smb-devel mailing list
Ledger-smb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel