Anonymous | Login | Signup for a new account | 2024-04-19 06:34 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000441 | [In-Portal CMS] Optimization | feature request | always | 2009-12-07 10:35 | 2010-08-31 14:21 |
Reporter | alex | View Status | public | ||
Assigned To | |||||
Priority | normal | Resolution | open | ||
Status | active | ||||
Summary | 0000441: Converting "Unit Config" files from Arrays to Classes | ||||
Description |
Goal is to convert all unit configs from array to classes form. This will give us such immediate benefits: - all common unit config settings, that are copied from one unit config to another will be located in parent class (saves space); - all unit config setting names will be automatically suggested by Zend, and this will eliminate most of setting name typing errors; - we will have a list of all possible unit config settings with their description, purpose and usage examples. We should create base class for unit configs where all mentioned above. I think, that all unit configs (system and user-made) should be named the same way and need to use some prefix (along with suffix as usual), that will prevent them from appearing in class-name auto-complete dialogs at least user really wants them to be there. Unit config class name could be formed by coding standards using prefix-name, declared in this config. For example "ucUserConfig" (for prefix "user"), "ucAgentConfig" (for prefix "agent"), "ucCustomSection" (for prefix "custom-section") and so on. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |