Alex, Can I ask if you are going to continue developing aMember using the Smarty template system. I am currently delving into PHP more and more and am interested in learning Smarty. However this may be dependent on the template system aMember uses, and if it changes etc. I seem to remember about a year or so ago you said you were going to ditch Smarty for something else. Can you let me know, cheers. Also, may I ask where you draw the line betweeen releasing code which is encrypted as to unencrypted...What I mean by this is the amount of code in aMember which is encrypted (10%, 20% etc.). Users are always going to want access to as much code as they can get their hands on for customisation etc. but you as a developer want to protect your intellectual property (quite rightly). I was just wondering which areas you decided needed to be protected and which areas were ok for users to customise. Any other related comments on this topic would be appreciated by others who have used smarty/aMember extensively.
Only 2 files are encrypted in the aMember package. One file is the database class file (mysql.inc.php), which if you have legitimate reason for using the unencrypted source, the team will probably be happy providing you with it. One file is a core functions file (rconfig.inc.php), which the team is very protective about. This only contains functions for licensing, reading configuration settings from the database and error handling. That's pretty much it. I love Smarty, but a pure-php templating system would give more flexibility for things like AJAX. Here's why Smarty's so great: