Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:3

I need a slash....... theme

posted by Krow on 09:01 AM March 4th, 2002   Printer-friendly   Email story
I can't believe that no one has published another theme apart from the default? Can anyone giude me in the right direction?
Fish in ice
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.
  • I've found the *easiest* way to do a theme is to copy the slashcode theme, rename it's directory, change the THEME file (name and description) and then start changing the templates/htdocs/images files.

    This way, you are assured to have, at the start, all the minimal templates, tasks and scripts needed.
    lottadot []
    • How are you picking up on changes to the slash theme then?

      You can't grep a dead tree.
      • diffs, and scanning the output of cvs update :)

        I had originally been creating themes with the unmodified templates symlinked back to ../../slashcode/tempates/templatename.

        But that was before I was using CVS to control everything. Now I just import all the templates, and make a note of the date and go from there.

        lottadot []
        • I don't keep diffs currently. I have basic sets of templates for certain areas (like for instance users) and I just those across all sites.

          You can't grep a dead tree.
        • > But that was before I was using CVS to control everything. Now I just import all the templates, and make a note of the date and go from there.

          The best way IMHO, and the one I use for Slash-Italian, is to keep Slashcode releases in the vendor branch of your local CVS repository, and update the main trunk with your own modifications.

          For example, when slashcode will release 2.2.6, I will download, untar and do a
          cvs import -m 'Rel. 2.2.6' MySlash slashcode REL-2-2-6
          cd MySlash ;cvs update -j REL-2-2-5 -j REL-2-2-6
          (details omitted for brevity)

          It just means (1) "put rel. 2.2.6 in a vendor branch, tagged REL-2-2-6" and (2) "update MySlash with the differences between REL-2-2-5 and REL-2-2-6".

          See Fogel's explanation [], surely better than mine.


          Check out the Slash in Italian Project []

  • Themes are new. Slashcode has changed significantly in the last 12 months. Many (like myself) have changed the interface and are reluctant to upgrade all the templates (which is a minor PIA) to get their site up to the latest version.

    Copying the entire slashcode theme sounds like a good way to start though. When I finally *get* a theme going, I'll publish it.

  • If anyone's interested in working on a new theme, drop by #slash on and I/we will be happy to talk about what's involved. Personally I'd love to ship more than one theme with the tarball.
  • One of the biggest pains with running a Slash site is keeping all the templates up to date. Things change quite a bit in various code releases, and I think we all know about the lack of documentation on what exactly changes in templates. It would be very cool to have a CVS tree or something that we can see changes to.

    The template toolkit, dumping them out, and seeing if there is a difference is good. But, maybe a better idea would be to do a freeze on say a "slashcode basic" theme. Then, the only changes th


    It's either on the beat or off the beat, it's that easy.
  • [] intends to release a couple of themes for the slash community. one will be a stripped down version of the slashcode theme (good for starting a site from), and the other will be based on our current (news.openflows) design, which we plan on revamping after releasing the theme. we expect to release at least one, if not both by the end of March, if not earlier.