Perl on CPAN
Requires: Perl 5.004, Carp, Exporter, GD (optional)
http://search.cpan.org/~wrw/Barcode-Code128-2.21/lib/Barcode/Code128.pm…
Example:
use Barcode::Code128 'FNC1';
$code = new Barcode::Code128;
$code->text(FNC1.'00000123455555555558');
The LedgerSMB team is pleased to announce the release of LedgerSMB 1.3.25. With this release we mostly have focused on cosmetic changes for the software, thus reducing the sorts of user interface issues that are likely to cause minor headaches for users of the software.
There are, however, three significant issues that have been corrected in this release which make an upgrade recommended for everyone:
1: In previous versions, term of payment on sales orders and purchase orders were not properly respected.
First of all, you need to backup all your company databases followed by an upgrade of your PostgreSQL installation. There are plenty of places on the web to explain how to do that. The high-level process is to install the two versions in parallel and run the pg_upgradecluster command.
When the technical upgrade has succeeded, however, you're not ready to see the performance improvements promised by the 8.4+ versions of PostgreSQL with respect to the menu-generation. This is because the database doesn't automatically use the new 8.4+ code definitions.
The LedgerSMB development team is proud to release 1.3.24. This release contains a fairly large number of polishing bug-fixes, but also important Plack-related fixes for folks wanting to use LedgerSMB in FCGI and PSGI environments. These fixes ensure that LedgerSMB can be run caching some of the dependencies and thus will be far more responsive than when run as a simple CGI application.
In general: neither. The advice is to have the full source tree in /opt/ledgersmb/<version>.
The default configuration limits access to the /ledgersmb/login.pl page to connections from localhost (127.0.0.1) only for maximum security.
If you want to allow connections from other locations, it's highly advisable to use encrypted (VPN) connections to access your ledger in order to maintain good security.
# diff -u "original file" "new edited file" > “diff file”
Submit your patches ( “diff file” through the Sourceforge project tracker. If you are going to do somewhat largish changes, it's best to discuss how to do them on the developers list. That increases chances for acceptance which is in general the best solution for you and the lsmb community.
LedgerSMB 1.3.23 has been released. This release includes a number of bugfixes, some of which affect the ability to deploy LedgerSMB in new environments. Most of these bugfixes are relatively minor but they do impact upgrades from 1.2.x for some users. Additionally most of the changes are ones which allow us to present a more polished product to the user.
This also corrects some i18n issues and a few other issues. The complete changelog is below.
The simple one:
Sales order: Customer wants to buy something.
Sales invoice: Customer owes for goods and services delivered.
Business-flow-wise, typically you take an order before everything is done necessary for the transaction to hit the books, and convert it to an invoice when everything that has been done for the income to be realized has happened. This typically means:
1) Goods or services are delivered
2) Any approval/error checking the business requires has happened
NP Broadcast Limited is a UK-registered Limited Company with a yearly turnover of approximately GBP 150,000, VAT registered with 2 LedgerSMB users. We are mainly a services company providing studio and outside broadcast engineering support to broadcasters.