Thanks for all the awesome feedback. To summarize most of the questions, yes it's compatible with the ThemeForest requirements, including Phase 2. We have a theme coming out in November that will demonstrate this.
seems to be an awesome framework!
I'm curious about this:
Integrate required plugins into your theme, to install when the theme is activated."
Is it like TGM Plugin Activation ? Does it support plugins updates from the theme package?
That's built using the TGM class. It uses an admin interface during development so you don't have that config file to fill out for each plugin. Just upload a ZIP file for a plugin and it will be included in the theme.
When you do a theme update, you can simply replace the plugin ZIP file with a newer one. The theme will automatically read the file and determine if it's newer than the installed plugin on the customer's site. If it is, the prompt to update will be displayed and everything else is automated the same as TGM. It's a bit easier because you don't update version numbers in the config PHP file like the TGM class, just copy the ZIP file.
We'll have more options for this later to handle things like remote hosted files and core WP repository. Those features exist but we haven't yet added the admin interface for them.
I wonder if this framework fits the new theme requirements.
EDIT: I see you can sort of export a theme as an individual theme. Does that mean it will output a theme with the build options without the options framework to build options?
When the theme becomes a stand-alone it removes the development tools like the Options Builder.
We think it's a good idea to distribute the theme in both child and stand-alone format so developers buying the theme can use the child version to customize the admin for their client. It's amazing how much time that can save when you're not learning another person's code structure when all you want to do is rename or remove an admin option. We already have customers doing this with our existing themes and we will include the child (development) version of our themes in the future.
Awesome... thanks for the new post and moving it out of the Ultimatum one.
Now we can ask the Ultimatum people to post about Ultimatum here... ROFL.
Ha! Getting a taste of my own medicine.
It looks really nice, but seems to me that approach to pack theme with extensions instead of plugins is completely opposite new TemeForest requirements for themes?
Correct, that's why i also had my doubts if it is according the new requirements - with the point you make it is not indeed.
We have a theme coming out next month, after Phase 2 begins, so it definitely will be compliant with those rules. I spoke with Japh and other Envato staff at the PressNomics conference about this so there is nothing to worry about on that side.
Extensions can be anything, which means you have to put things there that can't be included in the theme after Phase 2. That being said, we're adding a feature to our Plugin Installer extension so any active extension can be selected to "Install as plugin" which will truly make it easy to be compliant with ThemeForst changes. Extensions are modeled after Plugins so this is a really simple update. Once we add this you can let the framework do the work of separating the functionality for you.