Thread

Hi folks,
I am trying to decide if I should wait to buy a commercial lic. for ee 2.0 vs a commercial lic. for the most current version.

My question is do you have an idea or an opinion as to whether or not ee 2.0 on the ci framework as opposed to the current version would be more suited to some admin and member back-end customizations(modules, extensions etc.) so that members have the ability to save real estate properties to their own portfolio, save searches they have made for themselves, have emails automatically sent to them when properties in their searches have been updated (price changes, status changes etc.)and for the admin some crm tools like leads/members management, auto responders etc.

I am trying to save money. Would it be easier and less costly for a programmer to work with ee 2.0 because of the ci platform as opposed to the current ee version? I’ll already have considerable costs in having a programmer hook ee up to our local property multiple listing service (MLS) and its RETS server to download property listings to the ee db.

I am just trying to avoid having to pay for programmer back-end re-dos after an upgrade from ee current version to ee 2.0 if that is the route or just wait for ee 2.0 ... 😖

Thanks and have a GREAT day!  😊

Hi,

Since there is already a large community of CodeIgniter developers, I think you would actually have more potential contractors to choose from for EE 2.0 than you do now. I don’t know if it’ll save you money, but you might get some more competitive offers simply because the community of developers is most likely larger.

Hi Mike,

I’m in the same situation for our Job Openings website (see it as a Job Alert kind-of-thing):

We need the ability for our members to save their Job search criteria/interests (which industries, province/state, full-/parttime etc) to their account. When new Jobs opening are added and match their criteria, they should receive an status update email.

Something like this

We’ve not yet started, but we’ll have to do so within 1-2 months. Difficult to make a decision on this one. Hopefully the EE-team will give us more info about the release date of EE 2 before the end of december…

I’m going to borrow an answer our CTO Derek Jones gave to a member of the Pro Net:

If you build an add-on that works well in ExpressionEngine 1.6, then converting it to 2.0 to use CI’s libraries, helpers, etc. would not be difficult.  Add-ons continue to interface with ExpressionEngine in the same manner - the difference will be in the methods you choose to execute, and some syntax differences between using EE 1.x’s global objects versus using CI’s super object.  You won’t be using controller and views for front-end functionality, so any work you expend in that direction with CI will be more difficult to translate to EE than it would be to convert your EE add-ons to take advantage of CI’s way of doing things.

That said, to some extent, PHP development is PHP development.  It’s unlikely that any effort you expend would be a complete waste in either direction, since your logic, variables, and algorithms would essentially be unchanged.  I’d do whichever you’re comfortable with deploying and sustaining now, with the tools currently at your disposal.

Bottom line, developing for EE is changing yes, but anything developed for the current version of EE can be updated to the next version with some effort. “Hand wringing” gets you no where. If you need a project done there is absolutely nothing wrong with starting with what’s available and planning from there.

As we’ve stated before 2.0’s release isn’t going to be a surprise. There will be stages to its release, starting with a developer preview, followed by a beta, and finally a public release. The public release will be determined by how well the initial stages go.