Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I have only one design idea... Let each user build his/her own CSS style. I even have the idea on how to implement this with minor growing pains, although it would require that all of the bgcolor, color, etc tags be replaced with class="whatever" tags. On the HTML side, we could do a
<head> <title>$current_node</title> <link rel="stylesheet" type="text/css" href="/style.pl?style=$user_pk" + title="Default Styles" media="screen"> </head> <body class="myBody"> <!-- ... and so forth... -->
and on the database side, a table like
create table user_styles ( user_pk varchar2(x) primary key references whatever.user_pk, mybody varchar2(32), mytable varchar2(32), mytr varchar2(32), mytd varchar2(32), myth varchar2(32), mylink etc, etc, etc, );
I'm not sure I'm making myself clear, but if you need a sample with source I can soupe something up... (and if you need a reference on my so called design skillz, please check out my website.

#!/home/bbq/bin/perl
# Trust no1!


updated idea:
...and if you don't feel like creating your own style, you could always select from a library of presets and/or have a "dropdown" or something for other monks themes.

Maybe even a "most popular themes" thingy...

In reply to User Requests Quest - CSS "themes" by BBQ
in thread User Requests Quest by vroom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (6)
As of 2024-04-23 10:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found