Think about it, Rick is about to answer once and for all his view of how a CMS should be built on CodeIgniter. Lots of people are wondering what EE 2.0 will ultimately look like. Lots of developers probably have a pretty good idea on the answer. I think we should try to figure this out in the form of a contest before details come out. Who wants to play?
Edit: I mean, if YOU would build EE on CodeIgniter, how would you do it? How would you build the templating system? How would the control panel work with an MVC framework? That sort of stuff.
My bet… is that CI has been upgraded to build EE2 with.
CI will have a nice new shiny release that allows EE2 to do what it does with its modular structure etc.
There will probably be a new way of running other controller’s methods, allowing for ‘blocks’.
I think CI would need a bunch of new libraries and perhaps a structure change, but there are some basic ideas that will still be present. For instance, CI will still be an MVC framework.
I think EE 2.0 will be pushing CI to the max. You are going to see a shit-ton of custom libraries and non-CI code to actually make it all function.
EE 2’s primary purpose is to say, “Looky - we’re all one big family now.” No matter how much the CI framework is demolished to accomplish that goal.
After the release, CI will be worked on extensively to prepare a proper version of the framework to power EE. CodeIgniter 2.0 and EE 2.1 will be released at the same time, or nearly so, and will truly change the game of EllisLabs products.
You guys just broke all the rules. To add insult to injury, Sergeant Wales called the company “EllisLabs.” We all know how much Paul hates it when people do that.
EE 2’s primary purpose is to say, “Looky - we’re all one big family now.” No matter how much the CI framework is demolished to accomplish that goal.
I thought about that too. I hope this is not the case. If CI goes though big changes I hope it is still has the same qualities that make it the great framework it is today. I am sure it will be though.
If CI goes though big changes I hope it is still has the same qualities that make it the great framework it is today. I am sure it will be though.
I don’t think CI - as a framework - will be demolished for EE. What I mean is - when you look at the EE 2.0 code, you’ll be able to see CI sitting there, but there is going to be a ton of work done in the application directory to make it all actually work. Most of the true functionality will come from custom libraries and such to make EE work.
Then, after launch, EllisLab will sit back and say, “okay - let’s get a lot of this into CI.” Thus, will be the birth of CI 2.0 and the release of EE 2.1, based on the CI 2.0 code.
So you think they will overhaul the structure too? There are a ton of threads about the best way to handle view folders, making the views, libraries and models modular and other things. Will a module use a view, controller and model? Will the “model” part of MVC be ignored in EE?
How about templating? That is the most interesting to me. Will EE be able to improve performance with an MVC approach to templates? There was some talk about template handling in EE 2.0 but I will have to find the link.
