What is Reddit's opinion of
FuelPHP?
From 3.5 billion Reddit comments
➔ FuelPHP website
By popularity on Reddit, this Service is:
19 reviews of this app found across Reddit:
Codeigniter has far wider community and great documentation.
Although it seems rather ~~friezed~~ frozen in time. Lately I've been using http://fuelphp.com the community is also great and growing, irc channel is very welcoming and helpful the documentation is good.
Actually it's not, PHP5.3 has namespaces it just has some downsides which made us decide to use a mixture of both namespaces and underscored classnames. It's explained on our blog if you're interested: http://fuelphp.com/blog/2011/04/classnames-autoloading-namespaces
What are the differences between FuelPHP and, say, Kohana? Also I'd love for a non-5.3 version, since I never use closures/namespaces. Still got some 5.2's hanging around.
edit: I do see things like Migrations, Tasks, and that neat Oil doo-dad. Anything that would make me go, "Oh man, I have to switch!"?
Fuel uses a front controller, by default it is in the "public" directory - so you need to copy the /home/folder/example.com directory and look for an index.php in either /home/folder/example.com/public or maybe another directory used as an entry point. You should also make sure only this one directory is accessible from the outside, otherwise you will have security issues.
For "nice" URLs you will need to configure your web server to call this index.php for all files not found in this public directory, for example in Nginx this would be something like
try_files $uri index.php;
Or replace index.php with @php if you have a PHP location to call scripts. Only index.php needs to be executed by PHP.
The Fuel documentation is also available on http://fuelphp.com if you need to find out more details.
Maybe try searching around for an open source project, to see if there is anything that fits with your requirements. I don't know of anything off the top of my head, but it doesn't seem like a difficult project to write from scratch. Could possible make it in an hour with FuelPHP or CodeIgnitor, and you would learn a great deal more by doing it yourself.
As people have said, FuelPHP is a very new framework so there is not a huge amount of information available, but it does exist.
I have recorded two screencasts explaining how Oil (the command line utility work) and this will generate scaffolding for you.
Introduction and Scaffolding: http://blip.tv/file/4849032 Migrations, Tasks and Console: http://blip.tv/file/4885416
From that you can pick things apart or check out the documentation:
Admittedly there are a few bits missing from docs, but they are the bits we have been finalising for RC in a few days. Why waste time documenting features that will change in a few days, if you could spend that time changing the features and hitting a release deadline?
The RC release will coniside with our whole website redesign which will have a great new FuelTV section, so these videos (and more) will all be easy to find. Think RailsCasts. :)
FuelPHP is approaching final release and is really stable. http://fuelphp.com
For the sake of your projects please don't make your own. A lot of people on here advocate that but if you are working with others or have to hand the project off at any point having a standard framework is much better then one you created yourself. Also with a open source framework there are hundreds of people working on it and fixing bugs, bugs that you may never notice that could leave gaping holes in your security.
I don't think that FuelPHP started off as a Kohana clone ... from their website they say they took some pieces from Kohana, but that most of the code is unique.
While FuelPHP is being authored by some big names (Phil Sturgeon) it's still very new. On the plus side, the documentation seems to already be better than Kohana's, with descriptions on what the classes actually do, although some don't seem to be fully fleshed out yet.
It really depends on the specifics but it sounds like you might be describing the presenter pattern, also know as model-view and viewmodel.
FuelPHP is the only framework I know that uses them, but I have only used a few of the major frameworks, I'm sure plenty exist. http://fuelphp.com/docs/general/presenters.html
Is this what you're looking for?
I've seen a lot of people recommending old frameworks and that's ok but I recommend you simply dive in at the deep end and start with a newer object oriented framework such as Fuel.
It sounds like you're done with PHP, but if you ever find yourself in a situation where you're forced to develop in it, you might be happier if you use a framework that requires PHP 5.3 like Fuel. It's still super new, but the fact that it requires PHP 5.3 and the fact that they say "it was born out of the frustrations people have with the current available frameworks" and "the team has decades of PHP experience between them and have all been involved with Open-Source projects" makes it seem promising.
The only language besides PHP that I've used for web development is Lasso. I've been very interested in learning Python / Django, but haven't had time to do it. How did you get into Rails? Is it way, way different than PHP?
Don't listen to these guys. MVC is an ever changing model. It evolves, in many directions. I wouldn't delete it or scratch it out. Keep it around as a learning tool. However if you want your students to come away with something marketable, often times, just learning the language is the first battle, but being taught off of someone's custom framework will hurt them in the end because they will only be familiar with your framework, just like in school students should be working extensively with libraries such as boost so that later on if they get a job they will be able to actually write some real software instead of only knowing how to use the "learning Crutches" they were taught to use. If you want something simple, you should give PHP Fuel a shot, i think that it's one of the easiest of the frameworks I've looked into to learn off the bat. CI is very Old Style MVC and people are moving away from it in droves because it doesn't have support for more modern php 5.3 standards. http://fuelphp.com/
Well, IMHO is not. Personally, if you want to generate something, then you are doing it wrong. Better way is to use inheritance - you reuse more code and situation when you have some global changes on hundred files and you have to use sed won't occur as often.
In example: http://fuelphp.com/docs/packages/oil/generate.html you generate some actions with titles and setting views. But you can do that in abstract controller where you assigned your view by the controller and action name, and create title same way (btw - you will have easier task with this to also generate breadcrumbs). So for me this is not an advantage, because you don't have to use that, writing some template controller by your own (with using inheritance properly) won't take you much time - it's even harmful because is tempting just to generate another controller instead of think more and create flexible abstract controller, resulting in the long way of much code almost copied from each other.
Seriously, I absolutely love this framework. You can have a rest controller and there is an ORM Package
Fuel is very young (1.0 final is around the corner.. I think). As a result there is not a wealth of documentation or examples for it. There are the official docs: http://fuelphp.com/docs/ . For a (simple) example application you can look at this: https://github.com/abdelm/stationwagon . Fuel is certainly a hip new framework... but it isn't going to have the level of documentation/examples of things like CakePHP or CodeIgniter.
This project looks really interesting, the first new framework I've seen which has looked fresh.
I saw in the documentation
>Closures - 5.3 adds anonymous functions (a.k.a. Closures).
Closures and anonymous are actually not the same thing, this is a common misconception. In most languages closures do use anonymous functions, but not all anonymous functions are closures.