to Marco: Yes, it will be Open Source. By security reasons I did not 
publish current repo as It can contain private data. Soon, I will put in 
github or in bitbucket new source tree from scratch.

I see progress of this project like box application which solve some 
ordinary task for user like management of menu and articles (pages), 
user, module, global configuration management, etc. And CMS must accept 
zf2 modules and it's own modules. So this modules may be public or 
private (for commercial usage).
Libra modules differ from zf2 by having administration aspect (and that 
there will be else).

Now I am thinking of file structure:
I want put in base one of several models:

1.  It will be have whole separated admin(backend) and front end (like 
in current version). So it will be such structure
First structure

Cons:
     We should get 'back end' Module path to include it in 'front end' 
classmap for utilizing.
     It use same NS.
Pros:
     It use same NS.
     Easy install, separated from front end.


2. We put it in front end admin login by including in Form and 
Controller folder additional Admin folder and NameSpace.
second structure.

Pros:
     backend accessible by magic __DIR__.
     have different NS
     Put all in one place.
Cons:
     Must divide configuration files.
     Need check for Admin folder to include before front end class.


3. Same as 2 but add Prefix Admin in src for admin sources:
Third structure

4. Same as 3 but add Admin to whole module, so we will have and 
separated view.

5. Module resolve itself how process by 'case' operator(if admin ..., 
else if user .....)  inside module  (I guess it will be worse).

6. Your suggestion.

In 1-4 structure administration available  by url /admin/ (we add 
directory public/admin).

Also as you see at images, I divide zf2 modules by what it do:
Component  -  do current action like showing article content, user 
profile, list of users. Usually take centre of page.
Module         -  output addition info to component at page like menu, 
news feed, login form. Also can be named as Widget.
Hook            -  only attach events to existing component/module.


I'll be glad to know opinion of others.
May be someone met with any of that model and you can point on the 
biggest problem in any of it.
Thanks.


--
View this message in context: 
http://zend-framework-community.634137.n4.nabble.com/Announce-Libra-CMS-based-at-ZF2-tp4576406p4579911.html
Sent from the Zend Framework mailing list archive at Nabble.com.

Reply via email to