Thread

One question I forgot to ask was about the possible integration of an easier coding interface. I followed the lead of some on these forums and got TextMate and Transmit, and it would be great if there was something like Textmate built in to EE 2.0. Is this in the works, or even on the list of changes?

TM has the built-in ability to open content in a textfield in a new new doc and save changes back to the field in Safari (or FF I believe). I use this all the time in EE.

I’m super glad Veerle is doing the interface; it’s looking great and I’m sure the code is going to be clean, good idea! I’m even more excited about a modular and easily-customizable control panel. The ability to handle the backend in the same way as the front end would be amazing. CP template groups; I’m so ready!

As a recent convert to ee I’m super excited about these new changes. I’ve been lamenting about lack of interface, backend customization, better framework (code ignitor, yes!!) and lack of arms reaching out to things like jquery.

Sweet!

Just a point of clarification for those that did not attend the sneak peek at SXSW, or who did, but don’t have a knowledge of MVC application architecture, the CP themes are not going to be identical to front end templates.  You will be able to create and modify the View files that are used to display the application’s pages.  They are not stored in a database, nor do they use ExpressionEngine tags in their architecture.  More details will be available closer to release, but I felt this was an important distinction to make before people make that assumption based on community members’ replies in this thread.

Wow just listened to the entire 49:33.52 minutes worth of the SXSW podcast! Very interesting to hear.

Just wondering if we are allowed to ask the question that no-one asked in there? That being ‘collections’. Is this the new name instead of ‘weblog’.

Also did I hear Macgyver mentioned 😉

Best wishes,

Mark

Just wondering if we are allowed to ask the question that no-one asked in there? That being ‘collections’. Is this the new name instead of ‘weblog’.

One of the first pages of this thread says they are dumping weblog as a descriptive term. Not sure who said it.

Weblog as a term is being removed from 2.0. The new term won’t be made public until later. Until then think of Collections as a place-holder.

Can’t wait to work with 2.0, I like what I see so far.
Is there any information yet about upgrading from 1.6?
I hope some good work has been put in the file/image upload feature because this is the only thing that gives me headaches to explain to clients. I’m praying for an easier image handling and displaying in the CP. Any infos out on that yet?

Until then think of Collections as a place-holder.

Ah good! I don’t mind the word weblog but can definitely change to something different but just not collection as that by itself implies pluralistic tendencies of which I think it would be even more confusing to new users.

Thanks for that Leslie.

Best wishes,

Mark

Can’t wait to work with 2.0, I like what I see so far.
Is there any information yet about upgrading from 1.6?
I hope some good work has been put in the file/image upload feature because this is the only thing that gives me headaches to explain to clients. I’m praying for an easier image handling and displaying in the CP. Any infos out on that yet?

Hi Tilo - I listened to the podcast last night where both of your questions were addressed.  I will paraphrase from memory…

1) They hope to make 2.0 an upgrade (as opposed to a migration) where existing sites will work without modification - though it will be necessary to upgrade your plug-ins.
2) Image and file handling is something they are working on but it is not yet designed.  It is a high priority.

2) Image and file handling is something they are working on but it is not yet designed.  It is a high priority.

Well nothing that they could show yet (from memory of listening to the podcast too) 😉

Could mean they are playing around with ideas though and we all know what that means!! When the EE development crew have ideas it usually means that we are in for some fantastic creations.

Thanks EE crew, you are the best!

Best wishes,

Mark

Listening to the podcast, where Derek A. dropped the j-bomb, jQuery.
I think everybody’s draw must of dropped or something like an inner “wow” tingly sort of feeling.
Js libraries work like the db class in Ci, provide the driver for whichever library you want to use by changing one word in the setup, mootools, scriptaculous you name it.
S-ss-weet-ness.
On w/ the show…

Listening to the podcast, where Derek A. dropped the j-bomb, jQuery.
I think everybody’s draw must of dropped or something like an inner “wow” tingly sort of feeling.
Js libraries work like the db class in Ci, provide the driver for whichever library you want to use by changing one word in the setup, mootools, scriptaculous you name it.
S-ss-weet-ness.
On w/ the show…

Yeah that does pretty awesome.

While I think the UI stuff is good to see and well worth the effort, it’s the other things they can’t really ‘show’ that make for bigger changes - rewriting from the ground up using CI is huge. I haven’t listened to the Podcast but if they’re addressing document management and member module shortcomings (member template theming, members in multiple groups, etc.) then that’s two huge things to cross of the ‘cons’ list for EE.

On top of those two I think the biggest one for me is some easy way for a client to link to other pages when adding entries. That’s always a big one for me - “go to the page itself in a browser and cut and paste that url in the textarea” isn’t a very robust solution at this point.

I’m interested to learn more about changes to the database structure - I’m hoping that kind of info might be available. Are revisions going to be handled the same way? Are the title, fields and data structure for all entries staying around, or is this changing? This has major implications for a project I’m going to start developing in the next couple months, and needless to say I’d love to learn more.

I know there is no ‘release date’, but with information now more forthcoming about 2.0 I’m wondering if it’s possible to give any kind of indication as to what to expect moving forward. “We’ve know 75% of the functionality we’d like to include, and we’re about half way through development” or “We’re hoping to launch it in the 2nd half of 2008”. Something like that would actually mean a lot to me, and allow me to make some educated decisions about developing and licensing EE until 2.0 is released.

Excited to see and learn more.

It has been said before: if EL weren’t confident to be able to release something (relatively) soon, they wouldn’t've shown it at SXSW. Naturally, everybody is excited about EE2 now, and that might well affect sales for v1.6. Naturally, they are well aware of that, so I expect a first release sooner rather than later.

It has been said before: if EL weren’t confident to be able to release something (relatively) soon, they wouldn’t've shown it at SXSW. Naturally, everybody is excited about EE2 now, and that might well affect sales for v1.6. Naturally, they are well aware of that, so I expect a first release sooner rather than later.

My sentiments exactly.

Something that wasn’t maybe addressed, is CI on the verge of major changes as well?
Anybody wanting to get a jump start with codeIgniter need to know anything about what’s in the pipeline there? The current version cI 1.6.1 released February 12, 2008.

Thought I’ld ask, even though as LC said “I’m primarily a html/CSS guy.” 😊