Thread

Progress on 2.0 continues smoothly and the light at the end of the tunnel gets brighter and brighter. Jones is wrapping up a new Kaylee package, Greg whipped out some cool CSS3 solutions for a few places where we want to be edgy with the Example Site and is now searching high and low for fonts. Lisa and I are working out a few Example Site deployment details. Allard is working on “quick save” improvements, Robin is finishing up a number of important Q&A tasks, and Pascal is making jQuery do whatever he wants (he’s quickly established himself as a Javascript master ‘round these parts).

Post Permalink.

Hooray for being on target! I’m looking forward to 2.0 more than Xmas…

Oh joy of joys! Ready for the Beta!

...Greg whipped out some cool CSS3 solutions for a few places where we want to be edgy with the Example Site and is now searching high and low for fonts.

www.acidfonts.com - The best resource for a crazy amount of free fonts that I’ve ever encountered.

no major obstacles have shown up

That’s only because I haven’t tried it yet. I can screw up anything. 😉

Sounds like we’re getting really close now. Looking forward to the final date when it arrives.

No Comment (after my flaming last time!!! 😉 )
But seems like things are happier in the office and its going well, congrats. 😊

A European Vacation, huh?

“Hey look kids, there’s Big Ben!”

A European Vacation, huh?

“Hey look kids, there’s Big Ben!”

We’ve been lured to Europe by tales of “the best beer on Earth” residing there. Big Ben is nice too I suppose.

Pascal is making jQuery do whatever he wants (he’s quickly established himself as a Javascript master ‘round these parts).

ExpressionEngine 2.0 is of course a very complicated project. But jQuery is hardly suitable for complicated projects because of its lack of methods for handling inheritance. jQuery’s plugins are monolythic; you cannot take the function which was defined in one plugin and use it in another plugin. There was some experimentation to add methods for handling inheritance here and here, but none of them seems to be production-ready.

So, if it is not some secret, do you use some inheritance technique for jQuery?

So, if it is not some secret, do you use some inheritance technique for jQuery?

We’re using jQuery, and its plugins, where it makes sense to do so. We carefully evaluated its appropriateness for this project, and I must say we all really enjoy working with it. To directly answer your question, no we aren’t using any inheritance technique.

Based on the list of what you guys are working on, couldn’t this really be beta already? I mean, I’m not too concerned with what fonts are used on the example site at this point. And, if it’s an issue with having enough documentation, etc. you could release it to some of the more experienced EE users first. I’m not trying to be critical. You guys know when it’s ready I’m sure. Just this post had me thinking why not release it now and get the ball rolling?

Based on the list of what you guys are working on, couldn’t this really be beta already? I mean, I’m not too concerned with what fonts are used on the example site at this point. And, if it’s an issue with having enough documentation, etc. you could release it to some of the more experienced EE users first. I’m not trying to be critical. You guys know when it’s ready I’m sure. Just this post had me thinking why not release it now and get the ball rolling?

Some of the things Les mentions need to get to third party developers prior to the beta, so that there can be some third party add-ons for beta testers to use right out of the gate.  So while we’re close, it’s still not quite there.

Thanks Derek! As always, you explain it very well.

Big Ben is nice too I suppose.

Hey! What about Little Ben?