Posts by der

Siddharth said
From a quick look, this looks really excellent. Do you mind if I do a quick write up on Nettuts+ about this?

Not at all! More exposure will help the project grow!

Keep me posted when you do so

Hi all. I’ve just released a new Open Source project some of you might be interested in

CoreJS is an Open Source Web Application Framework, using the MVC Architecture written in CoffeeScript, allowing you to create Powerful Web Applications with ease, keeping your code clean & readable.

Using an Object Oriented workflow, you can create, extend and reuse classes to be used within your applications. You can configure several environments for your applications, using a common configuration approach. Prototypal inheritance is used behind the scenes to provide a simpler Object Oriented Inheritance.

You have a build system based on Cake, CoffeeScript’s build tool similar to Make and Rake. This allows you to automate and configure several aspects of your applications, such as building the documentation, or performing maintenance / cleanup.

For a detailed feature list, check out http://core-js.org

Guide: http://core-js.org/guide

Github Repository: https://github.com/derdesign/CoreJS

Hope any of you find it useful

Users usually ask for a refund when their “expectations” are not met, specially when they want to do something that is not possible within the theme’s feature set. On 99% of the cases there’s nothing wrong with the theme.

Do your best to solve any bugs present in your themes. The only way they’ll get a refund is if the product is not working, which is rare since themes go through a review process in order to get approved.

Also, there are some pretty annoying people that will make you lose your patience sometimes (try not to, at all costs). Then you tell them one thing or two that makes them uncomfortable, and they will ask for a refund too, either by lack of functionality or by dissatisfaction with your support service.

I think the right place to post this question is in the product’s comments… You might get the answer you’re looking for. Pre-sales questions are usually handled in each of the product’s comments pages. The forums are for other types of topics

Well, here’s what you could do: Instead of sending the tags to the client, you could instead send the URLs of such scripts. After you receive the URLs in the AJAX response, you can create an array with those URLs.

You can then pass the array of script urls to head.js. The scripts can be loaded either synchronously or asynchronously (in parallel, but execute in order), your call.

Also, you can run a callback after all the scripts have been loaded, maybe the initialization code that should be run after all the scripts are loaded. If you’re including such initialization code in one of the scripts, there is no need to do so, since the scripts are executed after they are loaded into the DOM .

Hope it helps

Count me in

Hey @crozer, you better get AVG Free, if I know a virus stopped you from releasing more crozerawesomeness, then I’d feel very bad

Kriesi said
The smartest solution would be to create a copy of the current theme, pack it into a backup zip file and then update. that way the user can always revert back easily in case something went wrong…

I think this would be perfect.

Regarding what @duotive said about child themes. I also thing this would be a great idea. But the child theme advantages should be exposed (or enforced) by ThemeForest, not by authors themselves. This provides an advantage since the benefits would be explained on a per-theme basis, not on a per-author basis.

Also, including a changelog of updates (as @kailoon said) would be a good idea to include as a link. Something like “What’s changed since version 1.0.2 for example”. This could point to a changelog page, which could be automatically generated by using data provided by theme authors. This data could be collected by adding a textarea on the theme edit screen, so authors can specify what has changed in this version (in a detailed way).

The changelogs page could be placed next to the “FAQs” tab on the theme’s product page.

Another thing that crossed my mind, is that the update scheme should be versioning-scheme-agnostic. This means that if you use x.x.x or x.x or whatever versioning system authors use, the envato update plugin should be able to manage these with ease. Or, maybe they can provide a versioning scheme so authors use it instead.

This is definitely a great move. There are times where authors should be heard, and times where buyers should be heard. There have been times where a feature like this has crossed my mind.

It has many advantages both for authors and users, here they are, based on my experience:

• Many fixes come with updates, so you just point the users to update the theme (from their WordPress admin panel) to fix the issue. This increases customer satisfaction. This buyer is very likely to buy again from you
• When users see an update, they will very likely upgrade to a new theme version. This is good & bad at the same time (see note below)
• The author doesn’t have to provide update notification for his themes, nor he/she needs to worry about implementing an update notification system (even though there have been authors who have provided the code for free), envato does notify the users directly from their source, real time (or something like that)
• The user won’t have any problems updating the theme to the latest version. They usually upload the ZIP file downloaded from ThemeForest, not the theme’s ZIP . This is a problem you won’t need to handle yourself anymore (at least not as often)

Note:The update notification system (provided by envato) must include a notice stating that any changes and customizations made to the themes could be lost after updating (this would make your customers very mad). Obviously, this might not be the case for some themes, where only the core gets updated (not the templates themselves). Very rarely a theme update happens on the frontend (based on my personal opinion and experience).

Very good idea. You’re definitely listening to customers and that’s a good thing! Thumbs up for you guys…