Anonymous | Login | Signup for a new account | 2024-03-28 17:17 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Vertical ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000850 | [In-Portal CMS] Optimization | task | N/A | 2010-09-01 02:31 | 2011-09-26 05:08 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | open | ||
Status | needs work | ||||
Summary | 0000850: Automatic class name retrieving based on it's filename | ||||
Description |
I propose we auto-guess php class name based on filename, where that class is stored. For example "my_super_helper.php" file will contain "MySuperHelper" class and nothing other. There are several benefits of this: * no need to specify class name in unit config file (only class filename remains); * developer will be forced to properly name class file to connect it's class to the system. We'll make some presumptions, that: * "eh" will transform to "EventHandler" * "tp" will transform to "TagProcessor" * all classes from "core" module, that are not event handler/tag processor should have "k" in front of their name Before: * UsersEventHandler, users_event_handler.php * UserGroupsEventHandler, user_groups_eh.php * kThemesHelper, themes_helper.php * CustomFieldsTagProcessor, custom_fields_tag_processor.php After: * UserEventHandler, user_eh.php * UserGroupEventHandler, user_group_eh.php * kThemeHelper, theme_helper.php * CustomFieldTagProcessor, custom_field_tp.php |
||||
Additional Information | This large change, since we need to rename most of our classes/files to keep everything working. That's why I propose this change to be made as part of 5.2.0 release. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |