Posted on: 2015/5/19 5:15
Re: The future of XOOPS?
I would suggest any modules that do get rewritten to follow a strict MVC model so it makes things much easier to modify down the road.
Rodney, MVC seems to be a little bit outdated, and there are some new and cool variations of it, like the ADR (Action-Domain-Responder)
An interesting article about "Alternatives to MVC
" was published by Anthony Ferrara, as a follow-up to his article "A Beginner's Guide To MVC For The Web
", and Paul Jones (author of ADR) responded here
There is also an interesting comment about ADR by Akihito Koriyama
, who himself is working on yet another framework called BEAR Sunday
Please note that Richard has already experimented with ADR and there were several aspect that the he liked about it.
However, the main key will be to bring all the pieces in sync, especially the Presentation Layer
that Eduardo is porting to XOOPS 2.6.0 from his "Common Utilities" and the work that Richard was doing on Core, incl. his various experiments with XMF, MVC, and finally ADR.
The opportunity for XOOPS is that because we won't have any "legacy" code written using the classical MVC, we can choose and take advantage of some of the newer ideas, and have XOOPS again on the cutting edge of development I would like to credit here both Richard and Eduardo for their willingness to look at new ideas from others, test them, and then select the best and implement them in XOOPS! The "Not invented here" syndrome is gone from XOOPS!