Loan road to Commerce v3.0 stemming back from OS Commerce v2.2 Milestone 3 and maturing throughout the v3.0 Alpha releases. This long journey has never been about adding new features into the core to stop at and to possibly include a kitchen sink, but a long journey of improving a procedural based codebase and striving for a perfect, high quality level, OS Commerce framework to use as our foundation for future releases that can also be easily extended on. We’re never going to reach “perfect OS Commerce”, but we’re close and the result between OS Commerce v3.0 and OS Commerce v2.2 are clearly worlds apart.

We want to pass this result to OS Commerce developers and want to share and see the same high level of quality being placed into the Add-Ons they make available.

This won’t be achieved with a simple text file document titled “coding_standards.txt”, but actually utilizing OOP (Object-Oriented Programming) design methods in the framework. This stems across the visibility of class methods and properties (public, protected, and private), to abstraction (subclasses, abstracts, and interfaces), to OS Commerce design patterns.

Not only does the OS Commerce framework utilize PHP v5 OOP features, but is also set to log each and every programming error encountered, from fatal errors that stop further loading of the application, to simple notice messages when undefined variables are accessed.

Our goal is to deliver OS Commerce v3.0 without any errors logged at the highest possible level (E_ALL | E_STRICT), and force this requirement onto developers to provide the same results with their Add-Ons.