Re: More specific CSS rules for the admin

I could move all the class and id rules into layout.css, but they're still going to rely on the base tag rules defined in global.css. I might do that anyway, but I'm not sure I see how much it helps. Also, the way I have the import rules set up now, the more specific stylesheets actually import t

Re: More specific CSS rules for the admin

Am 10.04.2006 um 17:28 schrieb Wilson Miner: > That should be possible with the changes to stylesheets in magic- > removal. Almost, but not entirely. Observe: This mixes complet

Re: More specific CSS rules for the admin

I think it's great you were able to get that much mileage out of the admin styles in your app. If other people see a benefit in doing the same, you've certainly proven it's possible. I still don't consider it within the scope of the admin application to provide a public interface for your app. On

Re: More specific CSS rules for the admin

That should be possible with the changes to stylesheets in magic-removal. Also, nothing should be preventing you from copying the admin styles and modifying them to be specific to your own needs. On 4/10/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: > > Am 07.04.2006 um 17:03 schrieb Wilson Mi

Re: More specific CSS rules for the admin

Am 07.04.2006 um 17:03 schrieb Wilson Miner: > I'm open to being convinced otherwise, but I don't see it as within > the scope of the admin CSS to accomodate being embedded in other > interfaces. > > We've discussed this internally before and the general consensus was > that if you're reusing the

Re: More specific CSS rules for the admin

> Take zyons.com for example, a open source forum app I'm developing. I grabbed > the admin template modified it slightly and pushed it out. zyons.com is about the level of admin L&F customization that I was thinking about - tweaking CSS & templates just a little. Even just colors. -rob --~-

Re: More specific CSS rules for the admin

On 4/10/06, oggie rob <[EMAIL PROTECTED]> wrote: > > > My point is not that you should or shouldn't have to write your own form > > code. My point is that (in my mind anyway) needing to write your own styles > > is not a barrier to reusing the admin form code. > > Yes, I agree. Like I mentioned,

Re: More specific CSS rules for the admin

> My point is not that you should or shouldn't have to write your own form > code. My point is that (in my mind anyway) needing to write your own styles > is not a barrier to reusing the admin form code. Yes, I agree. Like I mentioned, the only limitation I've faced with the styles that come wi

Re: More specific CSS rules for the admin

My point is not that you should or shouldn't have to write your own form code. My point is that (in my mind anyway) needing to write your own styles is not a barrier to reusing the admin form code. Styling forms (once) is a lot less tedious than writing them (over and over). And style is somethin

Re: More specific CSS rules for the admin

> I'm open to being convinced otherwise, but I don't see it as within the scope > of the admin CSS to accomodate being embedded in other interfaces. Not to throw fuel on the fire, but for some applications in particular we're stuck between a rock and a hard place, and the admin interface is the

Re: More specific CSS rules for the admin

Christopher Lenz wrote: > Am 07.04.2006 um 18:30 schrieb Rudolph: >> It could be solved by putting the django-admin stuff inside a tag with >> a django-admin class. Then ".django-admin p" or ".django-admin >> #content" will format only the admin stuff and not your site. > > No, because the admin

Re: More specific CSS rules for the admin

Am 07.04.2006 um 18:30 schrieb Rudolph: > It could be solved by putting the django-admin stuff inside a tag with > a django-admin class. Then ".django-admin p" or ".django-admin > #content" will format only the admin stuff and not your site. No, because the admin style sheets use "p" as a selecto

Re: More specific CSS rules for the admin

On 4/7/06, Rudolph <[EMAIL PROTECTED]> wrote: > It could be solved by putting the django-admin stuff inside a tag with > a django-admin class. Then ".django-admin p" or ".django-admin > #content" will format only the admin stuff and not your site. It could be, but I think I'm with Wilson in feeli

Re: More specific CSS rules for the admin

It could be solved by putting the django-admin stuff inside a tag with a django-admin class. Then ".django-admin p" or ".django-admin #content" will format only the admin stuff and not your site. Rudolph --~--~-~--~~~---~--~~ You received this message because you

Re: More specific CSS rules for the admin

I'm open to being convinced otherwise, but I don't see it as within the scope of the admin CSS to accomodate being embedded in other interfaces. We've discussed this internally before and the general consensus was that if you're reusing the admin templates and code in your public site (which is g

More specific CSS rules for the admin

Hi all, (this one is mostly for Wilson, I guess) I see there's been some refactoring of the CSS for the admin app going on, so this might be a good time for a related change: Many of the style rules used in the admin CSS have very generic selectors (there are styles for p, ul, etc). In my c