| Re: XoopsObject and design patterns? |
| by trabis on 2009/7/10 18:59:02 Maybe is more like the template pattern! Maybe facade? Hum, decorators, iterators and composites are breathtaking patterns. Criteria class is my second favorite one :) But why is object.php in kernel folder? Why is xoopsblock.php on class? Am I supposed to use commentrenderer.php on my modules? What belongs to XOOPS and where is my API? Why core have special attention over modules? Why can't I extend other modules preferences like core/comments and core/notifications do? |
| Re: XoopsObject and design patterns? |
| by bumciach on 2009/6/14 11:03:57 Let's be serious  Thanks for the replies and links. I know that XOOPS was established in little other purpose than an extensive framework like Zend or CakePHP. So naturally there is no such comprehensive solutions. Design Patterns can help you better understand XOOPS ... or XOOPS can help get a better understanding of design patterns. I learn both. I would like to more fully and more consciously use the XOOPS API in my projects. |
| Re: XoopsObject and design patterns? |
| by Mamba on 2009/6/12 14:58:42 Quote: discovering patterns in existing code and then arguing why this piece of code is more pattern x then pattern y Very funny! 
|
| Re: XoopsObject and design patterns? |
| by ghia on 2009/6/12 7:53:13 One of the exciting passtimes of Design patterns:  discovering patterns in existing code and then arguing why this piece of code is more pattern x then pattern y.
|
| Re: XoopsObject and design patterns? |
| by hervet on 2009/6/12 7:38:11 It's a little bit of the "active record" design pattern. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|