LDS PHP Framework
Posted: Fri Apr 09, 2010 6:45 pm
This is in reference to https://tech.lds.org/wiki/LDS_PHP_Framework
Is this framework going to be/is it being made from scratch? I would like to see the use of something that is already being actively developed so that the church doesn't have to maintain quite so much.
One possible project that could save some effort is flow3. (See http://flow3.typo3.org/ ) It's an Open Source PHP MVC Framework upon which you can build just about anything. According to http://flow3.typo3.org/about/comparison/ it is, or will quickly become, very similar in feature set to SPRING, which I believe the church uses in it's Java stack.
As this is designed for enterprise application some features, like security reviews/updates, making sure extensions/packages are compatible, and enterprise user control, are high priority and included from the start. There's even an Eclipse Framework to help with creating new extensions for it. (See http://www.dev3.org/ )
If we used that, then the only thing that would need to be maintained would be a package (or set of packages) that helps it interface with other church systems (eg LDSAccount integration, and packages for interfacing with other APIs)
Another good php framework for smaller applications is RADICORE: http://www.radicore.org/
What else is being considered? What has already been done? Am I completely missing the point for this framework?
Thanks,
Jacob
Is this framework going to be/is it being made from scratch? I would like to see the use of something that is already being actively developed so that the church doesn't have to maintain quite so much.
One possible project that could save some effort is flow3. (See http://flow3.typo3.org/ ) It's an Open Source PHP MVC Framework upon which you can build just about anything. According to http://flow3.typo3.org/about/comparison/ it is, or will quickly become, very similar in feature set to SPRING, which I believe the church uses in it's Java stack.
As this is designed for enterprise application some features, like security reviews/updates, making sure extensions/packages are compatible, and enterprise user control, are high priority and included from the start. There's even an Eclipse Framework to help with creating new extensions for it. (See http://www.dev3.org/ )
If we used that, then the only thing that would need to be maintained would be a package (or set of packages) that helps it interface with other church systems (eg LDSAccount integration, and packages for interfacing with other APIs)
Another good php framework for smaller applications is RADICORE: http://www.radicore.org/
What else is being considered? What has already been done? Am I completely missing the point for this framework?
Thanks,
Jacob