Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Journal of tf23 (175)

Thursday May 22, 03

Slash CSS Theme

06:23 PM
Slash Plugins and Themes

Two days ago I got fed up with Slash not using CSS. Don't get me wrong - I'm not complaining - I'm dearly grateful that Slash's src is available as a backend; it's saved me many many hours of coding.

However, it would be *so* much better with CSS.

So, I started converting. Yes, I know pty started doing this recently, and yes, I hate to double up on a project. (pty, just incase, I'm not trying to one up you are anything even remotely close to that).

I just couldn't take it anymore. I had to give it a shot.

I think pty's project and mine differ in that he's going strict, while I'm not.

Anyway, I have made some progress. Infact, I've got to the point where I needed to modify plugin's templates (specifically, the journalhead and Slash::Message's display_prefs; the problem was the userslashboxes on the right hand side. they were tr td'd, I needed to div them so I could throw them to the right in the style sheet).

Take a look at it: I don't intend to wack this test-site's db over the course of the next week or two, so get an account on it if you want and mess around.

If you're using a newer browser, you can use different style sheets. The "noboxen" has errors. The "coolbreeze" works quite well, but was a 15 minute hack from another site's css file (and yes, the columns are reversed on purpose). Using Konqueror - it's under the view menu, with Moz it's under the view menu too).

If you are at all interested in this, please post and let me know. It would be great to get some feedback. It would be even better to get some *help* with it. And it would be greater still to get some feedback from the OSDN guys as to was I could make this easier for them to possibly use in the future... hint? hint? :)

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • hehe... When I was running a slash 1 series site I created a stylesheet and manually forced it as an include in the page header... I always wondered why there wasn't css support but figured since a style sheet wasn't too difficult to cook up manually never bothered writing it in anywhere in my version of slash.

    Is your css plugin running the info from the db or does it just write a css file from form data?
    • The stylesheets are in the site's theme. It's not in the db, since that would run-around css's 'download the css once, surf the site forever' benefits.

      lottadot []
      • Not what I was thinking exactly.

        I was figuring that your script was a configuration utility that stored the info in a table and would write/rewrite a slashsite.css file whenever you update it, after that it wouldn't change until next time an admin makes a change and forces it to update.

        I wrote something like that for a client not so long ago in vb/asp (please don't throw food...) and it worked out pretty cool.
        • Ah, I see what you're saying.

          Yes, that would be a plugin many people would find useful I'd bet.

          This is just a theme. No code. Just html/css.

          It's up on our cvsweb, you can check it out, at lottadot [].

          I honestly don't know what'll really happen with this. I loved pty's approach, using all the web content accessibility guidelines [].
          Some parts of mine adhear to that, but not all. I think that's truely the "right" way to do it. But that's a ton of work. Maybe over time it can get there...

          lottadot []
          • Hoho, seems like someone else understands how nice it would be to have the Slash templates working nicely with CSS :)

            I think that I could make a stable / usable release of my Strict Slash theme out in say 2-3 weeks.

            That would include valid XHTML 1.1 templates ( and a script to downgrade to HTML 4.01 Strict ), all Priority 1 and 2 checkpoints in the Web Content Accessibility Guidelines 1.0 [] satisfied ( and some Priority 3 checkpoints as well ). Validation of articles and comments. And a good-looking defau