| Anonymous | Login | Signup for a new account | 2024-05-03 08:12 CDT | |
| Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
| View Revisions: Issue #268 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0000268: Code Cleanup in 5.2.x branch | ||
| Revision | 2012-05-29 06:15:33 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process (maybe by creating kiUrlProcessor interface, that will be implemented in PlainUrlProcessor and RewriteUrlProcessor classes). 2. Temp Handler class optimization: - implement class using Collection pattern (like tests are collected in phpUnit) and create Clone, Delete, etc. methods for the class. - this way operations will be single-item based, not table-based as right now. - This of course will result separate sqls for subitem quering based on individual parent, but that's small price to pay to have correctly organized class hierarchy 3. 0001224 - Email event usage refactoring (part 1) - create kEmail class with following public methods: -- findEvent($name, $type) -- setParams($params) -- send() - make $this->sender refer to kEmailSendingHelper class instance for easy access across all methods - move existing code from EmailEventsEventHandler into new kEmail class - replace OnEmailEvent event sending with new kEmail class usage 4. Email event refactoring (part 2) - replace tons of "switch by RecipientType (to, cc, bcc) field" into polymorphism |
||
| Revision | 2012-03-14 12:12:05 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process (maybe by creating kiUrlProcessor interface, that will be implemented in PlainUrlProcessor and RewriteUrlProcessor classes). 2. Temp Handler class optimization: - implement class using Collection pattern (like tests are collected in phpUnit) and create Clone, Delete, etc. methods for the class. - this way operations will be single-item based, not table-based as right now. - This of course will result separate sqls for subitem quering based on individual parent, but that's small price to pay to have correctly organized class hierarchy 3. 0001224 - Email event usage refactoring - create kEmail class with following public methods: -- findEvent($name, $type) -- setParams($params) -- send() - make $this->sender refer to kEmailSendingHelper class instance for easy access across all methods - move existing code from EmailEventsEventHandler into new kEmail class - replace OnEmailEvent event sending with new kEmail class usage |
||
| Revision | 2012-03-13 08:09:47 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process (maybe by creating kiUrlProcessor interface, that will be implemented in PlainUrlProcessor and RewriteUrlProcessor classes). 2. Temp Handler class optimization: - implement class using Collection pattern (like tests are collected in phpUnit) and create Clone, Delete, etc. methods for the class. - this way operations will be single-item based, not table-based as right now. - This of course will result separate sqls for subitem quering based on individual parent, but that's small price to pay to have correctly organized class hierarchy 3. Email event usage refactoring - create kEmail class with following public methods: -- findEvent($name, $type) -- setParams($params) -- send() - make $this->sender refer to kEmailSendingHelper class instance for easy access across all methods - move existing code from EmailEventsEventHandler into new kEmail class - replace OnEmailEvent event sending with new kEmail class usage |
||
| Revision | 2011-12-23 11:35:14 by Dmitry | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process (maybe by creating kiUrlProcessor interface, that will be implemented in PlainUrlProcessor and RewriteUrlProcessor classes). 2. Temp Handler class optimization: - implement class using Collection pattern (like tests are collected in phpUnit) and create Clone, Delete, etc. methods for the class. - this way operations will be single-item based, not table-based as right now. - This of course will result separate sqls for subitem quering based on individual parent, but that's small price to pay to have correctly organized class hierarchy |
||
| Revision | 2011-10-24 06:52:13 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - also record $_SERVER['HTTP_HOST'] to store host, where problem was found in multi-user development environment - also record current user id (guest or not) and it's session data - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis 2. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process (maybe by creating kiUrlProcessor interface, that will be implemented in PlainUrlProcessor and RewriteUrlProcessor classes). 3. Somehow divide In-Portal into layers, that can be easily turned on/off. 4. Maybe modularize core itself, e.g. "form submissions", "permission system", "various logs", "visits", "site domains". 5. Maybe some parts (within the main module) can be downloaded separately. 6. Temp Handler class optimization: - implement class using Collection pattern (like tests are collected in phpUnit) and create Clone, Delete, etc. methods for the class. - this way operations will be single-item based, not table-based as right now. - This of course will result separate sqls for subitem quering based on individual parent, but that's small price to pay to have correctly organized class hierarchy |
||
| Revision | 2011-07-07 09:24:21 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - also record $_SERVER['HTTP_HOST'] to store host, where problem was found in multi-user development environment - also record current user id (guest or not) and it's session data - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis 2. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process. 3. Somehow divide In-Portal into layers, that can be easily turned on/off. 4. Maybe modularize core itself, e.g. "form submissions", "permission system", "various logs", "visits", "site domains". 5. Maybe some parts (within the main module) can be downloaded separately. 6. Temp Handler class optimization: - implement class using Collection pattern (like tests are collected in phpUnit) and create Clone, Delete, etc. methods for the class. - this way operations will be single-item based, not table-based as right now. - This of course will result separate sqls for subitem quering based on individual parent, but that's small price to pay to have correctly organized class hierarchy |
||
| Revision | 2011-02-07 01:58:45 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - also record $_SERVER['HTTP_HOST'] to store host, where problem was found in multi-user development environment - also record current user id (guest or not) and it's session data - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis 2. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process. 3. Somehow divide In-Portal into layers, that can be easily turned on/off. 4. Maybe modularize core itself, e.g. "form submissions", "permission system", "various logs", "visits", "site domains". 5. Maybe some parts (within the main module) can be downloaded separately. |
||
| Revision | 2011-02-01 03:47:36 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - also record $_SERVER['HTTP_HOST'] to store host, where problem was found in multi-user development environment - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis 2. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process. 3. Somehow divide In-Portal into layers, that can be easily turned on/off. 4. Maybe modularize core itself, e.g. "form submissions", "permission system", "various logs", "visits", "site domains". 5. Maybe some parts (within the main module) can be downloaded separately. |
||
| Revision | 2011-01-31 02:20:13 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - also record $_SERVER['HTTP_HOST'] to store host, where problem was found in multi-user development environment - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis 2. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process. 3. Make site domain functionality unpluggable and easy replaceable. |
||
| Revision | 2011-01-24 09:55:08 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis 2. kModRewriteHelper and kUrlManager both works with urls and get some data from kApplication class too. Need to unify url build/parse process. 3. Make site domain functionality unpluggable and easy replaceable. |
||
| Revision | 2011-01-24 02:17:58 by alex | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. --------------- 1. create EventLog class, that would: - handle sql error processing - handle php error processing - handle exception processing - ability to handle user defined events - put data to silent log, when not in debug mode - optionally use database to store all errors, that are happening - report errors to in-portal website for analysis |
||
| Revision | 2010-05-19 15:58:17 by Dmitry | ||
| Description | This an ongoing task for Code cleanup in the whole system in 5.2.x branch. | ||
| Revision | 2009-10-06 14:29:38 by Dmitry | ||
| Description | This an ongoing task for Code cleanup in the whole system. | ||
| Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic
In-Portal Open Source CMS |
Copyright © 2000 - 2009 MantisBT Group
 |