Timeline for Module development: how to follow OOP best practices
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2012 at 20:59 | comment | added | Filippo Salza | Hi Justin! Yeah i prefer create new objects. You are confirm my approach. I come from Java and I feel CodeIgniter a bit 'tight, I want to design my objects. | |
| Dec 4, 2012 at 15:22 | comment | added | Justin Kimbrell | I create "Libraries" a lot, which are now becoming PSR-2 compliance so I can write code that is framework agnostic. Erik's suggestions are spot-on and pretty much the exact same thing I do. I am increasingly creating new object vs. utilizing the CI singleton to get even more OOP in the mix. | |
| Dec 4, 2012 at 12:57 | comment | added | Erik Reagan |
@FilippoSalza in that case you have two options. 1) Create a "CodeIgniter style" library and load it in your module with CI's loader or 2) Write your class to suite your needs across the other platforms you need it portable for, then just use PHP's include() and instantiate the library/class in your Module as needed. Does that help?
|
|
| Dec 4, 2012 at 12:52 | comment | added | Filippo Salza | Yes, I want portable logic, so libraries/classes. | |
| Dec 4, 2012 at 12:49 | history | answered | Erik Reagan | CC BY-SA 3.0 |