Richard,
This is rather trivial to do with an extension. Write your desired CSS,
put it in your extension public/stylesheets directory. Then put
something like this in your extension's activate method:
SiteController.class_eval do
before_filter :customize_admin_css
def customize_admin_css
include_stylesheet 'my_stylesheet'
end
end
Obviously you'd want to name your stylesheet something else. Hope this
is helpful!
Sean
Richard Hurt wrote:
> Putting the controls on a sidebar is OK with me. I would even be fine with
> a smaller text for the page title and various controls. I'm screen height
> challenged, not blind. :)
>
> Hmmm...what about a way to customize the CSS of the Admin pages for each
> install? Would that work? It wouldn't even have to be anything fancy like
> a table in the DB, just a static file on the server would work for me. We
> could then change the look & feel of the pages pretty easily and to fit
> within our own guidelines.
>
> Later...
> Richard
>
> On Dec 2, 2007 3:08 PM, Ryan Heneise <[EMAIL PROTECTED]> wrote:
>
>
>> I think I prefer having the buttons underneath the form, because it is
>> more standard and fits the open-edit-save workflow. Moving the buttons
>> to the top breaks with convention.
>>
>> What about a 2-column layout (similar to this:
>> http://www.madebyfrog.com/news/preview_layout_for_version_1)
>> , moving the meta-data form inputs to the second column? If some of
>> the metadata were moved out of the way horizontally, then the body of
>> the form could be shorter.
>>
>>
>>
>> On Dec 2, 2007, at 6:30 AM, Andrew Neil wrote:
>>
>>
>>>> 5. Can we make the edit page a little more friendly for those of us
>>>> without 1700x2400 displays? :)
>>>>
>>> I feel your pain. A couple of thoughts:
>>>
>>> * "Save Changes" and "Save and continue" buttons could go at the top,
>>> perhaps level with the "Edit Page" heading, but floated to the right.
>>> * The same two buttons could be given access keys, e.g. S and C, so
>>> that you can trigger them with a key command, rather than pushing
>>> them with your cursor.
>>>
>>> A
>>> _______________________________________________
>>> Radiant mailing list
>>> Post: Radiant@lists.radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>>>
>> _______________________________________________
>> Radiant mailing list
>> Post: Radiant@lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>>
> _______________________________________________
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
>
_______________________________________________
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
