Securing your code

The original post was about hiding source code that they were delivering to the customer - and my point is that with PHP it’s practically not feasible.

And to the original poster: How do you hide that source code from your customer and still comply with the GPL?

Thnx for your suggestions. once i have succeeded or failed wichever comes first, i will report back

about the GPL. Well i’m not trying to hide any of the modx code so that part doesn’t conflict with the GPL.
I only want to hide my already existing code. However strictly it will be an addition to the software (modx) issued under the GPL, so in the strict way it is indeed a conflict.
So i guess i’m hoping for a LGPL approach

But seriously will it be a problem then? I mean the code i wrote can not be used for the general purpose as the use requires a protected offline system.

Jason had posted in a different thread about the GPL issue but the short version is that if you’re only using the MODx API and not touching the existing code, then your own code does not need to be GPL’ed. Jason can clarify if I am misstating the issue.

Edit: Ryan posted a summary here: http://modxcms.com/forums/index.php/topic,10183.msg69676.html#msg69676

If you write snippets as part of developing a site for a client, you don’t have to distribute them on GPL if they only call the MODx API and don’t change any MODx code. You can distribute them using a closed-source commercial license.