Thread

Yes but it’s actually the 1st April so that could be them playing a little joke on us couldn’t it now!!

Absolutely, but now that date creates even more speculation on intent and your response just adds to the “will they or won’t they” which I would say is the sole reason that specific day of the month was chosen. It adds to the anticipation and speculation.

Couldn’t agree more! 😊

Darn them for doing that though 😉

Best wishes,

Mark

EE 2.0 is actually being built in CodeIgniter, rather than simply being integrated with it.  this has some great implications, one being that the two communities will become close and can help each other.  in terms of how that will effect EE users, it will should not complicate things - you won’t have to learn it to use 2.0.  but it will give us add-on developers a superb framework on which to develop and integrate our apps.

i plan on elaborating on this more once i get home from sxsw (it was well worth the journey from dublin, and its nice to know that the team of developers that we respect so much are all really cool, level-headed people!)

I have the same concerns, hopefully the status bar at the bottom of this screengrab is not a function other than a toggle being called.

That’s just a standard Safari function when you hover over a link and hold the command key.

Well, you and Pixelated 😉.

I strongly suspect this new Control Panel design will be readily skinned.

The look for the show seems aimed directly at the Rails and want-that-look people - probably a good capability to show, ‘in their language’, for future sales.

What I noticed was that the capabilities of the CP are now organised in a logical way; no more hunt decades of menus for what you need. 

Thus the reduced version of the CP that website construction customers see ought to be quite a bit easier for them to follow.

Imagine that with the button-down, woven collar Arrow shirt look applied, and you are there for worries about various sizes of businesses.

I suspect EE folk will be sensible as ever, about assuring it all works without Ajax or Jquery.  Rather, it will just work better, when they are there.

Speculating on when; well, that’s a mug’s game, isn’t it?  We already see some fishing for the features direction in 1.62, so they are carefully testing various waters.

I admit I hoped for something other than PHP as a ‘what other language could we use’, but in fact it has been sounding like Code Ignitor is the bee’s knee’s to keep from having to do messy functionality.  Just as EE is where it suits.  Probably this is then a very good decision, the CI rebuild. Presumably they will have a solid beta program to root out issues.  The same in terms of a helping hand to developers to get the important extras up to date.

Realistic?  I hope so, and likely think so, after a while to see how the Ellis team sees things and pulls them together.  That second part is especially impressive. 

Best to each, and great luck with the show…
Regards,
Clive

I have to agree with PXLated I’m afraid (btw that’s not a dig at you PXlated! 😊 )

I think the design is nice but just not right for this kind of application. EE has very quickly grown into an outstandingly capable application and I just think that the design (again no offence to Veerle as she is an excellent designer) doesn’t quite reflect this. Of course we haven’t seen a final version or one with all the AJAXy goodness in it so I am definitely going to hold reservation until I too get my grubby little hands on it 😉

Best wishes,

Mark

But why. For my point of view EE 2.0 should be usable without using the CI. Anyway, hopefully we dont have to start use CI just to use incoming EE. In the end i think i must also DL CI just in case but im not hoping that i need to learn 2 new things when its time. =)

Right, the so called “CodeIgniter integration” or whatever you want to call it should be totally invisible to the user.  I doubt downloading CodeIgniter now will give anyone any sort of head start on developing ExpressionEngine 2.X.  Only Ellislab knows the end result and I bet building things in ExpressionEngine will still be much different than building in CodeIgniter.

With few details, imaginations tend to run wild.  I will probably look back and laugh at my own thoughts on the subject when everything finally releases.

EE 2.0 is actually being built in CodeIgniter, rather than simply being integrated with it.  this has some great implications, one being that the two communities will become close and can help each other.  in terms of how that will effect EE users, it will should not complicate things - you won’t have to learn it to use 2.0.  but it will give us add-on developers a superb framework on which to develop and integrate our apps.

i plan on elaborating on this more once i get home from sxsw (it was well worth the journey from dublin, and its nice to know that the team of developers that we respect so much are all really cool, level-headed people!)

I posted a bunch of stuff on this too.  Click my sig to see.

I admit I hoped for something other than PHP as a ‘what other language could we use’, but in fact it has been sounding like Code Ignitor is the bee’s knee’s to keep from having to do messy functionality.

Why other than PHP?  I’m sure the last thing Ellislab needs to stuff into their busy schedule is to become expert with other languages and then rewrite everything in one or more of those languages.

Here’s a change to look at. 

It’s just a few color changes, using Replace Color in wonderful Photoshop CS3 - one for the buttons, and one for the strong element in upper right with sign-in name.

I also blanked Veerle’s logo, as that is part of the original effect.  What I actually did here was the put Masugo’s in place, as it is a quite professional job, and adds a lot in the direction I think you guys are seeking.

You’ll have to do that last yourself, as didn’t want to use Masugo’s property of course.

I admire Veerle’s work, and think she’s actually done a great job here, and in how much she may have influenced the clearer functionality.  That a few color changes and a logo change can lead to a quite different and useful feel is evidence of her design thinking.

I imagine she was asked to use a color scheme fitting the Ellis Labs sites, for this demo at the Show.  Take away that orange, and shift the greens to blueish-greens that are cooler for business and tech, and this is what you get.  Max size I could make it and still post here.

Regards,
Clive

I’m hopeful that we can customize the CP, at least theme-wise. But, in almost all cases, the client (other than a client super admin) has access to only two things, publishing a new entry or editing a current one. Those big headers look somewhat overwhelming to me when there is only one item available under each (see modified screen grab).

Edit-Add: Until I see the whole thing in action and how configurable it is, it’s hard to know what’s what or what to like or not like.

I don’t really care to much for the interface of the CP; as long as it’s logical, user’s will find it. If there would be one change for the Control Panel I would like to use a more icon-based version (combined with text of course). Beside the fact that content-editors love to see icons, they can be really usefull as well. But I assume that the templates for the CP are easy enough to change. I prefer the dev-team will put all their time and effort in functionality.

Beside the fact that content-editors love to see icons

They do?

That would just be plain evil. :-p

I understand their reasons for not releasing a date.  But some sort of timeframe could be appreciated.  I think it’s a little irresponsible to tease us with screenshots, videos, etc… and not give a timeframe.  All I’m looking for is an approximation - 1 months, 2 months, 6 months, 1 year.  Nothing exact, just a range and if they can’t meet it, they can’t meet it.  It’s not set in stone.

That timeframe dictates some key business decisions for me.  My dilemma is do I spend the resources and time to develop add-ons now which might become obsolete in EE 2.0 or wait.  Now, if the EE release is 4,5,6 months away, it makes sense for me to make the investment in time and resources to develop add-ons.  Otherwise, it doesn’t.

Just my thoughts.  Of course, that might just be the anticipation mixed with excitement mixed with speculation talking. 😊

My personal guess is that since there is a screen-shot from the demo of the control panel with a build number saying april 08 in it that may be a clue as to when they might anticipate the beta released to developers for accessory add-on testing.

Yes but it’s actually the 1st April so that could be them playing a little joke on us couldn’t it now!! 😉

Best wishes,

Mark

I don’t really care to much for the interface of the CP; as long as it’s logical

I agree, but unfortunately not attending the event leaves us only with hearsay and screenshots…

Cosmetic issues are not top priority, and as i said before as long as the markup has been approached responsibly, we can do whatever we like to the interface via css. I’m hoping they’ve learnt lessons from the member profile templates, and not using superfluous markup like

I can’t wait to take it for a spin.

Nothing exact, just a range and if they can’t meet it, they can’t meet it.  It’s not set in stone.

That’s one of the major things though…if they don’t meet it, people will say, “they said it would be done” and then get upset. While it is frustrating, I agree, I completely understand why they don’t do it and I respect them enough to know that they will do the right thing.

Just decide if EE works for you right now…if it does, buy it and move on. If it doesn’t, then choose something else.

That would just be plain evil. :-p

I understand their reasons for not releasing a date.  But some sort of timeframe could be appreciated.  I think it’s a little irresponsible to tease us with screenshots, videos, etc… and not give a timeframe.  All I’m looking for is an approximation - 1 months, 2 months, 6 months, 1 year.  Nothing exact, just a range and if they can’t meet it, they can’t meet it.  It’s not set in stone.

That timeframe dictates some key business decisions for me.  My dilemma is do I spend the resources and time to develop add-ons now which might become obsolete in EE 2.0 or wait.  Now, if the EE release is 4,5,6 months away, it makes sense for me to make the investment in time and resources to develop add-ons.  Otherwise, it doesn’t.

Just my thoughts.  Of course, that might just be the anticipation mixed with excitement mixed with speculation talking. 😊

I understand your point of view in that you develop add ons that potentially could become obsolete in version 2.0. But I also see EE’s point of view in that if they release a tentative date and fail to meet it, everyone is up in arms. I’m guessing a lot of us wouldn’t have a problem if EE gave a date and failed to meet it, but the truth is that a lot of people out there would be upset by it and in the end I’m guessing it wouldn’t be good for Ellis Lab’s business for every EE blogger to start saying things about them not meeting deadlines, etc. in the rumor mill.

I could be wrong?

Edit-Add: Until I see the whole thing in action and how configurable it is, it’s hard to know what’s what or what to like or not like.

Yes, that’s for sure, and how I feel also.

Good point about mini-menus with big intro buttons also - somehow I think we’ll be able to take care of this if it needs to happen.

Cheers, PXLated, and sorry to have mis-spelled your name.

Regards,
Clive

I understand your point of view in that you develop add ons that potentially could become obsolete in version 2.0. But I also see EE’s point of view in that if they release a tentative date and fail to meet it, everyone is up in arms. I’m guessing a lot of us wouldn’t have a problem if EE gave a date and failed to meet it, but the truth is that a lot of people out there would be upset by it and in the end I’m guessing it wouldn’t be good for Ellis Lab’s business for every EE blogger to start saying things about them not meeting deadlines, etc. in the rumor mill.

I could be wrong?

You’re totally right.  And I respect that.  I know the chances of them setting a date are against their interal philsophies.  I was just expressing some wishful thinking.

I wish there wasn a easier way of making some development decisions rather than just an endless waiting game.  But, I digress…can’t always get what you want, right?