The fact that there might be great reasons for creating a more advanced Parser in CI is not the point I am trying to show you. The fact is that the EE Template parser is a very specialized piece of code that is written for exactly our purposes, and it would not abstract well. It would simply be easier to write a new Parser class in CI than try to bring the EE Template parser over. Not everything is a one to one transference, so it will not be possible for us to give you all of your dream code.
[quote author=“maadmac”]I’ve noticed a barely-concealed disdain in the CI fora among developers toward EE that I can’t fully understand.
Well, I think there’s just going to be some natural conflict. Open-source (everything free as in beer) vs a commercial package and developer/programmers vs developer/designers. We’ll just have to learn to deal with that and try to get along :-)
[quote author=“maadmac”]what’s the best use of your time?
I’d rephrase - what’s best for the client.
——-
I must admit a bias though as I’ve been burnt more times by custom development and open-source than anything commercial. I have had a better experience with custom add-ons to commercial packages. Hopefully that’s where this uniting will be useful for us all.
I’ve noticed a barely-concealed disdain in the CI fora among developers toward EE that I can’t fully understand.
Seriously? I haven’t noticed it at all and i’ve been on the CI forum for years.
Personally i think it’s fantastic news and gives me even more reason to get stuck into EE.
I think people like being able to make their own systems instead of having to learn other peoples, however, for the right client i’m sure no-one would think twice about going for EE. Even more so with this cracking news about the marriage of CI and EE.
I’ve noticed a barely-concealed disdain in the CI fora among developers toward EE that I can’t fully understand.
Seriously? I haven’t noticed it at all and i’ve been on the CI forum for years.
Personally i think it’s fantastic news and gives me even more reason to get stuck into EE.
I think people like being able to make their own systems instead of having to learn other peoples, however, for the right client i’m sure no-one would think twice about going for EE. Even more so with this cracking news about the marriage of CI and EE.
I haven’t noticed this either. ExpressionEngine is often recommended on the CodeIgniter forums to those that are asking about a packaged CMS. You are talking about a community that has been drawn to the framework rather than a CMS though, so of course their first choice is likely to be custom coded solutions.
With some sort of option to integrate ExpressionEngine into the CodeIgniter framework, assuming there is not a big loss of flexibility will only provide more options for everyone though.
I’ve typically drawn a very dark line between which client sites I develop in CI and which ones in EE. It’s all about what they want to accomplish with their site. There’s no checklist, necessarily, but I just “know” when one will work better than the other.
Now that EE will be running on CI, it will be really nice to give my clients the power of EE and the ease of writing their custom CI features without having to decide between the two. It’s a no-brainer to add the extra $250 to the development cost; especially considering the power it brings.
I’m so stoked this functionality has finally arrived.
I must admit that I thought about jumping ship to using the Zend Framework so many times and the main reason why I haven’t is the thought of having a great easy to use framework with a kick ass bolt-on CMS and hooray, that day is fast approaching.
A big thank you to all involved and I wouldn’t be suprised if a lot (I mean a LOT) more people now start using Code Igniter because of this!
I can just see all of this stuff getting integrated also.
Like create a weblog and boom it’s in the grid.
jQuery is kind of to javascript what EE is to php, you don’t have to have full understanding to plug things in.
But this is the Ci crowd here, the PHP geeks are in the house.
There are so many jQuery plugins coming out it’s hard to keep up.
I would love just a little more exposition on the JQuery/CI integration and just how easy it will be to use our framework of choice. Personally, I’ve cottoned to scriptaculous, but I can make the move to JQuery if need be.
Dumb question, and maybe one better asked on the CI site, but do you need to know php to use this framework? Would it be better to start with php or CI (assuming I know neither)? I have a modicum of mysql experience if that matters at all.
Watching the videos on codeigniter.com and Derek Allards videos on http://video.derekallard.com really helped me in my php abilities. Between those and some experiments, I was able to make a good, usable website for a friend in Code Igniter. The community is as good as EE, and there is a lot of cross over. People over there are more than willing to help you out. It will really help you develop some serious PHP chops, which will make you an even better EE developer!!!!
Having used EE and CI a while, I am a little confused as to how I can “implement” EE into my CodeIgniter applications. For example, I have recently developed a site which has user management and custom page content… to do so I used the CI user libraries and my own custom CMS code for the pages. Lets say one day I think “Hey, I think this site could use a forum, I’ll install EE and install the forum module” would it seamlessly integrate or would I have to recode / restructure my application in order to incorporate EE?
Whilst this news is great, I can’t help but feel like anything I code at the moment for future projects is going to redundant in a few months when V2 comes out. Especially if I coded my own CI forum system only to be able to pop EE in there to do all the hard work for me :(
The Discussion Forum module interfaces with ExpressionEngine’s Member module, so it would not be a drop-in and switch-on using a custom user database. That said, ExpressionEngine has a very simple XML-based member import utility that would make it easy to transfer your existing user data into EE’s Member module. After that, the level of difficulty for further integration would depend on how much code you’d have to modify to work with EE’s member schema vs. your home grown version. It could be dead simple, but depending on the project it could be a somewhat significant migratory task.
The Discussion Forum module interfaces with ExpressionEngine’s Member module, so it would not be a drop-in and switch-on using a custom user database. That said, ExpressionEngine has a very simple XML-based member import utility that would make it easy to transfer your existing user data into EE’s Member module. After that, the level of difficulty for further integration would depend on how much code you’d have to modify to work with EE’s member schema vs. your home grown version. It could be dead simple, but depending on the project it could be a somewhat significant migratory task.
Thanks for the quick reply. I suppose it’s better to hold out for V2 so that I can create a system which integrates nicely with EE’s member module. Is user management something that will be structured specifically with EE in mind for the new version?
