Send a DMCA takedown. Be ready for the legal implications of that.
All that does is fake the user agent of a different browser. It doesn’t change the rendering engine at all. Some of the configurations are useful for testing specific conditions, but you’ll always need the real thing: browsers and devices.
Veuse saidWell i hate that rule. For me, responsive design have no sense, I’m totally sure that almost any celllphone or tablet can show me the desktop version of a website, theres no need of a responsive version, at least for me.
cooledition saidThere is no rule that says you can not zoom in on a responsive website. If some developers do this, it seems like a very bad practice to me.
one of the things i hate on must responsive websites is that you can not zoom in photos. Also many times there are things in the desktop version that don’t appear in the responsive version and that piss me of lol
Typical graphic designer. Wants every canvas to be fixed size…
Blame the implementation not the technique.
Most of those complaints aren’t problems with responsive design. They’re just poor implementations.
@ Bovelett — Thanks for the opinions from a buyer.
The issue is that it’s impossible for individual authors to implement any kind of recurring yearly payments for theme updates. Firstly it’s forbidden in license terms…
Read the license. Selling updates is not forbidden or even mentioned anywhere in the license. The license has no jurisdiction over services rendered beyond the initial sale. By Envato’s own definition support is the domain of the author, and Envato doesn’t enforce or specify what that involves.
Authors just have to implement such a payment, verification, and delivery system by themselves. Yes, that’s a big undertaking.
I’m quite surprised that authors are happy with the currently lifetime free updates strategy.
That’s because you only make WordPress themes and HTML templates. If you worked on a bigger platform like Magento you might see things differently. WordPress is a tiny platform in comparison. 16,334 vs 1,168 files. That makes compatibility updates a big deal.
@ zeusmedia — Not necessarily an SLA. That would bind the author to provide fixes within a specified interval and be significantly more complex to contract. Ex: what defines a bug? It would be up to the author to define what level of support they want to provide.
Magento’s core package has 16,334 files. WordPress’ package has 1,168 files. Think about that.
Learning WordPress is a cakewalk compared to Magento. Magento themes are priced above WordPress because it’s a significantly deeper platform and architecture with a learning curve to match. It’s built for mission-critical eCommerce. Developing for WordPress is not really comparable.
Yes, I’d imagine the company would require you stop using it if they buy it.
Sell it, this is business. Make sure you price it according to the value they’re getting i.e. more than the time you put into it.
GravityDept saidI think you doing it wrong Also Gravity Dept… was wondering about your logo… did you know there is a hexagram shape on Saturn’s north pole? Is that the symbolism behind your logo, or is that just a coincidence.. video here
Am I doing this right?
Move along folks, nothing to see here. Ignore the 192 billion square mile hexagon on Saturn. Let the department do its work.