Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

more css support, step 1

by jdporter (Canon)
on Jan 06, 2008 at 00:22 UTC ( #660598=pmdevtopic: print w/ replies, xml ) Need Help??
jdporter has raised the following topic:

I wonder what, if any, reservations the patch appliers have about my Red CSS - (patch) and kin. They're very small changes with potentially major benefit. Though, of course, they're but one of a slew of similar steps toward fully css-based PM theming.

A word spoken in Mind will reach its own level, in the objective world, by its own weight

Comment on more css support, step 1
Re: more css support, step 1 (point?)
by tye (Cardinal) on Jan 06, 2008 at 07:10 UTC

    I don't have much to offer, but since you asked, I'll say what little I have to say. My immediate reaction is two-fold: 1) "I'm supposed to have some clue what the point is based on what?!" 2) That patch at least looks fairly harmless.

    But now that I write that I think the "harmless" assessment is nearly tied to the "pointless" assessment. If it isn't adding a completely new item to CSS then the patch might have some impact besides making way for some future idea. But I have little clue what the immediate impact would be or what future ideas are hoped for so I go back to not knowing what the point is.

    Update: I looked for a reply (to the linked patch) or at least that was my intent so I'm disappointed in myself for not seeing the reply. It answered my questions.

    - tye        

      1) "I'm supposed to have some clue what the point is based on what?!"

      Point is, there should be as little tag attribute values hard-coded into the HTML; instead they should be relegated to CSS directives. That has the benefit that layout and appearance can be tweaked and improved on a site or per-user basis (by individual CSS settings) without having to change the least bit of the PerlMonks engine code (see the CSS Zen Garden for what's possible with CSS).

      So, no, those changes aren't pointless, and ++ to jporter for his work.

      --shmem

      _($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                                    /\_¯/(q    /
      ----------------------------  \__(m.====·.(_("always off the crowd"))."·
      ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

      The overarching point, or goal, is to replace all the hard-coded style with CSS classes (or IDs, if/where appropriate). I identified clr_highlight as one such style parameter which could easily be replaced with CSS. It is only one small step toward the goal, but it's an easy one, a viable first step. The patches (Red CSS - (patch) and kin) are only one half of this first step; the second half is to modify those places where clr_highlight is used to use the CSS classes (tr.post_head, tr.highlight, table.highlight) instead.

      Do we need to talk about why CSS is better than hard-coded style?

      A word spoken in Mind will reach its own level, in the objective world, by its own weight

        Applied

Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2014-10-25 09:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (142 votes), past polls