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:Dfastuning wrote:Please, add posibility of use Products as Options and control stock
Also, KITS creation from multiple products.
artisantool.co
Don't forget to add [SOLVED] to your Thread Title (first post), if your issue is solved.
Great job it's responsive template! 
Please check cart page on mobile:
Please check cart page on mobile:
width.png (90.55 KiB) Viewed 14004 times
مصمم ومطور متاجر إلكترونية | @Oc_Style
لطلبات التصميم، تعريب القوالب والاضافات، ترقية الإصدار، حماية المتجر قم بمراسلتي من خلال المنتدى
موديل: إشعارات البنوك السعودية
1 | 2 | O :طرق لحماية السكربت
http://forum.opencart.com/viewtopic.php?f=120&t=107615tjsystems 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
See all my extensions: https://www.opencart.com/index.php?rout ... 20OpenCart
Thanks Daniel for the update. Looking forward to it for new projects. Obviously, we need to give it sometime to get stable.
Regards,
Marvin
Regards,
Marvin
You want to thank me for my time! 
Click here to donate
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.
I don't think any of us want to see a v2.0.1 released a couple of days later.
OpenCart custom solutions @ https://villagedefrance.net
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.
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.
OpenCart®
Project Owner & Developer.
Great work - looking forward to use it. If you add blog module as seen in your opencart website it will help lot of users.
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.Daniel wrote:maybe use a auto loading function instead of the current loader class.
Export/Import Tool * SpamBot Buster * Unused Images Manager * Instant Option Price Calculator * Number Option * Google Tag Manager * Survey Plus * OpenTwig
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;
}
}
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;
}
}
OpenCart®
Project Owner & Developer.
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:
Code: Select all
....
// Length
$registry->set('length', new Length($registry));
// Cart
$registry->set('cart', new Cart($registry));
....
Code: Select all
require_once($action->getFile());
$class = $action->getClass();
$controller = new $class($this->registry);
For example, we use this in the Override Engine for library classes:
Code: Select all
// Factory
$factory = new Factory($registry);
$registry->set( 'factory', $factory );
....
// Length
$registry->set('length', $factory->newLength($registry));
// Cart
$registry->set('cart', $factory->newCart($registry));
....
Code: Select all
$file = $action->getFile();
$class = $action->getClass();
$controller = $this->factory->newController( $file, $class );
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:
Code: Select all
$this->data['header'] = $this->load->controller( 'common/header', array($this->registry) );
Export/Import Tool * SpamBot Buster * Unused Images Manager * Instant Option Price Calculator * Number Option * Google Tag Manager * Survey Plus * OpenTwig
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.
Who is online
Users browsing this forum: No registered users and 9 guests
