TomatoCart

We have finished a new roadmap for coming releases. The features in this roadmap represent the direction of future TomatoCart. Please follow this thread to post your opinion.

We plan to finish all these features in v1.2 and v1.3. In v.1.2 we will concentrate on the core enhancement including: template engine, frontend usability, performance & cache mechanism to build a robust and extensible platform for developers and designers.

We would very appreciate community developers can give us some suggestions concerning the core architecture; community designers give us feedback to help us improve the template system.

We also appreciate that the community become more active to help us improve our wiki and help people in community so that we can concentrate more on the development work and speed up the development.

Frontend
-- Support specials for products variants
-- Batch Updates to products in admin panel
-- Attribute Filters for Product Category and Product Search Result
-- Ajax List/Grid View for Product Category and Product Search Result
-- Allow customer to add tags
-- Two layout for variants in product info page：list view or dropdown menu
-- Google adsense integration
-- Allow article comments
-- Live Chat system Integration
-- Time-based Auction

Catalog
-- Improve Categories Tree Usability
-- Use categories tree in products List instead of dropdown menu
-- do server side sort for articles, articles categories, categories, products, customers grid etc
-- Product tag management
-- Color variant support
-- Allow Guest checkout
-- Google Base Integration
-- Improve product import/export system
-- grouped products
-- bundled products

Customers
-- Allow guest order in admin
-- Re-orders from customer “my account”
-- Customers Loyalty System (Store Credits)
-- Configurable allowed countries for registration
-- Control to display price to guests or not
-- Enable user to create customize fields for customer group

Orders
-- Allow Guest checkout
-- Allow multiple invoices, delivery slip for each order
-- Allow multiple addresses for each order
-- Allow re-orders for customers from administration panel
-- Telephone number over Orders in admin panel
-- Out of stock e-mail alerts
-- [new]sending the invoice to the customer via email through the admin interface

Shipping Module
-- USPS

Shopping Cart
-- Shopping Cart with tax and shipping estimates
-- When the right cart is disabled, Flying ”add to cart” effect to header cart

Front end
-- Integrate TomatoCart with Social Network sites such as Twitter, Facebook to attract more customers, new product or article will be automatically posted to these social networks

Core
-- Optimize TomatoCart framework with better OOP design
-- Update database scheme to ensure Database Integrity with Foreign Keys
-- Allow zipped payment modules, shipping modules, templates upload and install
-- Web Services API to exchange data with other applications
-- PCI DSS compliant
-- Optimize the search query and improve the cache mechanism to improve frontend performance
-- Integrate Upgrade script inside installation routine

Template System
-- Rewrite store front based on MVC pattern
-- Extend the template system to support multiple instance of template module
-- Improve the template engine for Dissociate CODE and CSS, easy customization and upgrade
-- Use css button instead of image button
-- Support customizable configuration parameters for each template
-- Visual editor for template management, allow user to drap and drop template module and modify the parameters
-- Control the navigation menu from backend
-- Right to Left Support
-- Enable users to assign different layout for different products categories and products

Those new features sounds good!
Also shouldn t you focus on BUG correction first ???
The number of open bugs in bug tracker have been increasing lately. Arround 50 (20 before 1.1).
I believe that sorting those should be the priority... in a version 1.1.2

I agree the 1.2 should focuse on the core and the template. The development documentation on the wiki is also very welcome.
All this should help bring more developpers to the platform. (especially the naming of the classe file confusing when lots of files are open)

WoW cool!!!!
any chance for UPS/FEDEX module as well?
Also is there an ETA? I cant wait.........

Very Good and Serious roadmap, think all this features should be sorted by priority, (perhaps with a poll to let him speak comunity opinions).Front is the first opinions of people, Some features are essencials for attracting more and more people in the community , so more devellopers ..
About bugs, i think many code will change and corrections in the same time.

yann wrote:
Those new features sounds good!
Also shouldn t you focus on BUG correction first ???
The number of open bugs in bug tracker have been increasing lately. Arround 50 (20 before 1.1).
I believe that sorting those should be the priority... in a version 1.1.2

I agree the 1.2 should focuse on the core and the template. The development documentation on the wiki is also very welcome.
All this should help bring more developpers to the platform. (especially the naming of the classe file confusing when lots of files are open)

We are working on the bug fix and new features simultaneously. Of course the bug fix has the highest priority.

as the proverb goes:many hands make light work; so we post the roadmap here to attract more develpers and designers to give us suggestions concerning the core and the template system so that we can make it better.

very good news zheng, I like the roadmap, do you have some estimate about the time for version 1.2? I know is difficult but is good to know 4 month, 7 mothn 1 year?, is good for community to know the date, other thing where are posting the bug found in the version 1.1? because here code.google.com/p/tomatocart/source/list i do't watch change since code.google.com/p/tomatocart/source/list

regards
Frank