mootools and Code Igniter

I promised Derek Allard that I’ll be publishing some examples of how I integrated mootools with Code Igniter, but alas, I have not yet had made the time to just sit down and do it. I promise, Derek, soon!

I just want to add that I have not integrated mootools as an Code Igniter class or library. I should prolly, but here is my reason for not doing it. Two reasons actually:

1. I’m too damn lazy… That and deadlines was WHOOSHING by again.
2. I like my Javascript seperated from my PHP and Code Igniter classes!

I’ll focus on the second reason, since that one is easier to defend. Firstly, let me just say once more that it is a matter of preference! I’m not arguing right and wrong here. Simply what I prefer and that can hopefully help you make up your mind if you have similar questions.

If you are going to integrate mootools with Code Igniter, you are going to write PHP that generates Javascript functions/classes. That for me is somewhat against the grain of the whole MVC philosophy. You already seperate your database access from your business logic from your HTML views. Now, you want to write PHP that generates Javascript just to make it easier to implement. What if you need very particular functionality? You will then have to want to stick with extending your PHP library to generate the appropriate Javascript functions. This is perfectly alright, but not always practical, since you might have certain time constraints.

There is of course a number of drawbacks you will need to consider when implementing mootools seperately, but more on that at a later stage.

Maybe I can be convinced that integrating it is better? I don’t know. It just feels more comfortable having it seperate.

technorati tags:codeigniter, mootools, javascript, php

Blogged with Flock

Spit it out!

Filed in: Code Igniter, PHP, javascript, mootools by: Stii