Page 2 of 2

Posted: Fri Mar 02, 2007 12:46 am
by garvinhicking
Hi owen!
Yes, I'm sure. To be sure, using EditCSS, I deleted the main style.css, so all I was left with was ltgrey_style.css. That is where I was making the changes to see what would work.... and it only worked as I described.
I really suggest while testing the things you do to NOT use editcss, but edit the .css files manually via an editor.EditCSS might screw with paths, so you should always edit the fresh ones to test things. EditCSS should only be used to tweak existing thingsin a latter phase?
I didn't start out on this path thinking I was going to become a template designer, but I am slowly being coaxed into it!!! :lol: For starters, I'll probably set up a subdomain on my boating site. Not idea, but good enough for this.
And I really enjoy the path you're taking! Look at the huge progress you've made from your first posting here to the things you'Re at now. WIth my responses I try to push you even more, because I'm absolutely certain you're on the right track and work out many things on your own. I very much think you can be an active part in the future of Serendipity, which makes me very cheerful :)

If you have that testsite online somewhere, it would help me a lot to see what things are happening :)

Best regards,
Garvin

Posted: Fri Mar 02, 2007 12:57 am
by Don Chambers
EditCSS is a tool you turned me onto about a year ago.... and I use it extensively. In this case, perhaps it is messing around with the paths. I will not know that until I start to slice up my style.css, removing colorset specific tags into new css files, leaving behind only the core tags.

The template I am currently working on is still very conceptual, which is why there has never been a public link to it. In some ways, it is parallel to BulletProof, in others, it is an experiment in styling. Whatever that particular distinction, it is defintely a learning experience, and I am doing my best to share every conclusion that shakes out of that experience.

Of course, with this inspiration provided by you, and so many of the other experts hanging around this project, I now have NO LIFE BECAUSE I'M GLUED TO MY COMPUTER TRYING TO FIGURE THIS STUFF OUT!!!! :lol: :lol: :lol:

Of course, the really SICK thing is that I actually enjoy it!!! :wink:

Anyway, I wil try to get a test site up and running as soon as I can. Would make things like this a bit easier. I do not want a new domain just yet, so will probably try a subdomain. Any issues with that if I have a subdomain on my boating site (http://www.chicagoloopcruise.com), where that site has an older version of s9y installed in the root? And YES - I KNOW!! I need to upgrade that site to 1.1. If you guys hadn't sucked me into this black hole of templating, I would have done that already!!! 8)

Posted: Sat Mar 03, 2007 12:44 am
by Don Chambers
Owen Stubbs wrote:
garvinhicking wrote:Hi!

Since the addiotnal style sheets are referenced directly inside the CSS directory (instead of being in the base directory when style.css is loaded through PHP) you can use relative paths for all background images in additionally linked CSS files, like:

Code: Select all

.yourclass {
background-image: url(img/mypic.gif);
}
So you don't need to use {TEMPLATE_PATH} as your CSS is already within that directory.:)

HTH,
Garvin
Does not work in EditCSS as you describe. I will need to do a whole lot of editing before I know whether or not it works in the css files that way.

EDIT: url('templates/template_folder_name/img/mypic.gif') works in EditCSS. Note the quotes and the path all the way to templates. This is not very desirable since I could easily move this stuff around, or possibly rename the template folder.
Just for closure on this issue - it does work the way Garvin described. When the additional stylesheet is loaded, which cannot use the variable {TEMPLATE_PATH}, all that is needed for a background is:

Code: Select all

background: #ddd url('img/mypic.gif') repeat-x 0 0%;