I'd just minify it. You may say that if I'm using a license there is no need to scramble (or whatever) the code Yeah, I would say that. :-P Just minify it, doing anything else is probably a bit overkill if the license would prohibit stuff anyway.Do you want an open source or proprietary license?
It sounds from your description that you'd like open source but then you want to obfuscate it....
There is nothing bulletproof you can do, since PHP is interpreted. Minifying and obfuscating are your best bets. Though (and believe me I mean absolutely no offense by this), you have to ask yourself if you really think it's worth the hassle.Be honest with yourself and answer this question: Are any of your clients honestly going to go through the time and trouble to steal your work?
If so, it will be a tiny percentage, and will the lost money be worth the hassle? Here's the thing: If they have the expertise and determination to steal your project, obfuscation won't stop them.
Excellent point! Like I've said in previous comments I will stick to minifying the code and using the license to prohibit stealings and thefts :) – JamWaffles Nov 9 '10 at 20:46.
You could consider having parts of the code on your own server. The distributed version would rely on using the scripts you're hosting. This of course has obvious drawbacks and it's not feasible for every project.
That is a very good point, but it's not practical for this application. Thanks all the same :) – JamWaffles Nov 9 '10 at 20:45.
A couple of options: PHP Obfuscator Zend Guard.
Here's a couple I know of: ioncube and php obfuscator.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.