Bermi Ferrer kept his promise, and even if a few were skeptic on the pre-announced features of his upcoming Akelos framework, last week he sent me a “development preview” and a few days ago he opened the development SVN repository to the public:
Go, get it: it’s worthwhile (see below).
“[…] The Akelos Framework is an open-source port of Ruby on Rails to the PHP programming language.
The main goal of the Akelos Framework is to help programmers to build multilingual database-backed web applications according to the Model-View-Control pattern. It lets you write less code by favoring conventions over configuration.”
At the Akelos Framework Features page you can find detailed information about what has been already implemented into the framework.
I think it says it all, well almost. Some people will undoubtedly be disgusted by yet-another-hopeless-Rails-clone: not again! I hear them crying…
Well, yeah, I think this – to be honest – should be the last attempt someone makes to port Rails to PHP or at least port some features and the overall philosophy, like CakePHP did: there are honestly too many for one single language. Look at Python, Django seems to be the only “Rails-inspired” framework available and everyone is happy with it, while as a general rule PHP folks are never happy with what they already got.
Bermi is undoubtedly one of them, and that’s the reason he decided to code his very own Rails-inspired framework for PHP, which is, to date, the most remarkable of the ones I left out (it wasn’t available at the time) in my article.
Confirmed Features & Contents
So well, although I didn’t really have a proper chance to play with Akelos I can certainly herald some of its – verified, this time – features.
For one, it’s huge. Take Cake, add every excellent, useful third party library or class you can possibly thing of and you’ll get Akelos. No kidding. The unzipped source of the whole framework is a massive 16MB, 8.5 of which constitute the
vendors folder. What’s in it? Well, all this:
- Excel (reader library)
- Hyper Estraier full-text search system
- Inutio XML-RPC Library
- Many PEAR packages
- A Simple PHP YAML Class
- various Scriptaculous packages
- FileUploader (by the author, using prototype)
Good, well, kind of: that’s just what others did, but it’s worth noting that it’s all there and – apparently – integrated with the framework, hopefully not too tightly. But people are fussy, and do not get excited easily anymore, long gone are the early days of Rails, when the whole Internet shake at hearing about code generators… Aye, there are in Akelos as well, of course!
Coming to the more juicy stuff, lo’ and behold, ye contents of /lib folder (with comments):
- AkActionController (controller)
- AkActionView (view)
- AkActionWebservice (Web services)
- AkActiveRecord (model)
- AkAdodbCache (content caching)
- AkCharset (utf8 support, includes all mappings)
- AkConfig (load config settings)
- AkConverters (conversions!)
- DBDesigner > AkelosDatabaseDesign
- Excel > Array (bi-dimensional)
- Excel > CSV
- HTML > RTF
- HTML > Text
- Word > Unicode
- PDF > Text
- Xdoc > Text
- AkHeaders (HTTP headers, redirections)
- AkImages (Image operations, resizing)
- AkLocalize (Localization, countries and timezones)
Well, it’s all there, at any rate. The best way to know if it all works, and how it works, is simply to try it out: www.akelos.org.
As I said earlier, Akelos looks like CakePHP on steroids: agreed, the Cake philosophy of “no we-may-use-it code in the trunk” has been completely (and intentionally) ignored, but this is our chance to peek at what CakePHP could have become if such philosophy didn’t become a lifestyle for the Cake Dev Team.
Akelos code is Rails-inspired, so yes, it’s very similar to Cake, although with some rough edges and some re-used parts, but it’s the work of ONE person with no community support (yet), don’t forget. Remarkable.
And he needs co-developers, by the looks of it, so there you are then: there’s your chance!
My personal opinion about it? Well, I think Akelos can learn from CakePHP and vice-versa: a merge? Well, at least it would reduce the number of Rails-inspired framework for PHP and possibly meet the needs of more people: those who want just the essentials, as a framework, and those who like to be virtually almighty and be able to do anything, if they wanted to.
Two flavours of the same framework? CakePHP and cAkePHP (note the case)? Bah, let’s stop raving now, shall we?