Hi
I am sorry for being late in my reply. Lots of work!
>Integrate vtiger and frontaccounting WITHOUT changing the core code of either vtiger or frontaccounting.
I don't believe this is possible. For me, this is not a "seamless" merger but only the "basic" integration. Two different dbs, 2 different UIs (look and feel), 2 different sets of base functionalities, fi, vT role-based security is quite different from that of FA. This kind of integration is a kind of work-around. Or, you can say its a patch-work. If our objective is to challenge the ERP proprietary market, then we should look forward for the seamless integration. Good, stable software are not built in a day, my original quote :-)
There are several disadvantages related to the "basic" integration, The main being:
a. Maintain 2 different PHP code-bases. Let's talk about customization, a company wants to add a new field in its invoice and validate the value of that field. In this case, we have to modify 2 code bases.
b. Backup/Restore/Create tables in 2 dbs
c. The end-users will have to learn 2 different set of UIs and base functionalities (like roles, etc.)
d. The multi-currency concept is different in both the FA and vT.
e. vT is multi-theme, FA is not.
f. For instance, both offer the Sales Order (SO) functionality. We will have to ask the end-user to login to vT and create the SO and then login to FA to perform other operation related to SO which vT does not offer.
g. Two accounts for each user, one in FA and the other one in vT. The user has to keep track of 2 passwords.
h. It will become really difficult for a new developer to maintain the two different code bases. First he will have to learn both More importantly, he will to shift his mindset from one codebase to another while making the modifications.
>we would like to have the ability to take advantage of the awesome updates that both Front Accounting and Vtiger come out with in the future.
Both are pretty stable versions now and if something major update comes, we have to do it manually. Let's think it the other way around, if we come up with a major module, then vT and FA users will be chasing us.
>It doesn't make sense for us to try to compete against FA or vtiger with another ERP system that is a fork of both.
No. vT does not offer, fi, Accounting and FA does not offer CRM. But our version will offer both. So we are better than them :-)
>I think FA should specialize in what it does best, Accounting. and vtiger should specialize in CRM.
If we get good sponsors, our end-product is going to be a very powerful package. I think the sponsor will play a major role in the product's feature and other decisions.
>FA needs the following things: 1. Ability to add Custom Fields ...
Vtiger needs the following things: 1. Ability to add a Task ...
I can do this. I have already planned for the seamless integration. And I am successful whatever integration I have done so far.
For instance, I have made huge changes in the vT source code to make it multi-company . Just like FA, at login time, it asks you to select a company. And the data in the db of multiple companies is completely separate. And one can easily consolidate them for reporting.
If any long-term sponsor is there, I am always around. I know what and how to do from the developer's point of view. Yes, from the features point of view, we need to discuss.
Kind Regards