EDIT: I’ve started moving this article to the wiki and will not update this post any more!

In my last post I started a list of things to do before the magic 1.0.0 release. I’d like to keep this post as a reference for things to do. Hopefully, I’ll be adding (and removing!) things often as I go.

Of course, suggestions are highly welcome…

• admin – maintenance
• facets
• other plugins
• make ZMPluginView more useful and start using it (this will require changes to a few plugins that do funny things like loading files and eval’ing them…)
• review email templates and integration (plus perhaps a new email service?)
• review the remaining template functions (l10n, i18n)
• alternative shipping/payment/order total modules
  NOTE: This is actually not to replace or re-implement any existing code. However, should plugins wish to implement new modules, that should be possible without relying on globals (in particular as those might not be available using ZenMagick in the first place)
• review the security code – for one thing it’s not possible to have multiple authentication sources (one alternative could probably be OpenID)
• Review and perhaps improve the price/attribute lookup code (reduce database queries)
  (mostly done, but more possible)
• Convert all code to using the new ZMDatabase API (this has evolved quite a bit since 0.9.1) [2 or 3 more to go]
• Review all code that creates files with a focus on file permissions
• Review and either justify or change the use of model classes to populate forms
• Convert the search to using ZenMagick [would be ok if I can get the SQL changed so no binding is needed)
• implement product listing default order: PRODUCT_LISTING_DEFAULT_SORT_ORDER
• Write a 5 minute installation guide, based on this post
• allow to configure the controller clas for a given page
• make all tests work with a vanilla demo data setup
• Have a single file, no dependencies page that verifies all requirements and advises on things that are missing/not ok
• reorganize settings, (build admin interface?) (started)
  
• update check
• plugin install option
• plugin upgrade (version check??)
  

Also, there are some things that are beyond 1.0.0, but nevertheless worth writing down:

• Start using the alternative bootstrap code (alpha at most at the moment) for all non checkout pages to further reduce the init code
• Redo session handling to start sessions only when really needed (any form of login, cart action, language change, etc) [I have a prototype class, but nothing production ready]
• Complete template review – refactor some of the view classes, access views and (side-)boxes (and others) via the same view access code. That should allow more fine grained caching. A possible implementation could have a PageView to access the full page and FragmentViews to access smaller bits like boxes, views, etc. However, rather than re-inventing even more wheels it might be more effective to improve the Smarty plugin and probably complete the smarty default theme.
• Have some more themes
• widgets (of some sort)
• Create an ‘Installation Wizard’ separate from the current Installation page
• Allow to map controller to page names – this would allow to reuse controller without any change for
  new pages