Wednesday, September 30, 2009

Package Structure

Digitalus Framework is going to be released as a set of packages, so you can export just what you need for a project, and don't have to sort through hundreds of files that you will never use.

Each package is going to follow the ZF standard project structure: /library, /public, /application

This will enable you to create a default project with Zend_Tool and then export the packages that you need into the root of the project.

I just released the first component, Dig_Core, but that is another story...


  1. How will templating/skinning work --
    it seems all who use the Zend framework are obsesed by abstraction and 'proper' coding methodolgies, the concept is good, but look at magentoecommerce, its bloated and slow, and the number of complaints about the templating/skining/theming is amazing, - although perfect coding practices are nice on paper, the reality is you need time and skill, so I guess it depends on who this product is aimed at.

    if it's the same small business people who want to use an opensource poject that simply 'GET THE JOB DONE' then there needs to be a balnce between perfect coding patterns and actually being able to do somthingas simple as add a new template & pages in without having to edit 50 different pages -- see things like MODX. CMSMS - CUBECART - CS-CART etc -- Magento is great -- but to hard, time consuming, bloated . slow

  2. i totally agree. when people start ranting and raving about best practices i respond with the oldie but goodie 'the best thing about standards is there are so many to pick from'.

    templates are set up as packages, so it is easier to develop and share them. the packages work very much like they do in the last release of Digitalus CMS, but they are much more tightly integrated with ZF.