[wp-hackers] Re: Not Feeling Crazyhorse

Viper007Bond viper at viper007bond.com
Mon Sep 15 12:53:40 GMT 2008 

There already is an API to change the admin CSS via a plugin, three ways
infact (listed from best to worst methods)

1)  Use wp_admin_css_color() to register a new admin "color" which requires
a new CSS file, so just add the custom CSS in there (the colors you pass to
that function are only used for the theme picker, they aren't actually used
CSS wise). When the user picks the new color scheme, they are actually
picking a while new design. When you switch between Fresh and Classic, you
just happen to be using two designs that look the same minus colors.

2)  Enqueue a new stylesheet:  if ( is_admin() ) wp_enqueue_style(
'my-admin-theme', plugins_url('/my-admin-theme/theme.css'), array(),
'1.0.0', 'screen' );      but this isn't per-user like #1 is.

3)  Least preferred method, but you could just hook into "admin_head" and
output a <style> tag.


Short of actual admin themes (which I discussed earlier and mentioned why
they'd be a bad idea), I can't think of how it could be any easier to reskin
the admin area. Heck, I have been using the above methods to make tweaks to
the admin area for ages now (for example, to make the category picker box
much taller so there's no scrollbar).

And WordPress does ship with two admin themes already (Fresh and Classic).
They are the same design though, but that's because the devs pick one horse
and stick with it as it's been determined it's the "best" choice.

On Mon, Sep 15, 2008 at 5:39 AM, Xavier Borderie <xavier at borderie.net>wrote:

> I'd be cool with changing the CSS of the admin area, if it was both
> stable and documented. As it is, AFAIK, it is more of a question of
> guess work, trial and errors. And not all themes developers (ie.
> designers more than coders) want to deal with the Plugin API.
> Having a solid way to update/modifiy the CSS has long been a request
> of some themes, even more so since the introduction of the
> "Fresh/Classic" color schemes. Some altruistic developers build it up,
> like James Dimick (
> http://www.jamesdimick.com/creations/easy-admin-color-schemes/ ), but
> the huge change of 2.7, one could think the core-devs would have used
> the "let's start from scratch" admin redesigning as a justification
> for going the obvious next step in this matter : at least explicit
> admin-CSS, at best an API...
>
> Of course that would mean many many badly-built admin themes, just
> like there are a humongous number horribly-built wp themes out there,
> but in the end this would allow WP to be shipped with 2 or even 3
> admin theme, and that's about enough to make all users happy without
> having them scouring the Web for another one. And, obviously, the
> happy devs that live by selling custom WP, who'd be able to custom it
> even further. All this to say, I don't see anything wrong with this
> direction :)
>
> -x.
>
> 2008/9/15 Viper007Bond <viper at viper007bond.com>:
> > That'd be a nightmare waiting to happen. Theme developers seem to have
> > enough trouble adding wp_head() and wp_footer() to their themes, I
> couldn't
> > imagine how they'd do with admin themes.
> >
> > I think the current method of just changing the CSS of the admin area is
> > just fine. I mean, look how different the various admin theme plugins can
> > make the admin area look without changing any of the DOM. Heck, worst
> case
> > scenario they could tweak the DOM via JS or PHP's output buffer.
> >
> > On Mon, Sep 15, 2008 at 2:40 AM, Xavier Borderie <xavier at borderie.net
> >wrote:
> >
> >> I suggested making everyone happy by building some sort of "user-made
> >> admin template" API, back in August.
> >> http://comox.textdrive.com/pipermail/wp-hackers/2008-August/021448.html
> >> Got a bit of traction around here, if I remember well, but now we're
> >> too far in dev, and too close to feature freeze, to think about that.
> >> I think its too bad, really, 'cos it could really have been a huge
> >> plus for both users (ability to choose between 2.3, 2.5 and 2.7-style)
> >> and developers (ability to build tailor-made admin for clients).
> >>
> >> I still think it's a neat idea, and wish the core-team would consider
> >> this for the near future (2.7 might be too late, so 2.8?)
> >>
> >> -xb.
> >>
> >> 2008/9/14 Frank Bueltge <frank at bueltge.de>:
> >> > Why is it not possible to set the backend-theme in the user-settings.
> >> > All functions for this feature is in the core. It si hard for many
> >> > users you change very often the design.
> >> > I use wordpress in many buisiness-bligs with many authors. I set the
> >> > backend theme on design of WP 2.3 - the people tha tankyou, she will
> >> > not changes i the backend.
> >> >
> >> > Liebe Grüsse
> >> > Frank
> >> > ______________________________
> >> > Mein Buch: WordPress - Weblogs einrichten und administrieren | ISBN
> >> > 978-3-937514-33-8
> >> >
> >> > bueltge.de
> >> > kvfl.com
> >> >
> >> >
> >> >
> >> > On Sun, Sep 14, 2008 at 5:37 PM, Aaron Brazell <emmensetech at gmail.com
> >
> >> wrote:
> >> >> For me its not about the look and feel or ugliness. Is about
> >> >> usability. After a month of using and hoping I'd "get used to it",
> >> >> understanding from years of being a support person that users are
> >> >> change-averse but generally get used to changes after time, and I
> have
> >> >> not got used to it. It doesn't "feel" right and its not about colors,
> >> >> fonts, or backend functionality.
> >> >>
> >> >> If someone cares to clarify the semantic efforts here, I'd welcome
> it.
> >> >> To me, though, its a layour change like any other layout change. I'm
> >> >> happy to be corrected. I admit not being close to the development
> >> >> cycle on this.
> >> >>
> >> >>
> >> >>
> >> >> On 9/14/08, Stephane Daury <wordpress at tekartist.org> wrote:
> >> >>>
> >> >>> I'm assuming that the plugins options page contention is that the
> >> >>> usual
> "/wp-admin/options-general.php?page=plugin_dir/plugin_file.php"
> >> >>> seems to not be working and does not load the plugin's options
> pages.
> >> >>>
> >> >>> But this might just be because it's not ready yet.
> >> >>>
> >> >>> Stephane
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Sep 14, 2008, at 7:02, Frank Bueltge wrote:
> >> >>>
> >> >>>> I use in a lot of plugins with mayx options the html of the
> metaboxes,
> >> >>>> open/cles div-areas.
> >> >>>> This ist not a nice css in 2.7
> >> >>>>
> >> >>>> Why ist not possible to set for the user a design?
> >> >>>>
> >> >>>> Liebe Grüsse
> >> >>>> Frank
> >> >>>> ______________________________
> >> >>>> Mein Buch: WordPress - Weblogs einrichten und administrieren | ISBN
> >> >>>> 978-3-937514-33-8
> >> >>>>
> >> >>>> bueltge.de
> >> >>>> kvfl.com
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> On Sun, Sep 14, 2008 at 12:20 PM, Viper007Bond
> >> >>>> <viper at viper007bond.com> wrote:
> >> >>>>> I like how everyone is commenting on the looks of the admin area
> >> >>>>> and it's
> >> >>>>> not even done yet.
> >> >>>>>
> >> >>>>> As for a new options page, all of my plugins work just fine in 2.7
> >> >>>>> with no
> >> >>>>> modifications. Not quite sure what you mean.
> >> >>>>>
> >> >>>>> On Sun, Sep 14, 2008 at 3:06 AM, Frank Bueltge <frank at bueltge.de>
> >> >>>>> wrote:
> >> >>>>>
> >> >>>>>> I think the actually verson of the design in backend is very
> ugly.
> >> >>>>>> The
> >> >>>>>> html and CSS is very bad und man gugs.
> >> >>>>>> Th deisgn is also hard for plugin-authors. Many plugins is must
> >> >>>>>> write
> >> >>>>>> a new page for options.
> >> >>>>>> I hope, this is noct the end of the design in  backend and i hope
> >> >>>>>> alos, the user can change on your progile to the last 3 design
> >> >>>>>> (WP2.3
> >> >>>>>> and WP 2.5 classic and frsh)
> >> >>>>>>
> >> >>>>>> Sorry for my bad english!
> >> >>>>>>
> >> >>>>>> Liebe Grüsse
> >> >>>>>> Frank
> >> >>>>>> ______________________________
> >> >>>>>> Mein Buch: WordPress - Weblogs einrichten und administrieren |
> ISBN
> >> >>>>>> 978-3-937514-33-8
> >> >>>>>>
> >> >>>>>> bueltge.de
> >> >>>>>> kvfl.com
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> On Sun, Sep 14, 2008 at 6:47 AM, Jacob Santos <
> >> wordpress at santosj.name
> >> >>>>>> >
> >> >>>>>> wrote:
> >> >>>>>>> I do not share you lack of distaste in Crazyhorse. I do think it
> is
> >> >>>>>> almost
> >> >>>>>>> humorous that there are many bugs just testing through it. I
> >> >>>>>>> haven't
> >> >>>>>> filed
> >> >>>>>>> any bug reports because there are just too many that they would
> be
> >> >>>>>>> overwhelmed. I'm going to take note of them and wait until the
> >> >>>>>>> freeze is
> >> >>>>>>> conducted before filing the tickets. Hopefully, they will be
> >> >>>>>>> corrected.
> >> >>>>>> It
> >> >>>>>>> is the second half of September and while it is far more stable
> >> >>>>>>> than when
> >> >>>>>> I
> >> >>>>>>> first looked at it, I'm still not going to upgrade.
> >> >>>>>>>
> >> >>>>>>> To me personally, the level of customization within the various
> >> >>>>>>> pages is
> >> >>>>>>> enjoyable. I have to say, I find some sort of happiness being
> >> >>>>>>> able to
> >> >>>>>> remove
> >> >>>>>>> tags column, as well as other columns that I can see myself not
> >> >>>>>>> using on
> >> >>>>>>> some WordPress projects.
> >> >>>>>>>
> >> >>>>>>> I think too many people are seeing this as a new administration
> >> >>>>>>> panel
> >> >>>>>>> instead of what it is meant to be, an iteration of the current
> >> >>>>>>> administration panel. Yeah, there are many changes being made,
> >> >>>>>>> but many
> >> >>>>>> of
> >> >>>>>>> them are needed to ensure the ease of usability. Many parts are
> >> >>>>>>> intuitive
> >> >>>>>>> and I suggest giving the newborn some time before judging it
> "ugly"
> >> >>>>>> perhaps
> >> >>>>>>> it will grow up to be quite beautiful.
> >> >>>>>>>
> >> >>>>>>> If you are more specific in your objections, I'm sure the team
> >> >>>>>>> might be
> >> >>>>>> able
> >> >>>>>>> to do something about it. They are currently collecting input on
> >> >>>>>>> whether
> >> >>>>>> the
> >> >>>>>>> "New Post" button should be at the top or where the menu is.
> That
> >> >>>>>>> was
> >> >>>>>> added
> >> >>>>>>> after the testing and so there haven't been enough input on
> which
> >> >>>>>> location
> >> >>>>>>> it should be.
> >> >>>>>>>
> >> >>>>>>> Jacob Santos
> >> >>>>>>>
> >> >>>>>>> Aaron Brazell wrote:
> >> >>>>>>>>
> >> >>>>>>>> Hey folks-
> >> >>>>>>>>
> >> >>>>>>>> I've been using trunk on one of my blogs and tracked the
> >> >>>>>>>> Crazyhorse
> >> >>>>>> stuff.
> >> >>>>>>>> I
> >> >>>>>>>> guess part of me hoped that there would be some sense brought
> to
> >> >>>>>>>> it, but
> >> >>>>>>>> then everything I hated about it was merged into trunk. No
> >> >>>>>>>> offense to
> >> >>>>>>>> anyone
> >> >>>>>>>> who did any of the work, but it just doesn't feel right.
> >> >>>>>>>> Thinking it
> >> >>>>>> might
> >> >>>>>>>> just be me, I got second opinions. It just doesn't feel right.
> >> >>>>>>>>
> >> >>>>>>>> Granted, we're on this course now and there's no turning back.
> >> >>>>>>>> It would
> >> >>>>>> be
> >> >>>>>>>> nice, though, if there were a option to use the more
> traditional
> >> >>>>>>>> backend
> >> >>>>>>>> instead. Something along the lines of the Fresh/Classic color
> >> >>>>>>>> scheme
> >> >>>>>>>> switcher. Thoughts?
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>> _______________________________________________
> >> >>>>>>> wp-hackers mailing list
> >> >>>>>>> wp-hackers at lists.automattic.com
> >> >>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>> _______________________________________________
> >> >>>>>> wp-hackers mailing list
> >> >>>>>> wp-hackers at lists.automattic.com
> >> >>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >>>>>>
> >> >>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>> Viper007Bond | http://www.viper007bond.com/ |
> >> http://www.finalgear.com/
> >> >>>>> _______________________________________________
> >> >>>>> wp-hackers mailing list
> >> >>>>> wp-hackers at lists.automattic.com
> >> >>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >>>>>
> >> >>>> _______________________________________________
> >> >>>> wp-hackers mailing list
> >> >>>> wp-hackers at lists.automattic.com
> >> >>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >>>
> >> >>> _______________________________________________
> >> >>> wp-hackers mailing list
> >> >>> wp-hackers at lists.automattic.com
> >> >>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >> --
> >> >> Aaron Brazell
> >> >> web:: www.technosailor.com
> >> >> phone:: 410-608-6620
> >> >> skype:: technosailor
> >> >> twitter:: @technosailor
> >> >>
> >> >> _______________________________________________
> >> >> wp-hackers mailing list
> >> >> wp-hackers at lists.automattic.com
> >> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >>
> >> >>
> >> >
> >> > _______________________________________________
> >> > wp-hackers mailing list
> >> > wp-hackers at lists.automattic.com
> >> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Xavier Borderie
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >>
> >
> >
> >
> > --
> > Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
>
> --
> Xavier Borderie
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/

More information about the wp-hackers mailing list