Thread

I wouldn’t hold out for anything.  Do it now!  😉

Perhaps you could develop your app in EE rather than CI.

Haha, whilst development with EE would be a dream… I require the flexibility of CI in this instance. Especially since expansion in the future may lead us into areas which EE may not be best suited.

I am extremely sorry for my ignorance here, but I am struggling to see how EE integrates with CI from a CI developers perspective. Could someone please give me an example of where having CI developed application could benefit from installing EE on top?

CI is a framework, so if course it could be used to build something entirely incompatible with EE.  The shared libraries and resources however make it easy and efficient to develop an app that is fully compatible with a full-fledged CMS.  For a CI app to truly be integrated with EE, it won’t change the basic fact that for two applications to work together, they must be designed to do so.

This is fantastic news—i’m tempted to say a dream come true, but that would be too much, so i won’t.

but i have a question—in what way is EE going to be built on CI? what i mean is perhaps better explained by an example.

if i am developing a CI application, could i just drop in different EE modules, foregoing others? for example(fake code):

“load membership module”
“load wiki module”

{if member access == 1}

{embed wiki="mainwiki" template="bluebird_3col"}

{/if}

...so that EE modules can be invoked in a controlled context. is that the idea? or would it mainly be loading the entirety of expression engine, which would then handle the activation of hooks, extensions, modules, plugins, etc.?

thanks,

ward smith

It’s almost Summer, which is going to be a little bit like Christmas or a birthday around here 😊 Sorry had to bump the thread.

tip-ee, summer is more than just a single day. 😊 But we’re all looking forward to 2.0.

No pressure here. It’ll be ready —when it’s ready!
Is it soup yet, lol. 😊

Come to Florida; it’s friggin’ summer alright… 88+ and humid all day/night. *ugh*

As an aside I’m hoping to develop some backends like this in ee2:
http://flickr.com/photos/daverau/2575254141/
http://flickr.com/photos/daverau/2575254135/

Will this be fairly easy in ee2?

I’m evaluating using ExpressionEngine for my company.  Is there any word on when 2.0 will be released? We have some CodeIgniter functionality already built and don’t want to rebuild in EE to make it work now, and then rebuild it BACK to EE when 2.0 comes out.

The announcement was in March, and it’s now August.

“This summer” still holds true.

So, Ingmar, you’re basically saying that your deadline is up through and including the last calendar day of summer? September 21st? That’s ages!

Or 22nd, depending on your time zone 😉

September 21st? That’s ages!

That’s only 6 weeks - not that long - assuming it arrives on time.

anyhow, since the the summer 2008 announcement there have been a ton of threads, when is it coming. Now I understand ellislabs previous stance on no ETAs.

Hello,

I don’t expect to know the release date. I’m happy with knowing that it will soon come. However, I do urge some communication with the developer community so that we may make well-educated decisions in regards do our corporate concerns. Apart from knowing that somehow the benefits of CI will make its way into EE, we have very little knowledge of what to expect in EE 2.0.  Our company is very busy occupied with developing several modules and extensions for EE 1.6.5, some of which will be made open source and contributed to the community. However, it is frustrating to know to that possibly a lot of our source code might require extensive re-factoring. Please EllisLabs, if we could have some tips regarding how to prepare for the EE 2.0 release we should feel much more confident in moving forward with our own projections.

I am personally very excited about the release, and encourage others to be too - but having something more concrete than saying “it’s cool because it just is” would make some of our executives excited as well.

A happy and loyal customer…

From the sneak preview page:

We will be releasing a Developer Preview of ExpressionEngine 2.0 prior to ExpressionEngine 2.0’s public release. This will give developers the opportunity to update their add-ons to ensure compatibility with ExpressionEngine 2.0. Although third-party add-ons for the 1.x version of ExpressionEngine will not work with 2.0, the changes necessary to make them work are minimal.  We will provide a list of add-ons that have been updated for 2.0

If you are a developer for EE please subscribe to the ExpressionEngine Blog as we will post information on how to apply for the Developer Preview there when it’s available. 

Our company is very busy occupied with developing several modules and extensions for EE 1.6.5, some of which will be made open source and contributed to the community.

I thought I’d missed a new release then!