11–20 of 46 posts
ONE YEAR since the last commit, seriously? Where are the tests? Composer? Next.
Also, FuelPHP is a Rails inspired PHP Framework.
https://github.com/fuel/fuel/commits/1.5/master
Although this is the 1.5 branch, the other branches are also similarly inactive (it appears to have ended about a month ago).
This is a work in progress that I think could turn into a better CakePHP, but also has the potential to become something more similar to Sinatra and have the relationship to CakePHP that Sinatra has to Rails. Would love to get feedback on these two routes of development.
Your priorities should be tests, and documentation, before anything else.
I think that your efforts might be better spent on improving CakePHP; the developers have no particular concern for backwards compatibility in the upcoming major version (3.0). I would be interested to discuss all of your ideas related to this, please contact me at tenebrousedge @ gmail
Also, FuelPHP is a Rails inspired PHP Framework.
Judging by the commit history[1] it seems FuelPHP isn't being actively developed anymore. https://github.com/fuel/fuel/commits/1.5/master Although this is the 1.5 branch, the other branches are also similarly inactive (it appears to have ended about a month ago).
i.e.
public static function show_GET($params=null) {
self::render('show',array("layout" => "default"));
}
public static function index_POST($params=null) {
self::redirect('/auction/show');
}
in routes file:
get 'photos/show'
class PhotosController Out of curiosity, but is there a design-reason why the controller names are tied (by naming convention) to HTTP convention? i.e. public static function show_GET($params=null) { self::render('show',array("layout" => "default")); } public static function index_POST($params=null) { self::redirect('/auction/show'); } As opposed to how Rails does it (controllers are defined in their own file and associated with a HTTP pro…
This is a work in progress that I think could turn into a better CakePHP, but also has the potential to become something more similar to Sinatra and have the relationship to CakePHP that Sinatra has to Rails. Would love to get feedback on these two routes of development.
I am from time to time involved in the development of the CakePHP framework, at least often enough to have strong opinions on specific weak parts of the framework. I think your project might have potential, but the lack of tests and composer support is a serious flaw. Your priorities should be tests, and documentation, before anything else. I think that your efforts might be better spent on improving CakePHP; the dev…