If that's the decision then so be it. But it's a ridiculous one given how poorly the templates are structured at present.
I do, however what I'm looking for is a streamlined design process. From a designer's perspective, I would like to be able to offer my clients multiple templates to choose from. To be sure about what I'm saying, by 'template' I mean 'header/three columns/footer'. It would be nice to be able to control some of these elements from the admin panel, i.e. hide a column, make the site fluid Vs fixed width, change the background etc. Obviously this is a lot of work, so in the short/medium term it would be suitable to simply have a few different structures ('templates') out of the box.
That way I can just pick a template, change the graphical elements, and the site is ready to go. At present a great number of files need to be extensively modified for some fairly minor front-end layout adjustments. And with the rate of changes to the site's code, it's not necessarily practical for me to create my own range of templates as I may need to update them again with each release.
I'm not saying that this is a priority feature, but I find it hard to fathom the decision 'let's never offer more than one template'. It just seems to be a very final decision.
That way I can just pick a template, change the graphical elements, and the site is ready to go. At present a great number of files need to be extensively modified for some fairly minor front-end layout adjustments. And with the rate of changes to the site's code, it's not necessarily practical for me to create my own range of templates as I may need to update them again with each release.
I'm not saying that this is a priority feature, but I find it hard to fathom the decision 'let's never offer more than one template'. It just seems to be a very final decision.
If you'll look back over this whole thread I think that you'll see that it is supposedly going to get much easier to make the type of changes you are talking about, but I still don't see why all the designers keep saying you can't do different themes using opencart. You can make any type of theme you want to and it's really not all that hard. The biggest pain is one that the "desingers" pushed for in the first place. The removal of the layout.tpl so that now you have to make changes to a bunch of files instead of just one, but all the "designers" said they wanted to have the flexibility, though I haven't seen a single one use it, just complain that it's too hard to make anything "different".
OpenCart commercial mods and development http://spotonsolutions.net
Layered Navigation
Shipment Tracking
Vehicle Year/Make/Model Filter
Don't get me wrong - I'm not saying it's difficult to customise. I'm just saying that it could be improved by having a couple of templates out of the box, so that I can then offer more than one style of layout to a client.
We have to make a couple of designs so you can offer (as in: sell?) to your customer?oneilldesign wrote:Don't get me wrong - I'm not saying it's difficult to customise. I'm just saying that it could be improved by having a couple of templates out of the box, so that I can then offer more than one style of layout to a client.
Right....
Norman in 't Veldt
Moderator OpenCart Forums
_________________ READ and Search BEFORE POSTING _________________
Our FREE search: Find your answer FAST!.
[How to] BTW + Verzend + betaal setup.
Like I said, structure, not design. I don't plan on using the default templates, but I'd like to be able to use them as a starting point for a custom design.i2Paq wrote:We have to make a couple of designs so you can offer (as in: sell?) to your customer?oneilldesign wrote:Don't get me wrong - I'm not saying it's difficult to customise. I'm just saying that it could be improved by having a couple of templates out of the box, so that I can then offer more than one style of layout to a client.
Right....
I really want to install OpenCart now and get started setting up my store, but I'm concerned that 1.5.0 will be released and I'll have to rework the entire setup. Is there any word from anybody in the know that can help me to make a decision?
I know it sounds like I'm afraid of a little work, and that is because I am. =) I have fairly severe arthritis, and I try to avoid working with my hands when the results are going to be futile. I know it will happen eventually, but if eventually will be within a few days, I'll just wait.
Thanks for any helpful response.
I know it sounds like I'm afraid of a little work, and that is because I am. =) I have fairly severe arthritis, and I try to avoid working with my hands when the results are going to be futile. I know it will happen eventually, but if eventually will be within a few days, I'll just wait.
Thanks for any helpful response.
I have no insider knowledge, but since Daniel said he was shooting for the end of October, I think it's likely that 1.5.0 will be released soon. That being said, if a lot of things are changed, it's also likely to have a number of bugs (since bugs are generally proportional to changes) so I don't know if I would use it for a live shop right away. You could end up really wanting to wait until 1.5.1, and there's no saying how long that would be.
Right now 1.4.9.1 (plus 1.4.9.2 patch) is very stable, and definitely a good package. My recommendation is to wait as long as you can, and if 1.5.0 hasn't been released / has major bugs that affect you, go with 1.4.9.2 when you actually need to get started.
Right now 1.4.9.1 (plus 1.4.9.2 patch) is very stable, and definitely a good package. My recommendation is to wait as long as you can, and if 1.5.0 hasn't been released / has major bugs that affect you, go with 1.4.9.2 when you actually need to get started.
I personally don't care for admin controllable templates.. only because it conflicts with the css. ZenCart has this problem. You can enable/disable columns in the admin, as well as set the width of the column and the modules, but if you have a custom template that uses css to design things properly, things get skewed. Since we use MVC framework, we should really try to keep as much of the view in the view as possible.
i could make the system so the ytemplate controllers what is loaded using javascript.
i think shopiginiter said they do this. not sure how good it is for indexing though.
Code: Select all
<script type="">
$().load('index.php?route=module/information');
</script>;
OpenCart®
Project Owner & Developer.
I really wouldn't load page elements into the DOM via Javascript on load. It slows page load unnecessarily. And it's a bit overkill imo and complicates things. I guess not many people want to hide or move blocks around the page all day long. Things like these are better done by the theme designer.
About themes: I think what's most important is to have a set of template tags that doesn't change (coming from a front end developer's view). The good thing about Opencart is that the default theme looks simple and easy to work with. This drives people who know a bit CSS/HTML to adapt the script. And those who want something fancy can always go with a free or premium theme.
About themes: I think what's most important is to have a set of template tags that doesn't change (coming from a front end developer's view). The good thing about Opencart is that the default theme looks simple and easy to work with. This drives people who know a bit CSS/HTML to adapt the script. And those who want something fancy can always go with a free or premium theme.
yeah I have to say I don't like the sound of loading the modules through javascript.
I think there are basically two big things with the current template. It is not designed so that if you disable all modules in one of the columns the center content will take over the space. It should be it's not overly difficult to make it that way, and it would quiet many of the people who complain they want a two column layout. The second is all the stupid inline styles left in it. I am working on another site where gray boxes don't fit, and you have to edit every single file to get rid of them when it could have easily been done with one class in the css file.
I think there are basically two big things with the current template. It is not designed so that if you disable all modules in one of the columns the center content will take over the space. It should be it's not overly difficult to make it that way, and it would quiet many of the people who complain they want a two column layout. The second is all the stupid inline styles left in it. I am working on another site where gray boxes don't fit, and you have to edit every single file to get rid of them when it could have easily been done with one class in the css file.
OpenCart commercial mods and development http://spotonsolutions.net
Layered Navigation
Shipment Tracking
Vehicle Year/Make/Model Filter
That's all I was really saying - there should be some more flexibility with the way templates are created/handled. It would be nice to have multiple templates out of the box, but I'd definitely settle for some changes that make it easier to configure the layout without editing as many files.
I agree completely.Qphoria wrote:I personally don't care for admin controllable templates.. only because it conflicts with the css. ZenCart has this problem. You can enable/disable columns in the admin, as well as set the width of the column and the modules, but if you have a custom template that uses css to design things properly, things get skewed. Since we use MVC framework, we should really try to keep as much of the view in the view as possible.
Alternatively, store the CSS on the site itself for easy template switching.
not sure what you mean by this one where else would you store the CSS? on someone elses site?oneilldesign wrote:Alternatively, store the CSS on the site itself for easy template switching.
OpenCart commercial mods and development http://spotonsolutions.net
Layered Navigation
Shipment Tracking
Vehicle Year/Make/Model Filter
Sorry, I typed that in a rush. I meant store it within the admin panel rather than a file on the server.
Please don't do that. There is nothing worse than having to edit your css in a textarea.
All we need is a layout manager. By default, all pages should use layout.tpl. However, a custom layout can be defined and applied on a per-category, per-product or per-information page basis. Think of it as theming on a more specific level.
Or, we all just simply wait and see what sort of changes Daniel has cooked up for 1.5 before we get too far ahead of ourselves.
All we need is a layout manager. By default, all pages should use layout.tpl. However, a custom layout can be defined and applied on a per-category, per-product or per-information page basis. Think of it as theming on a more specific level.
Or, we all just simply wait and see what sort of changes Daniel has cooked up for 1.5 before we get too far ahead of ourselves.
OpenCart Extensions, Technical Support & Custom Development | Have I helped you?
Who is online
Users browsing this forum: No registered users and 7 guests
