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.
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.
Mark Bowen - 09 March 2008 12:28 PM
Rob Q - 09 March 2008 12:21 PM
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.
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
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.
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 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?
For those of you getting antsy about how long you’ll have to wait, I imagine the EllisLab release of ExpressionEngine 2.0 is right around the corner—a month or two. That was the story with ExpressionEngine, which was released for a semi-public beta and then out to the public what seemed like a couple of hours later.
Smart developers understand the Osborne Effect—preview what’s coming Real Soon Now™ too far in advance, and kill your current sales. Announcing the next big thing can drive you into bankruptcy before you can finish it! Rick’s been through an upgrade/update cycle before, and isn’t about to let the Osborne Effect bring down the company. And note that this company is particularly tight with hints about future developments. If we’ve been allowed to see this, that means its arrival is a matter of a few days away.
that means its arrival is a matter of a few days away.
I would love to see it in a few days if you are right but I would think that it will probably take a little longer than that though. Hope you are right though. I would just like to see it before my 34th birthday though, or maybe on my birthday in a nice neatly wrapped box would also be nice
Looks good, hope it’s out soon we can start building on it. Read the whole thread and I didn’t see it covered yet… will EE 2.0 be faster and more efficient? Performance is a big issue for us.
