Posted on: 2010/2/1 21:38
AMS 3.0 combine with News 1.64. Give your opinion.
After few days thinking... I think its quite make sense to combine AMS 3.0 with News 1.64. Since AMS originally fork from News 1.2, 70% of the code actually identical.
However, AMS already evolve so much to the different focus area... be a article management, with some big changes like spotlight, versioning, audience that may take a while before it could be fully integrated.
Here, I want to ask to everyone...
1) Should it combined, or let AMS evolve as it is and only adding features that needed/requested by article management user. So it will not bloat up with features that not needed.
2) Use AMS as a based, and add in News code. Folder will be /modules/AMS, prefix will be ams_
3) Use News as a based, and add in AMS code. Folder will be /modules/news and prefix will be news_
4) Use News as a based, and add in AMS code. Folder will be /modules/ams_news and prefix will be amsnews_
As a developer, I'll like to choose (3) since news have a few features that AMS didn't have, but I'm not familiar with the coding yet, but I already familiar with AMS coding, so port it might be little bit easier. No renamed need, so I can truly focus on porting AMS features. However, it may clash with other News 1.64 continuation/development that pursue by XOOPS and ICMS core developer. (4) will need all prefix to be renamed (including function name) that will caused me to touch every single file and do tons of testing to make sure none of them broken. It also complicate the process merging the amsnews coding with other news continuation that i mention before (icms & XOOPS core) since diff will highlight all changes including function name.
I let XOOPS community to voice your opinion, and I'll consider it.- NovaSmart XOOPS module development team