Hi Gordon, 2014.12.26 18:44, Gordon Dickens wrote:
Sorry, but I don't remember for sure which module(s) that it was. I had noticed that you replaced Pear::DB though... BTW, I am currently sorting though the Vexim patches that have been made since 2012 and I am patching Exim4U with many of your patches and improvements. It may be a while before I'm done but I hope to have most of the patches implemented soon. Thanks!
I think porting your changes to our codebase instead might be feasible as well. If I remember correctly, you have some additional fields/functionalities which don't exist in stock Vexim, but the last time I checked, the biggest differences were your use of Bootstrap and our use of PDO, and if we don't go with the rewrite, I'd very much like to apply that Bootstrap patch to our repository anyway.
I concur that there are advantages to moving away from php to some type of framework or forms generator. There are subtle differences in Vexim and Exim4U, particularly related to the exim configuration and how/when spam and viruses are processed, that would need to be reconciled for the same development work to easily be applied to both projects. I am sure that we could work that out though.
One of the reasons why I want to rewrite Vexim is simply to learn something new (a framework in this case). Currently, I'm facing a dilemma which framework to choose. In particular: * does framework's size matter? For example, Yii2 take up about 20MB, which might appear too much for our small application. * does framework's license matter? E.g. Fat-Free Framework (F3) is rather small, but uses GPLv3. If I choose F3, I assume it would mean licensing the new version of Vexim under GPLv3 as well. I wonder if that would be a problem for anyone. Regarding your second sentence in this paragraph, I assume it refers to Exim config files, and not the Vexim admin app, right? Hm, perhaps we should move the app into its own repository... Rimas