[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SF.net SVN: ledger-smb:[3955] trunk/LedgerSMB
- Subject: SF.net SVN: ledger-smb:[3955] trunk/LedgerSMB
- From: ..hidden..
- Date: Fri, 04 Nov 2011 07:42:32 +0000
Revision: 3955
http://ledger-smb.svn.sourceforge.net/ledger-smb/?rev=3955&view=rev
Author: einhverfr
Date: 2011-11-04 07:42:31 +0000 (Fri, 04 Nov 2011)
Log Message:
-----------
Fixing POD errors
Modified Paths:
--------------
trunk/LedgerSMB/PGDate.pm
trunk/LedgerSMB/SODA.pm
trunk/LedgerSMB/Scripts/account.pm
trunk/LedgerSMB/Scripts/payment.pm
trunk/LedgerSMB/Scripts/setup.pm
Modified: trunk/LedgerSMB/PGDate.pm
===================================================================
--- trunk/LedgerSMB/PGDate.pm 2011-11-04 06:40:09 UTC (rev 3954)
+++ trunk/LedgerSMB/PGDate.pm 2011-11-04 07:42:31 UTC (rev 3955)
@@ -23,6 +23,8 @@
=head1 PROPERTIES
+=over
+
=item date
A DateTime object for internal storage and processing.
@@ -238,6 +240,8 @@
1;
+=back
+
=head1 Copyright (C) 2011, The LedgerSMB core team.
This file is licensed under the Gnu General Public License version 2, or at your
Modified: trunk/LedgerSMB/SODA.pm
===================================================================
--- trunk/LedgerSMB/SODA.pm 2011-11-04 06:40:09 UTC (rev 3954)
+++ trunk/LedgerSMB/SODA.pm 2011-11-04 07:42:31 UTC (rev 3955)
@@ -65,6 +65,8 @@
=head1 CONSTRUCTOR SYNTAX
+=over
+
=item Full syntax
LedgerSMB::SODA->new({ db => $string, username => $string, cred => $string });
@@ -83,6 +85,8 @@
Out of the box, LedgerSMB only supports HTTP basic credentials. Kerberos could
be supported with minimal effort.
+=back
+
=cut
around BUILDARGS => sub {
@@ -299,9 +303,13 @@
List of hashrefs for order by clause. Each hashref contains:
=over
+
=item column (required)
+
=item order (optional enum(asc, desc))
+
=item null_order (optional enum(first, last))
+
=back
Expressions for ordering are not supported due to SQL injection concerns, but
@@ -368,7 +376,6 @@
);
-=cut
# Private method implements window clauses per above specs above
# All identifiers are escaped, and all key words whitelisted.
@@ -403,20 +410,26 @@
}
=back
+
=item aggs
An array of hashrefs, each of which contains four elements:
=over
+
=item agg $string
+
Name of aggregate
=item alias $string
+
Column name to assign aggregate
=item window $string
+
Name of window
=item cols $arrayref
+
array ref of column names for the aggregate.
=back
@@ -633,6 +646,7 @@
die "LedgerSMB::SODA $sqlstate";
};
+=back
=head1 ENVIRONMENT VARIABLES
Modified: trunk/LedgerSMB/Scripts/account.pm
===================================================================
--- trunk/LedgerSMB/Scripts/account.pm 2011-11-04 06:40:09 UTC (rev 3954)
+++ trunk/LedgerSMB/Scripts/account.pm 2011-11-04 07:42:31 UTC (rev 3955)
@@ -41,7 +41,7 @@
_display_account_screen($request);
}
-=edit
+=item edit
Retrieves account information and then displays the screen.
Modified: trunk/LedgerSMB/Scripts/payment.pm
===================================================================
--- trunk/LedgerSMB/Scripts/payment.pm 2011-11-04 06:40:09 UTC (rev 3954)
+++ trunk/LedgerSMB/Scripts/payment.pm 2011-11-04 07:42:31 UTC (rev 3955)
@@ -1,5 +1,3 @@
-=pod
-
=head1 NAME
LedgerSMB::Scripts::payment - LedgerSMB class defining the Controller functions for payment handling.
@@ -68,15 +66,13 @@
# CT: Plans are to completely rewrite all payment logic for 1.4 anyway.
-=pod
+=over
=item payment
This method is used to set the filter screen and prints it, using the
TT2 system.
-=back
-
=cut
sub payments {
@@ -106,8 +102,6 @@
=item batch_date
-=back
-
=cut
sub get_search_criteria {
@@ -651,8 +645,6 @@
This method is used to set the filter screen and prints it, using the
TT2 system.
-=back
-
=cut
sub payment {
@@ -748,8 +740,6 @@
}
-=pod
-
=item payment1_5
This method is called between payment and payment2, it will search the database
@@ -757,8 +747,6 @@
run unnoticed by the user, if more than one is found it will ask the user to pick
one to handle the payment against
-=back
-
=cut
sub payment1_5 {
@@ -821,15 +809,11 @@
}
-=pod
-
=item payment2
This method is used for the payment module, it is a consecuence of the payment sub,
and its used for all the mechanics of an invoices payment module.
-=back
-
=cut
sub payment2 {
@@ -952,12 +936,14 @@
# We need to check for unhandled overpayment, see the post function for details
# First we will see if the discount should apply?
-=i dont think this is working
- my $temporary_discount = 0;
- if (($request->{"optional_discount_$array_options[$ref]->{invoice_id}"})&&($due_fx <= $request->{"topay_fx_$array_options[$ref]->{invoice_id}"} + $request->round_amount($array_options[$ref]->{discount}/"$exchangerate"))) {
- $temporary_discount = $request->round_amount("$array_options[$ref]->{discount}"/$array_options[$ref]->{exchangerate});
- }
-=cut
+
+
+#I dont think this is working
+# my $temporary_discount = 0;
+# if (($request->{"optional_discount_$array_options[$ref]->{invoice_id}"})&&($due_fx <= $request->{"topay_fx_$array_options[$ref]->{invoice_id}"} + $request->round_amount($array_options[$ref]->{discount}/"$exchangerate"))) {
+# $temporary_discount = $request->round_amount("$array_options[$ref]->{discount}"/$array_options[$ref]->{exchangerate});
+# }
+
# We need to compute the unhandled_overpayment, notice that all the values inside the if already have
# the exchangerate applied
@@ -1143,15 +1129,11 @@
}; # PRINT ERRORS ON THE UI
}
-=pod
-
=item post_payment
This method is used for the payment module (not the bulk payment),
and its used for all the mechanics of storing a payment.
-=back
-
=cut
sub post_payment {
@@ -1292,15 +1274,11 @@
}
}
-=pod
-
=item print_payment
This sub will print the payment on the selected media, it needs to
receive the $Payment object with all this information.
-=back
-
=cut
sub print_payment {
@@ -1345,15 +1323,11 @@
otherwise { $Payment->error("$@"); }; # PRINT ERRORS ON THE UI
}
-=pod
-
=item post_and_print_payment
This is simply a shortcut between post_payment and print_payment methods, please refer
to these functions
-=back
-
=cut
sub post_and_print_payment {
@@ -1365,15 +1339,11 @@
&print_payment($Payment);
}
-=pod
-
=item use_overpayment
This item will do the trick to use the overpayment information stored inside the payments,
it should be powerful enough to link overpayment from one customer to other customers.
-=back
-
=cut
sub use_overpayment {
@@ -1422,14 +1392,10 @@
}
-=pod
-
=item use_overpayment2
This sub runs to allow the user to specify the invoices in which an overpayment should be used
-=back
-
=cut
@@ -1715,8 +1681,6 @@
}
-=pod
-
=item post_overpayment
This method reorganize the selected invoices by customer/vendor and adapt them to make them fit with the post_payment sql method, calling it once by customer/vendor id
@@ -1958,3 +1922,5 @@
eval { do "scripts/custom/payment.pl"};
1;
+
+=back
Modified: trunk/LedgerSMB/Scripts/setup.pm
===================================================================
--- trunk/LedgerSMB/Scripts/setup.pm 2011-11-04 06:40:09 UTC (rev 3954)
+++ trunk/LedgerSMB/Scripts/setup.pm 2011-11-04 07:42:31 UTC (rev 3955)
@@ -34,6 +34,8 @@
$template->render($request);
}
+=over
+
=item login
Processes the login and examines the database to determine appropriate steps to
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.