Anyone up for it?
With the limitations of 2.3.4 becoming more evident and a lack of progress from the official branch making it difficult to move forward, we should "go it alone" on 2.4.
@burt has done a fantastic job of the Community Version so far but improving 2.3.4 any further isn't worth the effort, as he's already indicated by making it Final.
I feel effort would be better spent on software more suitable for everyone.
We have the basic building blocks:
1. The software - https://www.oscommerce.com/Products
2. How to build an app step by step -
3. Documentation - https://library.oscommerce.com/Online&en&oscom_2_4&developers
We would need commitment from community members to make it happen!
Already done according to the documentation:
Introduce a framework to replace legacy classes and functions with.
Bootstrap Frontend Framework
Replace the jQuery UI based Shop, Admin, and Setup frontend with Bootstrap.
Introduce self-contained Apps with support for self-defined modules and url routes.
Introduce hook calls.
Introduce an online update feature for the core.
INI Style Language Definitions
Move the language definitions to ini style files.
Still needs to be done (according to the documentation):
Move core modules to an osCommerce App.
Migrate remaining classes to the new framework, including:
Introduce SEO features.
Database Schema Comparison
Introduce a database schema comparison tool existing store owners can use as part of their upgrade.
Hook Action Calls
Finalize hook action calls throughout the codebase.
Extend the online update feature to installed Apps.
Introduce an online App browser and installer.
Support community maintained language packs and provide a list of ready to be used languages in the setup routine.
Legacy Compatibility Module
Automatically re-map legacy v2.3 classes, functions, and code to the new framework for compatibility with existing v2.3 add-ons.
There would be a problem with the online app browser, installer and update feature of course, as that hasn't been implemented anywhere yet.
There is also a hidden templating feature which would need to be worked on. There are templates for:
Admin - includes/OSC/Sites/Admin/Templates/Sail
Store - includes/OSC/Sites/Shop/Templates/Sail
There would need to be admin to install and switch templates. I can't see that in the current code.
So, I think the most important thing to do first would be to analyse what is important, what should be added (product, products, customer classes for instance?), what can be ported from 2.3.4 Community Edition (updated breadcrumb module etc) and then exactly what needs to be done. After that, a roadmap can be created.
Time to leave 2.3.4 Community Edition behind and start on something new.