Solonik77 / digitalus-cms

Automatically exported from code.google.com/p/digitalus-cms
0 stars 0 forks source link

Enhancement: put application/ configs, data, and models into public #140

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

The ZF "application" dir is meant for ZF modules. admin and public modules
qualify for their own directories, but "configs", "data", and "models" are
no modules, so they should be put into "public".

Extending Digitalus with custom ZF modules is becoming an inconsistent file
system mess. It would be better to clean up the application dir to reflect
really ZF-modular structure:

application
+-- module1
    +-- controller(s)
    +-- config(s)
    +-- data
    +-- model(s)
    +-- view(s)
        +-- filters 
        +-- helpers
        +-- layouts
        +-- scripts
+-- module2
.
.
.
+-- moduleN

Original issue reported on code.google.com by kwut...@web.de on 2 Mar 2010 at 12:32

GoogleCodeExporter commented 8 years ago

Original comment by lowtower1974@gmail.com on 3 Mar 2010 at 8:10

GoogleCodeExporter commented 8 years ago
I think they rather belong to the "admin" module - started work on it

Thanks for the suggestion.

Cheers,
LT.

Original comment by lowtower1974@gmail.com on 7 Mar 2010 at 5:16

GoogleCodeExporter commented 8 years ago

Original comment by lowtower1974@gmail.com on 6 Apr 2010 at 9:31