From: Izzy B. <iz...@ec...> - 2001-04-17 07:25:18
|
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. |