OpenCart Community

fastuning wrote:Please, add posibility of use Products as Options and control stock

Also, KITS creation from multiple products.

You should put feature requests in the feature request thread. It would probably get more attention than in this thread about the new template;-) Please don't take offence by this as I also want to see kitting added, just trying to help get posts into the correct thread:D

Great job it's responsive template!

Please check cart page on mobile:

Is it posible to download this theme for 1.5.x? I'm just started making our template reponsive, it's gonna save me a lot of hours....

thanks,
Tim

tjsystems wrote:Is it posible to download this theme for 1.5.x? I'm just started making our template reponsive, it's gonna save me a lot of hours....

thanks,
Tim

http://forum.opencart.com/viewtopic.php?f=120&t=107615

Thanks Daniel for your hard work. Hope OpenCart 2.0 will be more robust and faster. All the best.

Hi all! Thanks, very beautiful template, even if it use bootstrap, but... what about terms of release? When will be OC 2.0 lock&loaded?

versu wrote:Hi all! Thanks, very beautiful template, even if it use bootstrap, but... what about terms of release? When will be OC 2.0 lock&loaded?

No one knows?

its taking a while but getting there.

Daniel wrote:its taking a while but getting there.

thanks, will wait impatiently!

Thanks Daniel for the update. Looking forward to it for new projects. Obviously, we need to give it sometime to get stable.

Regards,

Marvin

Hi,

When do you think 2.0 will be released? Eagerly waiting to use it in a big project, with the responsive/twitter bootstrap framework. Anyone know a rough time estimate, we talking weeks, months?

Cheers!

I remember waiting for 1.5 and thinking it was imminent for ages, then went through 2 more versions of 1.4 so I'm guessing it will be ready when it's ready

Great things cannot be rushed !
I don't think any of us want to see a v2.0.1 released a couple of days later.

villagedefrance wrote:I don't think any of us want to see a v2.0.1 released a couple of days later.

Its imminent, any version of OC (and not only OC) is not ideal, so there is always something to fix or update

I think it will be released this year. this is what's left:

finish the updating the file manager (currently working on this)
finish the custom fields
apply the new catalog template css changes to the already converted bootstrap 3 template.
clean up the new admin, minor css changes required.
move over new paypal stuff from 1.5.6.1 to 2.0 and try to make it match up with opencart style code.

on top of that i might do a few core changes. maybe use a auto loading function instead of the current loader class. stuff like this can be done quickly though with mass find and replace. i don;t want to do this now because i need system that works to while doing other changes.

Great work - looking forward to use it. If you add blog module as seen in your opencart website it will help lot of users.

Daniel wrote:maybe use a auto loading function instead of the current loader class.

I think using a factory class for loading the controller, model, and library classes would be more useful. That's how we do it in the Override Engine.

we sort of already are using a factory class. the loader class is a factory class.

i was thiking $this->data['header'] = new ControllerCommonHeader($this->registry);

then in the render method can be:

foreach ($this->data as $key => $value) {
if (is_object($value)) {
${$key} = $value->index();
} else {
${$key} = $value;
}
}

Not quite a factory class yet. For instance, in index.php you still create the class instances directly:
Or the controller files are instantiated like this in your system/engine/front.php:
With a real factory class, the factory might also instantiate possible extended classes, where the extended class might have overridden methods to modify some of the core class behavior.

For example, we use this in the Override Engine for library classes:
And this for controller classes instantiated in the system/engine/front.php:
We leave the business of loading the class file to the factory class. The factory may load the original class file, or a modified original class file (modified e.g. by your new VQmod-style modification class), or another file containing an extended class, in addition to the original class file. Using a factory class is more flexible than PHP's __autoload mechanism, because you can also load and instantiate extended classes from whatever is found from an additional override folder.


P.S.: I just noticed you have started adding some useful new methods to your system/engine/loader.php, such as

public function controller($route, $args = array())
public function model($model)
public function view($template, $data = array())
public function library($library)
public function helper($helper)
public function database

If you were to always use this new Loader class to instantiate all the other classes, then this could easily become the new core factory class with similar functionality! In fact, I could then easily port our Override Engine to using your updated Loader class. For example, a controller class could then be instantiated like this:

anna_raiders wrote:If you add blog module as seen in your opencart website it will help lot of users.

I also second this about adding a blog module similar to whats on this site would be great and i also think a lot of users will appreciate this.