I have been toying with the idea of merging Bootstrap into osCmax to provide a easy templating system + responsive design. My question is should we go down this route? By extending BTS to cover basically all files within the core you can call new versions of all of the files to use <div>s and bootstrap and leave the core code untouched - however, this has a major drawback since large portions of the code would be duplicated in the two places. (Core and Template).
The other option is to switch the core for osCmax which I do not like as it will deprecate everyone's existing stores which like osCommerce and others creates a massive split between those who have moved and those who have not.
Despite Burt's comments the other day I still feel that osCmax is fundamentally a good product and with a responsive design could be great. Okay some of the core is bit old but it does work!
Anyway, enough rambling ... what should we do next?
Blimey, you're quick off the mark! [I've been mulling this over for weeks]
I like the idea of a parallel BTS code base, primarily as an interim release. Whilst it will duplicate a lot of files, it does give a way forward, to removing the 'tired' table structures.
For folks that have a limited number of add-ons over and above osCmax, it will provide an easier transition. Where only some customisation has been done, it should be relatively quick to convert any tables to CSS.
My main concern is the size of the core files and the inclusion of a lot of extraneous 'stuff' for many people.
1. I still maintain that all non-English language files should be split from the core and be made available as language packs.
2. In utilising BTS (notwithstanding possibly a few core tweaks), the Responsive fileset could be produced as an add-on pack.
3. To drive this development, only bug fixes should be addressed in Bug Tracker, unless additions/features can be quickly added that will benefit more than just a few users.
In summary, yes, and this should be given some priority.
[Is your screenshot just a mash-up, or an actual working template?]
I would love a responsive and or mobile template I dont really care way much how its done, I just REALLY dont want to start learning new stuff right now!
@Ridex - that is a live install ... need to spend a bit more time on it before I commit to SVN for others to play with ... I have only done some very basic changes as a proof of concept.
Re: languages - I agree but we need some sort of online tool - does anyone know an open source one (like myGengo String?)
Last edited by pgmarshall; 03-24-2014 at 12:42 PM.
@Ridex - that is a live install ... need to spend a bit more time on it before I commit to SVN for others to play with ... I have only done some very basic changes as a proof of concept.
Re: languages - I agree but we need some sort of online tool - does anyone know an open source one (like myGengo String?)
I recognise that it is a proof of concept and more development is required. I was just offering to build on what you have, rather than the two of us working independently - hence using SVN. I/we could start another Google code project, unless Michael can quickly put up another branch for us to use, on the existing project.
TBH, the languages are manually done at present, so there is no backward step in making them language packs. I'm willing to do the split.
(I'm trying to push this before I get distracted by something else or the mood escapes me! )
((Strange: I didn't get notified of your reply. ))
Last edited by ridexbuilder; 03-24-2014 at 02:51 PM.
I've been lurking for a while now trying to decide whether to use Oscmax or not for my next project and the lack of a responsive design template is definately stopping me from trying your product. Especially since I saw a report on tv that states over 60% of all online shoppers now use their smart phones to shop and don't even own a desktop any more. So it seems you're on the right track and I will wait and see how long before you provide mobile support with responsive design.
Not 'our' product - it's supposed to be a community effort
Originally Posted by nootkan
..see how long before you provide mobile support with responsive design.
A start has been made, though a recent well publicised event, (and other 'stuff') meant effort had to be expended elsewhere.
Now that osC has a mobile framework to work from, it is a (non-trivial) matter of seeing what can be shoehorned in and where.
Not 'our' product - it's supposed to be a community effort
Sorry didn't mean to imply anything, poor choice of words on my part.
A start has been made, though a recent well publicised event, (and other 'stuff') meant effort had to be expended elsewhere.
Now that osC has a mobile framework to work from, it is a (non-trivial) matter of seeing what can be shoehorned in and where.
Okay, I'll check back at a later time to see how much progress has been made. Really like what I see with oscmax 2.5 and the progress to date from back when I first looked at it many moons ago. Even found my old site files created with oscmax on my old computer back when I was experimenting with it. lol
Sorry didn't mean to imply anything, poor choice of words on my part.
No probs. I stick my foot in it frequently.
Originally Posted by nootkan
..Really like what I see with oscmax 2.5 and the progress to date from back when I first looked at it many moons ago. Even found my old site files created with oscmax on my old computer back when I was experimenting with it...
I regularly chop and change from old to new versions (upgrades etc.) and get confused about what is available to each version. Unlike many other e-commerce alternatives, it is relatively easy to upgrade, retaining your customers, orders and products. Give it a go on your old site (with a backup) and see what ya reckon - be sure to check recent upgrade threads, for SQL gotchas.
Bookmarks