Guidance on "future proofing" plugins for Expression Engine 2.0?
Development and Programming
I am working developing a couple new plugins for Expression Engine. The first one is simple enough that I am pushing forward on it now. But another is way more complex. So, I am hesitating doing a lot of work on the more complex one out of concern that it will need a total re-write when Expression Engine 2.0 comes out.
So, I am wanting to know more about what will be different with Expression Engine 2.0’s Add-Ons.
Are there any guidelines for writing plugins that will require little or no changes to move from the current 1.6.x to the 2.x versions of Expression Engine?
(And, technically, what I am working on will likely end-up being a combo of extension and plugin.)
I appreciate that my question is pretty open-ended, and also that, until 2.x is a fully-baked released, things can change. But, any advice or guidelines about this would be much appreciated!
Anyone? Any suggestions?
I don’t think such info is already available. Best practice is to subscribe to the EE Blog. There’s gonna be an announcement calling for applications for the developer’s preview of ExpressionEngine.
If you have some spare time you can also take a first look at the Codeigniter framework to grasp the basic concepts behind it, as EE 2.0 will be build upon it.
Thanks silenz. I guess I’ll keep my fingers crossed for now, in terms of how the hooks into EE will change between 1.6.x and 2.x.
In general, I might start using CodeIgniter for my non-trivial plugin project. I could imagine that, in the future, ElisLabs will start including CodeIgniter in EE 1.6.x so that any 2.x compatible plugins can use CI classes without having to install additional (per-plugin) copies of the CI framework.
btw, I was glad to see your utilitEEs site – I have been using your SimpleTags 1.0 extension for a while, and have actually written some simple modifications to it (happy to share those with you). Looking forward to checking-out the new version you’ve released!