cms

cms copied to clipboard

I think since version 2.0 we need to move away from these long and ugly class names in the direction of the namespaces.

I really liked the structure of the Zend classes.

• One and the same directory contains the interface, abstract classes (if necessary), writers, base class... — in short all family of component
• Short and clear class names, for example Install instead Controller_Install_Install

For exaple:

Application/
Assets/
Licenses/
Modules/
       |_____Captcha/
       |_____Codebench/
       |_____...
       |_____Gleez/
       |         |_____ACL/
       |         |_____Assets/
       |         |_____...
       |         |_____Blog/
       |         |         |_____Abstract.php
       |         |         |_____Class.php
       |         |         |_____Controller.php
       |         |         |_____Exception.php
       |         |         |_____Interfase.php
       |         |         |_____Helper.php
       |         |         |_____Reader.php
       |         |         |_____Writer.php
       |         |         |_____...
       |         |         |_____Assets/
       |         |         |_____Models/
       |         |         |_____Views/
       |         |_____Widget/
       |_____User/
       |_____...
Themes/
...
index.php

It makes sense to consider supporting PSR-1/2/3 standart.

@sandeepone What do you think about this?

I like the idea basically, but designing such a structure is not easy in terms of development and performance wise. We need a strong roadmap for that.

Gleez Autoloader is done

Gleez Database is done

#553 #723 Linking other issues

Related issue #729

We need develop branch e.g. gleez-2.0.0 AND for current purposes which did not disturb 1.x API some devlelop branch. Or develop-1 for merging into gleez-2.0.0 and develop-2 for merging into current master