Help Rebuild OsCommerce
Moderator: General Moderators
One thing I would still like to clear up is the "Rebuild osCommerce" part. I don't particularly like being constrained to calling it an osCommerce rebuild. I would like the freedom to (if we like) stray very far from osCommerce. I think by calling it a rebuild of osCommerce, we are constraining the project by quite a bit.
I am all for taking a lot of osCommerce's features and implementing them better, and in an OOP format, if that is what we are doing, but I would like to make this abundantly clear beforehand. Is that what we are doing, or are we literally "Rebuilding osCommerce"?
I am all for taking a lot of osCommerce's features and implementing them better, and in an OOP format, if that is what we are doing, but I would like to make this abundantly clear beforehand. Is that what we are doing, or are we literally "Rebuilding osCommerce"?
I'm with The Ninja Space Goat, we need a new name and a new project instead of going and re-code every file on OsCommerce.
I'm in for the client-side part, that is: taking an image/design someone makes and convert it into valid XHTML and CSS.
As for programming, I don't know right now. I don't want to sound negative, but if we estimate whether this will success of fail according to the replies this thread gets here and taking into acount the size of the thread we had on our PHP Book project... This won't work.
Take a look at the thread we had about the book... how much we had been discussing about it, how much people said they would like to help... and then take a look at how much people actually wrote something...
Again, it's not that I'm negative... I'm just realistic.
I'm in for the client-side part, that is: taking an image/design someone makes and convert it into valid XHTML and CSS.
As for programming, I don't know right now. I don't want to sound negative, but if we estimate whether this will success of fail according to the replies this thread gets here and taking into acount the size of the thread we had on our PHP Book project... This won't work.
Take a look at the thread we had about the book... how much we had been discussing about it, how much people said they would like to help... and then take a look at how much people actually wrote something...
Again, it's not that I'm negative... I'm just realistic.
This is something that I am pretty interested in. Here are some of my random, unorganized thoughts:
I agree that if we did this, it should be a total rewrite, or in other words, a completely independent project of osCommerce. PHP 5, object oriented and ajax functionality. Fully validated xhtml and css. osCommerce itself is frame hell. Superior supply chain functionality and forcasting could make this a more serious application than something run by just small web vendors. Completely customizable interface. As with osCommerce, a fairly static layout with "theming" isn't adequate in my book. Attention to speed and efficiency, and as always security is a given. Fully functional using text browsers and handheld devices. Meets web accessebility standards. Built-in i18.
GOOGLECODE!!!
~fin~
I agree that if we did this, it should be a total rewrite, or in other words, a completely independent project of osCommerce. PHP 5, object oriented and ajax functionality. Fully validated xhtml and css. osCommerce itself is frame hell. Superior supply chain functionality and forcasting could make this a more serious application than something run by just small web vendors. Completely customizable interface. As with osCommerce, a fairly static layout with "theming" isn't adequate in my book. Attention to speed and efficiency, and as always security is a given. Fully functional using text browsers and handheld devices. Meets web accessebility standards. Built-in i18.
GOOGLECODE!!!
~fin~
Book vs Open souce project... we are not writers and editors, we are programmers.Oren wrote:I'm with The Ninja Space Goat, we need a new name and a new project instead of going and re-code every file on OsCommerce.
I'm in for the client-side part, that is: taking an image/design someone makes and convert it into valid XHTML and CSS.
As for programming, I don't know right now. I don't want to sound negative, but if we estimate whether this will success of fail according to the replies this thread gets here and taking into acount the size of the thread we had on our PHP Book project... This won't work.
Take a look at the thread we had about the book... how much we had been discussing about it, how much people said they would like to help... and then take a look at how much people actually wrote something...
Again, it's not that I'm negative... I'm just realistic.
This is going to be a big one. Very important that this is FULLY customizeable. I have a few ideas about this too. I'd like to give our advanced users the option to edit our page templates with almost no restraint. MIVA merchant, which is what my company uses (to my dismay) allows a pretty good amount of customization due to the fact that you are allowed to edit their templates as well as apply styles.bg wrote:Completely customizable interface.
Simplicity is the key. And it is so excruciatingly simple to do this that people dont realize how simple it is and over complicate it. Using proper html and css in a way that content is completely separated from presentation is all it would take. Properly used CSS can define a layout in its entirety.The Ninja Space Goat wrote:This is going to be a big one. Very important that this is FULLY customizeable. I have a few ideas about this too. I'd like to give our advanced users the option to edit our page templates with almost no restraint. MIVA merchant, which is what my company uses (to my dismay) allows a pretty good amount of customization due to the fact that you are allowed to edit their templates as well as apply styles.bg wrote:Completely customizable interface.
Are you saying start from scratch? Are you a software engineer? I ask because a good software engineer could kick this project off on the right foot.bg wrote:it should be a total rewrite, or in other words, a completely independent project of osCommerce. PHP 5, object oriented and ajax functionality. Fully validated xhtml and css.
I'd like to volunteer my fingers for this.
I say that because I have no experience in large scale application design, but without wanting to float my own boat, seem to do pretty well with designing objects and components.
I r coder monkey. :p
I think the first step should be deciding on which design practice we will take. XP/TDD/etc.
I say that because I have no experience in large scale application design, but without wanting to float my own boat, seem to do pretty well with designing objects and components.
I r coder monkey. :p
I think the first step should be deciding on which design practice we will take. XP/TDD/etc.
Unfortunately the design phase is currently my weak spot, as it happens I am searching for a selection of books to purchase at this very moment.
Test Driven Design I am liking the sound of, however: this, I imagine, would enter the project at a later stage, because we can't build a test without atleast a primitive design.
Test Driven Design I am liking the sound of, however: this, I imagine, would enter the project at a later stage, because we can't build a test without atleast a primitive design.
Right.. well, first things first - let's name it.
I don't mind the name DN Commerce or similar.. with slogan "By the community, for the community." Cheesy/Corny as hell, but meh.
Next.. requirements.
Well, this is a self composed high level list of what I think a commerce system should entail:

Next up.. common developing environment! We need a framework that everyone involved will use to make shared development a LOT easier. Would also be good for everyone involved to have a few days/weeks to get familiar with the chosen framework. Be it a 3rd party F/W or we start one from scratch specifically for this project, the choice is ours to make! We should also decide if we will support PHP4, or develop for PHP5+ only. My personal opinion is PHP5+ only. By the time it gets finished PHP4 will be but a distant memory anyway.

I don't mind the name DN Commerce or similar.. with slogan "By the community, for the community." Cheesy/Corny as hell, but meh.
Next.. requirements.
Well, this is a self composed high level list of what I think a commerce system should entail:
- Catalog
Ordering system
Payment system
User/Customer accounts (for features such as order history)
Email (receipt/confirmation)
Next up.. common developing environment! We need a framework that everyone involved will use to make shared development a LOT easier. Would also be good for everyone involved to have a few days/weeks to get familiar with the chosen framework. Be it a 3rd party F/W or we start one from scratch specifically for this project, the choice is ours to make! We should also decide if we will support PHP4, or develop for PHP5+ only. My personal opinion is PHP5+ only. By the time it gets finished PHP4 will be but a distant memory anyway.