Thread

If you are discontinuing Morphine are you going to fix the settings panels for your extensions to not look terrible without it.

I had to setup Better Meta for a site today and the extension settings panel is a mess without Morphine, but Morphine doesn’t work properly with 2.1.3.

Yep all my addons will be updated when this goes live. Bascially I’ll be releasing an update to Morphine which will remove the cp_tweaks and update the style to match the override.css

Found an issue on the add/edit custom fields within a channel - there’s a massive top margin!

Same applies on the page after submitting a new entry.

Holy bejebus! Looks like a clearing issue. I’ll fix that tonight and push up a new version.

Ah yes I noticed that too but in a different part of the CP but noticed that it was only doing it when the sidebar is open. Sorry meant to mention it earlier on.

Looks great Leevi.  We’re just starting to roll clients to EE2, and the look and feel of the CP is one of our few worries.

You can sign us up to maintain a blue fork, we’d be doing it anyways.  Quick find/replace:
http://dl.dropbox.com/u/611205/cameron/morphine2-blue.png
http://www.bluestatedigital.com/

Really like having this in a few CSS files, rather than as accessories + modules + extensions.

As to your questions:

1) Our clients only use publish and edit screens really, but those need to work in IE.  Doesn’t need to be as good as CSS3 supporting browsers, but needs to work.

2) Yes, this is much improved.

3) Happy to help pay for updates.  But for the EE community, having a freely available (preferably Ellis Labs blessed default) theme would go a long ways. 

I’m wondering if there is an amount of money that could be raised to fund your ongoing maintenance time.  Maybe Ellis Labs pays for it (easy to spend others money), or maybe the community raises it.  We’ll certainly chip in to set this free.

In the long run, I think EE needs a pleasant default experience to compete, and this seems like a great step in the right direction.

~cc

Morphine will no be developed in favour of this override.css. Consider the override.css a Morphine v2.

...

I don’t plan on adding any colour ways to this override.css. The added support development would be way too much. That said I’d be happy to create a fork and allow a private collaborator to keep the additional colours upto date.

all ideas…

Blimey - what I love about Morphine is less so the colour changes, and far more the simpler UI - I know you do tend to prefer UIs with as few graphics / images as possible, and Morphine meets that minimal approach brilliantly.
For me, working on the default EE skin with all it’s gimmicky rounded buttons, tabs and corners makes it look way too unprofessional and, well, gimmicky.

...that I prefer the colours of Morphine is a bonus.

Is the reason for this due to the ongoing support with making morphine compatible with future EE versions as well as other 3rd party addons?

And forking - not something I have a great deal of experience with but if other people are wanting to take Morphine on and adapting it, I’d be happy to help where possible.

You can sign us up to maintain a blue fork, we’d be doing it anyways.  Quick find/replace:
http://dl.dropbox.com/u/611205/cameron/morphine2-blue.png

Excellent.

1) Our clients only use publish and edit screens really, but those need to work in IE.  Doesn’t need to be as good as CSS3 supporting browsers, but needs to work.

I’m pretty sure they will although I havent tested it yet

3) Happy to help pay for updates.  But for the EE community, having a freely available (preferably Ellis Labs blessed default) theme would go a long ways.

I’m wondering if there is an amount of money that could be raised to fund your ongoing maintenance time.  Maybe Ellis Labs pays for it (easy to spend others money), or maybe the community raises it.  We’ll certainly chip in to set this free.

I haven’t put anything to Ellislab regarding override.css. I guess they are doing updates to the CP for version 2.1.4 so that will be interesting. The goal of override.css is to make improvements to the default CP theme. I hope one day there is no need for it.

Regarding funding the fairest I can figure is a user pays scenario. If EL were to cover the cost of development (similar to SAEF cracker) I’d be happy to hand the code over, that way everyone benefits.

Gah! Sorry - I’m being dim - hadn’t clicked that you’ve made teh overide.css file to look the same as Morphine, in which case, yes - it’s perfect - I’ll happily pay you a one off fee to make all my EE installs look clean and proffesional.
Might even try tweaking the overide colours too 😉

@moogaloo: Override.css aims to build on the principles of Morphine and remove all the unnecessary “flourishes”. The reason why I’m considering charging for it is purely to cover support and updates. I don’t want to get in a position where the community is wondering if I will stop supporting my other commercial addons.

Morphine will be limited to styling my addons only and will use many styles from override.css. Morphine is more than just styles, it’s also a set of scripts and HTML markup.

Gah! Sorry - I’m being dim - hadn’t clicked that you’ve made teh overide.css file to look the same as Morphine, in which case, yes - it’s perfect - I’ll happily pay you a one off fee to make all my EE installs look clean and proffesional.
Might even try tweaking the overide colours too 😉

Looks like your reply was published just before mine :D

Here’s a bunch of screenshots so you can see what override.css looks like: http://emberapp.com/explore/tags/override-css

yeh - i actually just installed it to see what it was like and at first wondered if I had actually installed it correctly as it does look like just Morphine - good work!

and yeh - i can see how its far better to manage a CP theme via a CSS file and not have to be overwriting HTML etc too.

One odd thing - some of the colours dont seem to match up tho…
the red-pink block in the top right with my name and logout on it - thats showing in firebug as #D91350
link text is showing as #E7174B
but your css file says #c21148 - Pink

the css file it’s pulling those from is /themes/cp_themes/default/css/global.css?v=1295449076

Am I missing something here?

@moogaloo: I probably just need to tweak a couple of things.

ah - ok - just checking I wasn’t once again being a bit slow.

Just pushed a decent update to override.css that fixes matrix issues, consolidates pink and fixes a couple of other layout bugs. Oh it also fixes the template access / preferences sub tables.

Release: https://github.com/newism/nsm.cp_override.css/tree/1.0.0PR2
Screenshot: http://emberapp.com/leevigraham/images/template-manager-expressionengine-1

We’d be happy to pay an unlimited licence Leevi.

Will you be commenting the code so we can adequately brand the CP with the site’s colours?

I’ve been having an issue with the breadcrumb_tab.png not showing in Firefox 3.6. I changed line 419 (under #breadCrumb li) to

background: url('../images/override/breadcrumb_tab.png') no-repeat right 50%;

reversing the background-position settings and that seems to resolve the issue.

Nice job, as always.