Thread

“What the dev preview has confirmed for me is that we’re on the right track.” - Derek Allard, EllisLab

That pretty much sums up how things are going with Kaylee (the ExpressionEngine 2.0 Dev Preview). The past several weeks have been filled with feedback from the Developer Preview that we’ve used to shape 2.0’s add-on strategy and make a few key architecture decisions.

Post Permalink.

Great to hear you guys are making progress, and I’m really looking forward to seeing the Beta. My only concern at this point would be how long we’re going to have to wait, if you’re making architecture decisions now the wait might be longer than I was hoping.

Please don’t be longer than mid-year.

Patience is a virtue…
In a mean time I’ll work with 1.6 which works just fine for me 😊

Patience is a virtue…
In a mean time I’ll work with 1.6 which works just fine for me 😊

Completely agree, patience is a virtue. 1.6 works fine for most situations, but it’s hard explaining why we charge clients now, and will quite possibly be charging them another chunk in a few months to upgrade. So for some projects I’d rather try and make the clients wait for 2.0 so we can utilise CodeIgniter — it’s just hard without any idea when it’s landing.

exp_fortunes? 

So my FR for a “Get Rich Quick” module has been fulfilled? 😉

So my FR for a “Get Rich Quick” module has been fulfilled? 😉

Na, ‘tis still ‘bout good ol’ cookies . :blank:

Great to hear you guys are making progress, and I’m really looking forward to seeing the Beta. My only concern at this point would be how long we’re going to have to wait, if you’re making architecture decisions now the wait might be longer than I was hoping.

Please don’t be longer than mid-year.

I wondered if using the word “architecture” was a good idea in the post… as well as the car analogy. In the end I did because I felt it was the most honest description of what’s going on.

Its also turned out to be a word that is used a lot without a specific meaning and it has a rather “epic” ring to it when really it can apply to any decision that impacts the well, “architecture” of the software, regardless of how small or big that decision is.

In this case the types of architecture decisions we made (and may still make during the Dev Preview) are in specific regards to how 3rd party add-ons interact with 2.0. While these are important, “key” architecture decisions they aren’t necessarily time consuming.

These decisions include discussions on where 3rd party add-ons are installed in the folder structure, how certain hooks are used, dealing with language files in unique situations, update notification schemes, how certain types of queries should be written, and other things related to 3rd party add-on development and interaction with EE.

For example, if we decided to change where the actual folder for 3rd party add-ons is, that’s an important decision! Its an architectual decision. Its also a decision that requires very little time to implement. In other words, architectual decision doesn’t necessarily equal huge amounts of time.

Being able to speak with the most active and prolific EE devs informed these decisions. We discovered that in most cases our default assumptions were correct but in a few, the feedback altered our approach for the better. This is exactly the purpose of the preview and the result is a better platform for 3rd party devs. This type of discussion simply couldn’t have occurred earlier in the development process.

None of this is particularly exciting to a general audience which is why I didn’t expand on the nitty-gritty details in yesterdays post. Though given the feedback, I probably should have. Lesson learned!

So my FR for a “Get Rich Quick” module has been fulfilled? 😉

Hee- yes.  I tested it out and am now posting this reply from by new villa in the Bahamas while deciding which island I want to visit next on my yacht.

Or possibly, it was just the simplest module I had laying around to trigger an error with.

I tested it out and am now posting this reply from by new villa in the Bahamas while deciding which island I want to visit next on my yacht.

What, no ponies?

Maybe in 2.1?  😉

From the post:

We plan to do one more round of Developer Preview invitations (in the next week or so) before closing off the Dev Preview and concentrating on the next part of the release phase, the semi-public beta.

Mmmmmmmm…semi-public beta…tasty!

Robin, you have to give us syntax here! Some of us are still relative EE newbies.

{exp:fast_wealth:island mode="yacht"}
{related_entries id="drinks"}
  {served_in_coconut_with_little_umbrella}
{/related_entries}
{exp:fast_wealth:island}

😉

Looking forward to the Beta Release…

Once you get through the first six months of waiting, it gets easier as time goes on.

Once you get through the first six months of waiting, it gets easier as time goes on.

Ha, so true.  Sooooo true.

Hmmm,

This is presents a conundrum. I really don’t want to put a whole lot of money into development at this point, especially if it requires third-party add-ons, if it is going to have to be redone with the new release. On the other hand, there is no telling when the new release will be released. How are others addressing this issue? Are others just waiting, or are they moving ahead not know how much will have to be redone? I would like to move ahead with my project, but I can wait.

Rich