Brainstorming: What do we "need" template-wise?

[yellowled]

Oops, big brother's watching

If BP should at any point be added to our main release/repository, then GPL would deny that possibility. Core s9y templates would need to be BSD licensed.

Just wanted to drop that in, but the call is yours of course.

Well, if you'd be willing to add it to the main release, I think everyone including me would be honored and also fine with a BSD license.

However, you probably wouldn't want to include the framework itself in the main release but rather a new default based on it, right? I'm pretty sure Carl would agree to redo his Serendipity v3.0 template based on BP once he finds time, which would be suited better to include with the main release IMHO. I think it would be better to put BP itself on spartacus (or even sourceforge or something).

YL

[d_cee]

Hi guys

I too have enjoyed the intercontinental collaborative experience - although I hope Don hasn't caught my virus from a couple of weeks ago working with us anyway - get well soon Don!

I too am fine with whatever license Garvin suggests. My feeling on distribution is that bulletproof should be left as it is, we add a couple of sample coloursets which demonstrate how to use it and that's it. Carl's default theme would then stay as it is - and bulletproof, as is, is then included in the distribution as an ideal framework for template design.

Documentation can then be added to the s9y.org user documentation as and when we get it done and I've got a couple of coloursets - one with graphics and one without - both kinda half done - which I can try and finish.

howzat? - as we say during the Cricket world cup!

cheers

Dave

[Don Chambers]

I have absolutely no idea what each of those license types are. What are the implications? Also - are you talking about whether BP exists solely on Spartacus vs. included as one of the templates in 1.2???

[yellowled]

I have absolutely no idea what each of those license types are. What are the implications?

http://en.wikipedia.org/wiki/BSD_license vs. http://en.wikipedia.org/wiki/GNU_General_Public_License - this stuff is rather complicated. I can't explain in two sentences what the differences are, but I understand that in order to be shipped with the s9y tarball, bulletproof would have to be licensed under the BSD license simply because s9y itself is licensed under it. I'm fine with that.

Also - are you talking about whether BP exists solely on Spartacus vs. included as one of the templates in 1.2???

Yes. I'd be fine with including it as Dave suggested (in case Garvin wants to do that, which he seems to ), as long as I don't have to do the colorset stuff, simply since I'm gonna be pretty busy the next 10-14 days, and I don't know how much s9y stuff I will get done over that period of time. But since Dave just volunteered to do that , let's do it that way. So, go ahead Dave!

YL

[Don Chambers]

I read the differences on the licenses too, but was looking for a simple sentence or 2 explanation of what the real difference is. Guess I really do not care one way or the other!!

I thought I spotted one or 2 things I wanted to investigate further in BP before it is considered a "wrap". Will get to that ASAP, but it does not really sound like anything is urgent right now given the fact that you are fairly unavailable the next several days/weeks.

[garvinhicking]

Hi!

The key difference in BSD license is that everything based on BSD license can be:

* Commercially used without charge
* Modified without the need to give back changes to the public

That makes protecting intellectual property when being used in commercial surroundings easier. But on the other hand, it lesser protects the intellectual property of the original author.

HTH,
Garvin

[yellowled]

I thought I spotted one or 2 things I wanted to investigate further in BP before it is considered a "wrap".

Somehow, I saw this coming ...

Will get to that ASAP, but it does not really sound like anything is urgent right now given the fact that you are fairly unavailable the next several days/weeks.

Well, we'll see how badly I'm out over the next couple of days. But in general, I'd say you can take your time.

YL

[yellowled]

Well, we'll see how badly I'm out over the next couple of days.

Well, I found the time to include some styles from the default stylesheet into base.css we had forgotten - msg_notice etc. Also prepared info.txt and index.tpl a little for framework use, i.e. changed it a little so that people customizing this just have to enter their template name and author.

I figured this wasn't worth another updated zip, I'm gonna wait what additions Don has in mind.

YL

[Don Chambers]

If you can believe it, I still have not fully recovered. Sorry guys. I realize I was hitting this thing hard for a few weeks, now I am being hit hard. Must be the computer-god's revenge! LOL! I have another issue - the primiary reason I even know about s9y is due to an annual boating event I organize. That thing is coming up in 5 weeks, and right now is crunch time for various components of that event.

I will do my best to investigate the 1 or 2 issues I noticed by the end of the weekend. It could very well be nothing at all, but, without going into detail, I still want to look at 2 things. Maybe 3.

Maybe I just need to drink a few more beers, then I will never remember what the issues were in the first place!!!

[yellowled]

I will do my best to investigate the 1 or 2 issues I noticed by the end of the weekend. It could very well be nothing at all, but, without going into detail, I still want to look at 2 things. Maybe 3.

You might also point out what these things actually are, so Dave and I could take some workload off you ..?

Maybe I just need to drink a few more beers, then I will never remember what the issues were in the first place!!!

Well, there's a German proverb saying warm(!) beer has some healing powers ... but that's just disgusting, right?

YL

[Don Chambers]

No warm beer for me! Good news is that I am back to nearly 100%. Sneezing all over, probably spreading germs, but at least I can breath again and almost think clearly.

I took a screen shot of the things that caught my attention. Here it is: http://chicagoloopcruise.com/library/s9 ... sue323.jpg

This is on a PC, with IE6. I have reduced the window size, probably in the neighborhood of 800 px or so. Problem does not become obvious until you drop the window size down into this range.

I used background colors: #wrapper yellow, sidebars are green, sidebarcontent is light grey, and footer is red.

See that the sidebar content, header, and footer are all narrower than what they should be.... with one very obvious exception - the freetag plugin. Perhaps it holds the clue.

This is either very simple, or very complicated. Whatever it is, I cannot find it. If I, or one of you guys do, I will probably feel like an idiot - I cannot get over the feeling that it is right in front of me!

Another issue regarding the use of "justify" for paragraphs. IE has an issue with this, and I have encountered before. Suggest p text (style.css) just be "left" justified, or not defined by css at all unless there is a really good reason for it.

Final thing (final for now that is!) - max-width (#wrapper) does not work in IE6. Should it be dropped completely?

This first issue is pissing me off. I just KNOW that little sucker is hiding somewhere and taking advantage of me. I will show no mercy if/when I find this thing!

[Don Chambers]

First of all, when I set my testblog to BP, the problem is not nearly as pronounced as it is when I view YL's test site. I have other issues with my test site, and perhaps that explains it.

Anyway, the problem SEEMS to be caused by #wrapper width: 95%. When NO width is set, the problem completely disappears. Setting width (and margin: 1em auto; on body SEEMS to be better, but not completely.

I keep saying "SEEMS" because I cannot draw an absolute conclusion due to some of the irregularites with my localhost test site.

[yellowled]

This is on a PC, with IE6. I have reduced the window size, probably in the neighborhood of 800 px or so. Problem does not become obvious until you drop the window size down into this range.

I think I have experienced similar problems - I have started a new template for my blog which is less scarce than the original bulletproof. I remember seeing something similar in IE 6 (very little), IE 5.5 and IE 5 (more) - a white vertical line or border on the right side.

Another issue regarding the use of "justify" for paragraphs. IE has an issue with this, and I have encountered before.

Dropped that, now using text-align: left. This is just personal taste, I like justify better.

Final thing (final for now that is!) - max-width (#wrapper) does not work in IE6. Should it be dropped completely?

I think so, seems to be especially bad in combination with the wrapper width. I'll play around with that a little on Monday - gotta paint a living room first

YL

[yellowled]

I'll play around with that a little on Monday - gotta paint a living room first

Done. I hate redecorating.

Okay, I think I have solved this, at least it should suffice now according to my tests. I have lost the max-width for #wrapper altogether, put the 95% width in base.css, and added #wrapper { width: 950px; } to ie.css. IMHO, this is a suitable width for 1024x768. I have also put some temporary background colors in style.css to make it easier to check this out (of course, this only works if you set the blog to default colorset).

I have also included a favicon link in the head of the index.tpl - Robert Lender sort of requested that in the comments in my blog, and I think it makes sense.

Zipfile and sandbox updated, please check it/them out to see if I have nailed it this time

YL

[Don Chambers]

Regarding the width stuff, did you change anything other than what you specifically mentioned? I was still having difficulties specifically stating a width to IE, but your latest revisions do not show that same problem with a stated width in pixels. In IE, a percentage width still produces the same problem as before, so I am not sure this is really "solved". Also, the experimental template I was working on, while very different from BP in certain respects, does NOT have this problem. I guess I need to figure out why. That template does set a % width on a wrapper div, like BP. Setting BODY width in BP instead of #wrapper eliminates this problem, but I still need to figure out why my experimental template can do it on the wrapper, but BP cannot.

You must be using a screen width of 1024... right? I'm using a 19" LCD with a width of 1280. BIG difference between 950px and 95%.

IE actually assigns screen space to the countercode DIV even though the only content of it is a comment - that space disappears if you scroll down to page bottom, then reappears if you scroll up. Another wonderful fluke of IE. Perhaps it would be best to set the default value of that to false, even if you leave the comment. Also, what is the purpose of the elseif?

Code: Select all

{if $template_option.counter_code_toggle == 'true'}
   <div class="counter_code">{$template_option.counter_code}</div>
{elseif $template_option.counter_code_toggle == 'false'}
{/if}