3 ms·
True, any obfuscation would make it impossible to judge the quality of the source. Good point. I'm surprised that ThemeForest hasn't jumped on this yet either.
by coderdude 15y ago
True, any obfuscation would make it impossible to judge the quality of the source. Good point.
I'm surprised that ThemeForest hasn't jumped on this yet either.
- moe 15y agoYou could perhaps partially obfuscate the code. But it'd probably be tricky to ensure that at least some interesting parts remain untouched. Perhaps let the template author markup those areas?
- coderdude 15y agoIf it were to be done that might be the only way to do it. The author is going to have a better idea of what they feel is the meat and potatoes than I would.
- jtheory 15y agoMeh. I'd say don't bother to obfuscate it. There's a real cost, and no obvious benefit (anyone making a real site would be stupid to steal their theme; anyone interested in stealing would just steal from a theme purchaser's site instead of you if you obfuscated). From a dev's POV - I won't believe you on the elegance & quality of the source unless I can see it, and that's very much what I'd be interested in paying for (an elegant/clean/flexible UI base). Obfuscating at all is somewhat like selling a fabulous custom car but hauling a dirty tarp over it before letting the prospective buyer get a closer look. Besides, it's HTML & CSS. De-obfuscating (unless it's seriously mangled, which seems dangerous) is as easy as copying the DOM and composed CSS from Firebug, I imagine, or cut/pasting the files into a good editor and auto-formatting. Or something; I can't say I've ever de-obfuscated a webpage before; when I check the source, if it's crap I don't keep reading. Which may be part of the point, here.
- mgkimsal 15y agoGenerate a PNG from the css/less source to prove its cleanliness, just without allowing anyone to use it for anything. :)