Thread

If there is no specific news about the 2.0 update…. then some general information about 2.0’s goals and direction would help. 

How does EE 2.0 work with CodeIgniter? 
How will CodeIgniter integration benefit us?
How will 2.0 help us build better sites and attract better clients? 

Since most of us were left out of the SXSW 2.0 preview…  Maybe some of the SXSW Preso could be rehashed into a series of articles?

Certainly.

How does EE 2.0 work with CodeIgniter?

http://ellislab.com/blog/entry/expressionengine_20_fully_codeignited/

It is just like any other CodeIgniter application. It is built on an essentially stock codebase of CI 1.7.1

How will CodeIgniter integration benefit us?

Also well answered in the link above, but the crux is:

If you’re an ExpressionEngine developer you will have a greatly expanded community of talented developers working with you, and for you. 

If you’re a CodeIgniter developer, this means you can drop a full-fledged content-management system right on top of your existing code base, and have it work.

Here are a few other nice things that we’ve shown.

http://ellislab.com/blog/entry/accessories_a_quick_primer/
http://ellislab.com/blog/entry/site_themes_in_2_0/
http://ellislab.com/blog/entry/a_present_for_your_friday/

How will 2.0 help us build better sites and attract better clients?

Allow me to expand this question to “better sites than EE 1.6”. The answer is, it won’t. ExpressionEngine will remain among the most flexible platforms on the planet. Anything you can do in EE 1.6 can also be done in EE 2.0. The principal gains are to the backend, where the CP is better organized, faster, more flexible and more powerful, as well as access to a broader community of third-party developers; but in terms of actual “will I see a difference on the public facing part of my site” the answer is essentially “no”.

We’re replacing an older engine with a shiny, modern piece of engineering, but the car will still look the same to those not looking under the hood.

Looks like my timing is perfect. I’ll be leaving Texas for the next two weeks to vacation in a place my four-year-old daughter likes to call “Fran Sancisco,” returning just in time for the next update.

Mmm…yummy.

“...while visions of sugar plums danced in their heads.”

We’re replacing an older engine with a shiny, modern piece of engineering, but the car will still look the same to those not looking under the hood.

A bit like upgrading a V8 to a supercharged V12?

A bit like upgrading a V8 to a supercharged V12?

Yes, but perhaps with improved gas mileage, a rust proof exterior, and better handling.

any official date for the release? 2.0?

any official date for the release? 2.0?

Nothing has changed in that department*, but as the steady stream of developers using Kaylee continues to grow, it’s clear we’re marching in a forward direction.

Is there any chance 2.0 will allow such a feature as allow posting a comment or submitting via SAEF and having an inline AJAX-esque Refresh? 😊

Looking forward to the next installment - I start a 10 week vacation come friday and have no client work lined up so have loads of time to make ASSumptions about what the next update will be.

Nice to see a sense of humour whilst you are all busy coding away. Means one of two things, either you’ve all gone stark raving bonkers or more likely you have totally proven what an excellent bunch of people you are. I’m betting on the latter one.

I see talk of new icons of which I’m guessing Mrs V? 😉

Cmon, let me in, let me in…I’m working with 3 client sites and one of my own…i just cant wait anymore….*crying like a lady and same time asking to get involved in some way*...

It’s getting too hot here with all these updates. How many beers i need to serve that i can get my hands into Kaylee or the next one…pleeeaase =)

- Peteomenon (like phenomenon ya know..)

Petri, it’s currently a developer preview; it gives developers a chance to take a look at the internal workings, file structure etc. and allows them to convert their plugins, modules etc. It’s by no means a full-fledged beta (which will come, too!) yet. Although I hear we’re getting closer…

Petri, it’s currently a developer preview; it gives developers a chance to take a look at the internal workings, file structure etc. and allows them to convert their plugins, modules etc. It’s by no means a full-fledged beta (which will come, too!) yet. Although I hear we’re getting closer…

Yeah me know me know =) But as all of us, we are drinking more and more water now to keep our heads and minds cool so that the exitement dont go and make our life too hard ya know.

I’m kinda of a “softjunkie” and evertime something new comes, i just need to work with it and find myself in endless “ahaa’s and wow’s” if you know what i mean.

Anycase, I think i need to “plug myself off” from the net soon so that i can’t access here and see these updates what makes my brains and mind grazy, lol. Few months away and then i access again and wohoo - there might be christmas =)

Packages—that sounds very interesting indeed. Is it about being able to easily reinstall a site’s structure without its data, so that say I build a site for a movie theater, then I can easily reinstall the general movie theater-ness of it for another similar site?

Quick notes…

1. Release date: We’re not giving out a date until well into the beta. Why? There is no point in doing so until we have data from the beta. Hey, that rhymes. There is a release process… Developer Preview (closed & almost done), Beta 1 (small, targeted group), Beta 2 (larger group), Release Candidate, Public Release. The beta will not be open. You’ll have to apply for it, just like the Developer Preview. The difference is that the beta is aimed at web developers in general, not just EE add-on developers like the Dev Preview.

2. Features: We will likely not comment on new features until well into the beta. We learned a hard lesson last year in that regard and its simply this. When we start talking features, people translate that as “selling it”. Once we start “selling it”, if there is nothing to buy, it turns into hype and angst. We want to avoid both.

3. Packages: This is specifically for add-on developers. Its a way to literally “package” add-ons that streamlines the installation and maintenance process for developers. This translates into a better experience for end-users and non-developers as well, but its primarily a set of tools that makes developing and deploying 3rd party add-ons a better experience.

Packages are the direct result of that “key” decision I blogged about and its turned out to be exactly the right decision. Team Kaylee (the people in the dev preview) did a great job helping shape Packages.