sql-ledger-users

[SQL-Ledger-users] Partial payments

[Izzy B. <iz...@ec...>]

I fired up SQL-Ledger about a month ago to test it's viability as an 
accounting package for my customers.  It is obviously still in it's infancy 
but shows great potential.  So much so that I would like to take an active 
role in it's development.  Sadly, I don't know Perl so haven't been able to 
do much more then pass a number of bug reports onto Dieter.  I plan to 
change this in the not so distant future so I can participate in future 
development.

I've noticed there hasn't been any activity in this list for almost three 
weeks and nothing is happening at the sourceforge site.  I'm hoping this is 
because the users are content with the current version and developers are 
busy with adding new features for the next version.  Unfortunately I don't 
see any evidence to this effect. :(

I haven't seen any mention of a separate developers list, but there doesn't 
appear to be much in the way of developer discussions on this list and only 
Dieter is listed as a developer at sourceforge.  It seems to me that the 
space at sourceforge could be put to much better use.

I've done some trolling through the list archives and have come across 
people who have made contributions, offered suggestions or volunteered to 
take on development of new features.  Unfortunately there doesn't seem to 
be any acknowledgement of these efforts or confirmation that it's ok for 
development to begin.  I can only assume this is all happening behind 
closed doors.  IMHO, it makes it hard for new developers to take on 
projects if there is no formal acknowledgment of existing projects in 
progress.

I've compiled the following list of noteworthy things I've found in the 
list since the last release.

Dieter has alluded to changes in the works that will make sql-ledger adapt 
to different tax systems better.  Are there any other changes in the works 
that we should know about?  I see the next release is almost out.  Version 
1.4 no less.  How does one become a beta tester?

Rod Anderson offered to "launch" himself into creating customer 
statements.  Something I'd very much like to see.  Hows it going?  Will 
this make it into the next release?

Paolo Bizzarri, and Martin Lillepuu discussed adding capabilities for multi 
part payments.  Something I'm sure a great deal of people could 
use.  Including myself.  Hows it coming?  I hope you've been working with 
Rod as I'm sure your changes will effect him and vice versa.  Is this to be 
in the next release?

Martin Lillepuu also posted links to diagrams he created of the sql-ledger 
database and code.  I haven't managed to find a nice way to print them 
though.  Could you create a print friendly version?  I haven't played with 
dia yet but I'm assuming it must be possible.  It'd be nice to see links to 
this stuff from the main SQL-Ledger site.

Adrian Blake submitted code changes for ca.cgi to add a sum to the bottom 
of the debit and credit columns of the account list report. I'm assuming 
this is going to make it into the next version?

Neal Irwin purposed creating a mechanism to allow "pending" invoices to be 
saved but not posted.  Having suffered from the mistake of printing, but 
not posting an invoice, this makes a lot of sense to me.  An invoice should 
be saved as pending as soon as it is started and every subsequent addition 
or change should be saved to this pending invoice.  This would prevent 
mistakes like forgetting to post a finished invoice as well as prevent the 
problem of an invoice being lost because of a crash or power outage.  Given 
that I didn't see anyone volunteer to take this project on, I'm assuming it 
isn't going to be implemented in this release.  Too bad. :(

Sylvain Duchesne asked about module support for sql-ledger.  Specifically a 
module to allow automatic billing.   I too could use this feature.  Is it 
going to be in the next release?  It seems to me that a more modular 
approach overall would be beneficial.   SQL-Ledger should focus on handling 
the accounting side of things and allowed the user to plug in their own 
contact database, inventory control system, payroll model, etc.  Of course 
it makes sense for SQL-Ledger to have basic versions of each, but designed 
in such a way that someone could plug in their own, industry specific 
versions.  Trying to create a solution that is perfect for everyone just 
creates bloated apps! :(  The module approch gives the best of both worlds.

Ted Stockwell was looking for a home for his 80% complete J2EE version of 
sql-ledger. What happened with it?

I'm very impressed with SQL-Ledger so far.  There isn't much more that has 
to be done before it becomes a viable option for some of my customers.  The 
multi part payments and customer statements features are among the most 
critical.  The problem of loosing invoices that aren't posted is another 
issue that I hope can be addressed soon.  There are a number of other 
features that I would like to see and plan to take an active part in 
creating.  I'm currently trying to learn how the internal workings of SQL 
operate and of course learn Perl.

...Izzy

Re: [SQL-Ledger-users] Partial payments

[Sylvain D. <sdu...@we...>]

I can't comment for the others but as for myself I do intend to get some 
sort of automatic billing system together whenever I can spare the time.

sd

> I fired up SQL-Ledger about a month ago to test it's viability as an 
> accounting package for my customers.  It is obviously still in it's
> infancy  but shows great potential.  So much so that I would like to
> take an active  role in it's development.  Sadly, I don't know Perl so
> haven't been able to  do much more then pass a number of bug reports
> onto Dieter.  I plan to  change this in the not so distant future so I
> can participate in future  development.
> 
> I've noticed there hasn't been any activity in this list for almost
> three  weeks and nothing is happening at the sourceforge site.  I'm
> hoping this is  because the users are content with the current version
> and developers are  busy with adding new features for the next version.
>  Unfortunately I don't  see any evidence to this effect. :(
> 
> I haven't seen any mention of a separate developers list, but there
> doesn't  appear to be much in the way of developer discussions on this
> list and only  Dieter is listed as a developer at sourceforge.  It
> seems to me that the  space at sourceforge could be put to much better
> use.
> 
> I've done some trolling through the list archives and have come across 
> people who have made contributions, offered suggestions or volunteered
> to  take on development of new features.  Unfortunately there doesn't
> seem to  be any acknowledgement of these efforts or confirmation that
> it's ok for  development to begin.  I can only assume this is all
> happening behind  closed doors.  IMHO, it makes it hard for new
> developers to take on  projects if there is no formal acknowledgment of
> existing projects in  progress.
> 
> I've compiled the following list of noteworthy things I've found in the
>  list since the last release.
> 
> Dieter has alluded to changes in the works that will make sql-ledger
> adapt  to different tax systems better.  Are there any other changes in
> the works  that we should know about?  I see the next release is almost
> out.  Version  1.4 no less.  How does one become a beta tester?
> 
> Rod Anderson offered to "launch" himself into creating customer 
>statements.  Something I'd very much like to see.  Hows it going?  Will 
>this make it into the next release?
> 
> Paolo Bizzarri, and Martin Lillepuu discussed adding capabilities for
> multi  part payments.  Something I'm sure a great deal of people could 
> use.  Including myself.  Hows it coming?  I hope you've been working
> with  Rod as I'm sure your changes will effect him and vice versa.  Is
> this to be  in the next release?
> 
> Martin Lillepuu also posted links to diagrams he created of the
> sql-ledger  database and code.  I haven't managed to find a nice way to
> print them  though.  Could you create a print friendly version?  I
> haven't played with  dia yet but I'm assuming it must be possible. 
> It'd be nice to see links to  this stuff from the main SQL-Ledger site.
> 
> Adrian Blake submitted code changes for ca.cgi to add a sum to the
> bottom  of the debit and credit columns of the account list report. I'm
> assuming  this is going to make it into the next version?
> 
> Neal Irwin purposed creating a mechanism to allow "pending" invoices to
> be  saved but not posted.  Having suffered from the mistake of
> printing, but  not posting an invoice, this makes a lot of sense to me.
>  An invoice should  be saved as pending as soon as it is started and
> every subsequent addition  or change should be saved to this pending
> invoice.  This would prevent  mistakes like forgetting to post a
> finished invoice as well as prevent the  problem of an invoice being
> lost because of a crash or power outage.  Given  that I didn't see
> anyone volunteer to take this project on, I'm assuming it  isn't going
> to be implemented in this release.  Too bad. :(
> 
> Sylvain Duchesne asked about module support for sql-ledger. 
> Specifically a  module to allow automatic billing.   I too could use
> this feature.  Is it  going to be in the next release?  It seems to me
> that a more modular  approach overall would be beneficial.   SQL-Ledger
> should focus on handling  the accounting side of things and allowed the
> user to plug in their own  contact database, inventory control system,
> payroll model, etc.  Of course  it makes sense for SQL-Ledger to have
> basic versions of each, but designed  in such a way that someone could
> plug in their own, industry specific  versions.  Trying to create a
> solution that is perfect for everyone just  creates bloated apps! :( 
> The module approch gives the best of both worlds.
> 
> Ted Stockwell was looking for a home for his 80% complete J2EE version
> of  sql-ledger. What happened with it?
> 
> I'm very impressed with SQL-Ledger so far.  There isn't much more that
> has  to be done before it becomes a viable option for some of my
> customers.  The  multi part payments and customer statements features
> are among the most  critical.  The problem of loosing invoices that
> aren't posted is another  issue that I hope can be addressed soon. 
> There are a number of other  features that I would like to see and plan
> to take an active part in  creating.  I'm currently trying to learn how
> the internal workings of SQL  operate and of course learn Perl.
> 
> ...Izzy

Re: [SQL-Ledger-users] Partial payments

[Roderick A. A. <raa...@ti...>]

On Sun, 15 Apr 2001, Izzy Blacklock wrote:


> Rod Anderson offered to "launch" himself into creating customer 
> statements.  Something I'd very much like to see.  Hows it going?  Will 
> this make it into the next release?

Once I find a couple of free hours I'll get it done.  I really needed it
the end of the last couple of months because of a billing agreement I
have with a couple of customers and kicked myself for not making the
time to do it.  Dieter provided a very good description of how to
accomplish it so it will be forthcoming... soon... yes... for sure...


Rod
-- 

Re: [SQL-Ledger-users] Payroll

[Paul E. <pe...@ca...>]

I needed a payroll script right away, so I did a simple one in python. It 
handles everything I found till my eyes crossed wading through the 
entertaining 95 pages of the federal publication. 

It's at http://cdnpayroll.sourceforge.net FWIW.

-- 

Regards, Paul Evans

Re: [SQL-Ledger-users] Payroll

[Izzy B. <iz...@ec...>]

At 08:59 AM 16/04/01, you wrote:
>I needed a payroll script right away, so I did a simple one in python. It
>handles everything I found till my eyes crossed wading through the
>entertaining 95 pages of the federal publication.
>
>It's at http://cdnpayroll.sourceforge.net FWIW.

I noticed this project the other day.  I haven't had a chance to take a 
look at it but I was going to suggest some collaboration between this 
project and yours.  Seems like a natural fit! :)

I also noticed an accounting project for the Palm on sourceforge as 
well.  I took a brief look at it also.  I'd love to see someone build an 
interface for it also.  It'd be nice to be able to carry your accounting 
data around with you and make small entries on the run.  Just a 
thought.  Here's the link.

https://sourceforge.net/projects/palmcoins/

I'd offer to take on this project myself, but I have to admit it will 
extend my learning curve.  I have to learn Perl still and I know nothing 
about palm programming.  If no one else is interested though, I'd be 
willing to look into what's involved.

...Izzy

Re: [SQL-Ledger-users] Partial payments

[Dieter S. <dsi...@sq...>]

I use sourceforge for the webpages and mailing lists only. This is why I
am the only one listed as developer. The source code listed on sourceforge
is also behind times and the latest stable release is only available from
the sql-ledger.org source code page.

The changes to the tax system are almost done. I think I covered just
about all the tax situations with the new dynamic setup. Other changes
include a new frontend processing system. Display and backend code was
split into perl scripts and perl modules. Lynx and all major graphical
browsers can be used, no more cookies. It's also possible to write a new
frontend for the console, a Tk, phyton or Javascript version. A trial
balance was added, and so were sums on the reports, you can also choose
which fields to display. Automatic dates for invoices, correct date
display and sorting, encrypted passwords, a new config setup, etc.

When will 1.4 come out? I don't know yet. The inventory received module is
not quite finished yet.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========


> On Sun, 15 Apr 2001, Izzy Blacklock wrote:
> 
> I haven't seen any mention of a separate developers list, but there
> doesn't  appear to be much in the way of developer discussions on this
> list and only  Dieter is listed as a developer at sourceforge.  It
> seems to me that the  space at sourceforge could be put to much better
> use.
>
> I've done some trolling through the list archives and have come across 
> people who have made contributions, offered suggestions or volunteered
> to  take on development of new features.  Unfortunately there doesn't
> seem to  be any acknowledgement of these efforts or confirmation that
> it's ok for  development to begin.  I can only assume this is all
> happening behind  closed doors.  IMHO, it makes it hard for new
> developers to take on  projects if there is no formal acknowledgment of
> existing projects in  progress.
> 
> I've compiled the following list of noteworthy things I've found in the
>  list since the last release.
> 
> Dieter has alluded to changes in the works that will make sql-ledger
> adapt  to different tax systems better.  Are there any other changes in
> the works  that we should know about?  I see the next release is almost
> out.  Version  1.4 no less.  How does one become a beta tester?
> 
> Rod Anderson offered to "launch" himself into creating customer 
>statements.  Something I'd very much like to see.  Hows it going?  Will 
>this make it into the next release?
> 
> Paolo Bizzarri, and Martin Lillepuu discussed adding capabilities for
> multi  part payments.  Something I'm sure a great deal of people could 
> use.  Including myself.  Hows it coming?  I hope you've been working
> with  Rod as I'm sure your changes will effect him and vice versa.  Is
> this to be  in the next release?
> 
> Martin Lillepuu also posted links to diagrams he created of the
> sql-ledger  database and code.  I haven't managed to find a nice way to
> print them  though.  Could you create a print friendly version?  I
> haven't played with  dia yet but I'm assuming it must be possible. 
> It'd be nice to see links to  this stuff from the main SQL-Ledger site.
> 
> Adrian Blake submitted code changes for ca.cgi to add a sum to the
> bottom  of the debit and credit columns of the account list report. I'm
> assuming  this is going to make it into the next version?
> 
> Neal Irwin purposed creating a mechanism to allow "pending" invoices to
> be  saved but not posted.  Having suffered from the mistake of
> printing, but  not posting an invoice, this makes a lot of sense to me.
>  An invoice should  be saved as pending as soon as it is started and
> every subsequent addition  or change should be saved to this pending
> invoice.  This would prevent  mistakes like forgetting to post a
> finished invoice as well as prevent the  problem of an invoice being
> lost because of a crash or power outage.  Given  that I didn't see
> anyone volunteer to take this project on, I'm assuming it  isn't going
> to be implemented in this release.  Too bad. :(
> 
> Sylvain Duchesne asked about module support for sql-ledger. 
> Specifically a  module to allow automatic billing.   I too could use
> this feature.  Is it  going to be in the next release?  It seems to me
> that a more modular  approach overall would be beneficial.   SQL-Ledger
> should focus on handling  the accounting side of things and allowed the
> user to plug in their own  contact database, inventory control system,
> payroll model, etc.  Of course  it makes sense for SQL-Ledger to have
> basic versions of each, but designed  in such a way that someone could
> plug in their own, industry specific  versions.  Trying to create a
> solution that is perfect for everyone just  creates bloated apps! :( 
> The module approch gives the best of both worlds.
> 
> Ted Stockwell was looking for a home for his 80% complete J2EE version
> of  sql-ledger. What happened with it?
> 
> I'm very impressed with SQL-Ledger so far.  There isn't much more that
> has  to be done before it becomes a viable option for some of my
> customers.  The  multi part payments and customer statements features
> are among the most  critical.  The problem of loosing invoices that
> aren't posted is another  issue that I hope can be addressed soon. 
> There are a number of other  features that I would like to see and plan
> to take an active part in  creating.  I'm currently trying to learn how
> the internal workings of SQL  operate and of course learn Perl.
> 
> ...Izzy

Re: [SQL-Ledger-users] Partial payments

[Izzy B. <iz...@ec...>]

At 02:36 PM 16/04/01, you wrote:
>I use sourceforge for the webpages and mailing lists only. This is why I
>am the only one listed as developer. The source code listed on sourceforge
>is also behind times and the latest stable release is only available from
>the sql-ledger.org source code page.

I hope you don't feel I was criticizing you personally.  It was not my 
intention. I was just trying to figure out what was going on and try to 
stir the fire a little.  Looks like I succeeded! :)  I actually started out 
to ask how to handle partial payments; hence the subject (any 
answers?).  Like a good little hacker, I decided first to search the 
archives to see if the question had been answered.  That's when I noticed 
the list seemed to be dead.  Further digging showed very little activity 
over all and almost no signs of development.  This lead to panic which was 
quickly replaced with frustration when I noticed your recent posting to the 
SQL-Ledger News indicating 1.4 was almost ready for release.

I'm relieved to see that development is ongoing, but I think my panicked 
message proves a point.  IMHO, it'd be good for everyone to be able to see 
evidence of ongoing development.  Most users wont really care about the 
details, but would like to see what they can look forward to in the next 
release.  The details should be  hammered out in a separate developers list 
(BTW, thanks for adding me), but everyone should know of it's existence and 
be able to get at least read only access to it.  This will go a long way to 
keeping users excited about the project and help to attract developers.

>The changes to the tax system are almost done. I think I covered just
>about all the tax situations with the new dynamic setup. Other changes
>include a new frontend processing system. Display and backend code was
>split into perl scripts and perl modules. Lynx and all major graphical
>browsers can be used, no more cookies. It's also possible to write a new
>frontend for the console, a Tk, phyton or Javascript version. A trial
>balance was added, and so were sums on the reports, you can also choose
>which fields to display. Automatic dates for invoices, correct date
>display and sorting, encrypted passwords, a new config setup, etc.

Wow!  You've been busy! :)  How do I become a beta tester!? :)

>When will 1.4 come out? I don't know yet. The inventory received module is
>not quite finished yet.

I could deal with this! :)  Does it handle partial payments?

...Izzy

[SQL-Ledger-users] Showing currency with dots and commas

[Paolo B. <p.b...@ic...>]

Hi everyone,

for internal usage, I have made some changes to sql-ledger, in order to show 
dots and commas when showing currency. This is really useful, for seeing how 
much we have to show.

Two questions:

1) I have used the Number::Format module to produce the result. Is this 
acceptable for sql-ledger, so to include the patches in future releases ?

2) How can I modify number shown in reports ? They are put in an array, but 
then they are used to perform calculation. 

And last a plea: is it possible to see the 1.4 version as a development 
version of sql-ledger ? I would like to cooperate to the new version, as the 
things included (like more tax level, for example) are really really useful 
for me.

Regards

Paolo 

-- 
Paolo Bizzarri
Icube S.r.l.

Re: [SQL-Ledger-users] Partial payments

[Izzy B. <iz...@ec...>]

I know how you feel.  I've been so busy myself lately, I've hardly had time 
to reply to much mail. It's tough finding time to do the things you have 
to, never mind the things you want to.  :(

Take all the time you need.  My intention wasn't to hurry anyone along with 
their projects, just to get an update.  Thanks for providing it.  And 
thanks to Sylvain and Dieter too.  I look forward to seeing new code and 
hope to provide some of my own in the not too distant future.  Time 
permitting of course! ;)

...Izzy

At 08:23 AM 16/04/01, Rod Anderson wrote:
>On Sun, 15 Apr 2001, Izzy Blacklock wrote:
>
>
> > Rod Anderson offered to "launch" himself into creating customer
> > statements.  Something I'd very much like to see.  Hows it going?  Will
> > this make it into the next release?
>
>Once I find a couple of free hours I'll get it done.  I really needed it
>the end of the last couple of months because of a billing agreement I
>have with a couple of customers and kicked myself for not making the
>time to do it.  Dieter provided a very good description of how to
>accomplish it so it will be forthcoming... soon... yes... for sure...
>
>
>Rod
>--

Re: [SQL-Ledger-users] Partial payments

[Antonio G. <ag...@ib...>]

I think the critic is well addressed. We must work together if we want to=
=20
have a very nice SQL-Ledger. Really, the app seems very promised, but we =
need=20
to boost the development and for this is very important the team working.

We are still waiting for the 1.4 version.

I learned Perl, because SQL-Ledger exists! ... Well I am a newbie on Perl=
=2E=20
but I try to write Perl code for SQL-Ledger ;-)

What is new in SQL-Ledger 1.4?

We can put some devel-info in the home page to help new developers to go =
into.=20
For example when I start looking into SQL-Leger, I draw a Schema of the D=
B on=20
Pg-Access. This schema is very useful for the developer. I will send the=20
schema later.

Well, I know SQL language better than Perl ! I wrote some Queries in Pg-A=
ccess=20
that helps to maintain the data consistency:


Query name:=09BadTransac
Descriptions:=09Display transactions where the balance is out of the rang=
e
=09=09<-0.005; 0.005>. This transacctions are not correct, and must be
=09=09corrected, because some times (debits-credits) is not 0.
Code:=09=09SELECT t0."trans_id", SUM(t0."amount") FROM "acc_trans" t0 GRO=
UP BY
=09=09t0."trans_id"  HAVING ABS(sum(t0."amount"))>0.005 ORDER BY t0."tran=
s_id"
=09=09ASC;
Use:=09=09When you find some transaction with this query I try to correct=
 the rows
=09=09of the transaction to get (debits-credits=3D0).


Queryname:=09LostSons
Description:=09in early versions of SQL-Ledger, sometimes happens that in=
 the
=09=09DB was account details without header in any of the tables ar, ap, =
or  gl.
=09=09Then I wrote this Query to find this kind of "Lost Sons" or "Detail=
s
=09=09without Headers".
=09=09Displays the rows of the table acc_trans, that have not header in a=
ny of
=09=09the tables ar,ap or gl.
Code:=09=09SELECT * FROM acc_trans WHERE issell(trans_id) =3D NULL AND
=09=09isgl(trans_id) =3D NULL AND isbuy(trans_id) =3D NULL

Note:=09=09The query use some custom functions: "issell", "isinvoice" and=
 "isbuy":
=09=09Function name:=09issell
=09=09Parameters:=09int4
=09=09Returns:=09=09bool
=09=09Language:=09sql
=09=09Code:=09=09SELECT TRUE FROM ar WHERE id=3D$1

=09=09Function name:=09isgl
=09=09Parameters:=09int4
=09=09Returns:=09=09bool
=09=09Language:=09sql
=09=09Code:=09=09SELECT TRUE FROM gl WHERE id=3D$1

=09=09Function name:=09isbuy
=09=09Parameters:=09int4
=09=09Returns:=09=09bool
=09=09Language:=09sql
=09=09Code:=09=09SELECT TRUE FROM ap WHERE id=3D$1
Use:=09=09When you find any row on the table acc_trans that meets this cr=
iteria,
=09=09please delete the row. I know that we can deletes the row on a SQL =
queries,
=09=09but still intrigate me what and when appears the "Lost Sons". I thi=
nk that
=09=09the "problem of Lost Sons" does not exist anymore since version 1.2=
=2E10. But
=09=09I still search some times for "Lost Sons" and this query helps to.


Query name:=09BadBalances
Description:=09Display the account numbers and more info about when the b=
alance=20
=09=09in the table chart is not equal to the balance of the account in th=
e table
=09=09acc_trans. I called the balance based on the table acc_trans "real =
balance".
=09=09I use here again the interval <-0.005; 0.005>.
Code:=09=09SELECT accno,balance, realbalance(accno) FROM chart WHERE
=09=09ABS(balance - realbalance(accno)) > 0.005 ORDER BY accno
Note:=09=09The query use one custom functions:
=09=09Function name:=09realbalance
=09=09Parameters:=09int4
=09=09Returns:=09=09float8
=09=09Language:=09sql
=09=09Code:=09=09SELECT SUM(amount) FROM acc_trans accno=3D$1
Use:=09=09When you find any row when run this query, change the field "ba=
lance" of
=09=09table "chart" to the value of the field "realbalance" of the query.

Also, I wrote two subs to help to format the amounts into a format three=20
digit comma separated. Example: 1000.00 will be 1,000.00.

I put this code at the end of HTML.pm, because like DB subs like=20
"update_balance", I use it in almost every page. Note, that this code ins=
erts=20
a comma every three digits and for this, we cannot sum the output like a=20
"normal number". But, Sid has the last word about.



### Start of code ###

# Formats an amount into a number with two digits containing commas every
# third number.
sub to_money($amount)
{
=09my($self, $amount) =3D @_;
=09return (&commify(sprintf("%.2f", $amount)));
}

# Performs the comma step
sub commify
{
=09local $_ =3D shift;
=091 while s/^(-?\d+)(\d{3})/$1,$2/;
=09return "$_";
}

### End of code ###


Use of the code. For example: on ca.cgi of the version: 1.2.10 I wrote:

$ca->{credit} =3D $form->to_money($ca->{credit});

Please see the attached file ca.cgi

Also, I sent a new report that work with a template. I called this report=
=20
"Comprobante", because I don't know what is the correct name in English.


That's is all by now. I hope this will help us to make a better SQL-Ledge=
r=20
accounting experience.

Regards,

Ing. Antonio Gallardo
AG Software, S. A.
Managua, NICARAGUA.

[SQL-Ledger-users] What about a integration with PHPGroupware?

[Antonio G. <ag...@ib...>]

Hi everybody!

I was work with phpgroupware for more than 4 month. PHPGroupware is a ver=
y=20
nice Web Application Framework.

Please visit: http://www.phpgroupware.org/

I think that we can integrate SQL-Ledger with PHPGroupware. We will must =
to=20
rewrite the SQL-Ledger code in Perl to PHP. But, maybe the pay off will b=
e=20
great: a suit with:
=09=09addressbook
=09=09calendar
=09=09translate
=09=09inventory
=09=09filemanager
=09=09email
=09=09nntp
=09=09notes
=09=09todo lists
=09=09trouble tracking system
=09=09projects

and SQL-Ledger!

What about this?

I think again that Dieter has the last word. What are the pros and cons? =
This=20
is a good choice?

Well I put the question to all of us.

Regards,

Ing. Antonio Gallardo
AG Software, S. A.
Managua, NICARAGUA.

Re: [SQL-Ledger-users] What about a integration with PHPGroupware?

[Izzy B. <iz...@ec...>]

At 07:42 PM 16/04/01, you wrote:

I haven't really looked at it much yet, but it seems to me this would add a 
great deal of bloat to SQL-Ledger.  I for one don't need all of what you 
mentioned.  Certainly not in my accounting package!  I think it makes sense 
to migrate SQL-Ledger into a modular approach which will allow it to be 
plugged into other projects or vice versa, but it should also be capable of 
operating on it's own.

Each of my customers have very different computing needs.  One thing that 
is common is their need for accounting.  I would like SQL-Ledger to be able 
to handle their accounting needs while being flexible enough that I can 
plug it into their existing contact management database, inventory control 
system, invoice system, etc.  This would allow it to interface with 
phpgroupware and use it's address book or inventory control system.  But I 
don't think we want to make it dependent on it!

On another note, I don't belive it would require a complete conversion from 
perl to PHP.  You might have to rewrite the user interface, but the back 
end stuff should be ok left in perl I'd think.  Of course I don't know PHP 
or perl so don't take my word for it! :)

...Izzy


>Hi everybody!
>
>I was work with phpgroupware for more than 4 month. PHPGroupware is a very
>nice Web Application Framework.
>
>Please visit: http://www.phpgroupware.org/
>
>I think that we can integrate SQL-Ledger with PHPGroupware. We will must to
>rewrite the SQL-Ledger code in Perl to PHP. But, maybe the pay off will be
>great: a suit with:
>                 addressbook
>                 calendar
>                 translate
>                 inventory
>                 filemanager
>                 email
>                 nntp
>                 notes
>                 todo lists
>                 trouble tracking system
>                 projects
>
>and SQL-Ledger!
>
>What about this?
>
>I think again that Dieter has the last word. What are the pros and cons? This
>is a good choice?
>
>Well I put the question to all of us.
>
>Regards,
>
>Ing. Antonio Gallardo
>AG Software, S. A.
>Managua, NICARAGUA.