The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
I've been here brfore preaching about using xHTML and CSS to layout pages instead of tables. One or two of you were sceptical about this method, and a few of you have seen the simple CSS/xHTML layout I have used for my own site... But I had to show you this...
http://wip.blackwellpublishing.com/wwwsubjsitescorp/
It's only a concept a the moment, but the layout is generally the final product. But check out source code (minus comments, about 130 lines), almost a 3rd less than if built using tables for layout. Look at the CSS for the #leftcolumn, #centercolumn and #rightcolumn, tru static/fluid layout.
Rob... before you ask, it works perfectly in IE6, NN6.22/7 and Moz 1.2 still a few minor positioning bugs in IE5/5.5, but this is due to it's box model handling.
I rock...
CSS rocks, this is the future of website design...
http://wip.blackwellpublishing.com/wwwsubjsitescorp/
It's only a concept a the moment, but the layout is generally the final product. But check out source code (minus comments, about 130 lines), almost a 3rd less than if built using tables for layout. Look at the CSS for the #leftcolumn, #centercolumn and #rightcolumn, tru static/fluid layout.
Rob... before you ask, it works perfectly in IE6, NN6.22/7 and Moz 1.2 still a few minor positioning bugs in IE5/5.5, but this is due to it's box model handling.
I rock...
CSS rocks, this is the future of website design...
Page:
cjh wrote:
> Mind if I ask, what "voice-family" does?
simple Link: http://www.blooberry.com/indexdot/css [space] /properties/aural/voicefam.htm
Or explaination from: http://www.glish.com/
"IE5x PC mis-implements the box model. Because of that we sometimes have to perform a little CSS trickery to get pixel-perfect display across Browsers. The following bit of code was proposed by Tantek Celik, and it preys upon a CSS parsing bug in IE5x PC that will prematurly close a style rule when it runs into the string "\"}\"". After that string appears in a rule, then, we can override previously set attribute values and only browsers without the parse bug will recognize the new values. So any of the name-value pairs above this comment that we need to override for browsers with correct box-model implementations will be listed below."
"We use the voice-family property because it is likely to be used very infrequently, and where it is used it will be set on the body tag. So the second voice-family value of "inherit" will override our bogus "\"}\"" value and allow the proper value to cascade down from the body tag."
"The style rule immediately following this rule offers another chance for CSS2 aware browsers to pick up the values meant for correct box-model implementations. It uses a CSS2 selector that will be ignored by IE5x PC."
> Mind if I ask, what "voice-family" does?
simple Link: http://www.blooberry.com/indexdot/css [space] /properties/aural/voicefam.htm
Or explaination from: http://www.glish.com/
"IE5x PC mis-implements the box model. Because of that we sometimes have to perform a little CSS trickery to get pixel-perfect display across Browsers. The following bit of code was proposed by Tantek Celik, and it preys upon a CSS parsing bug in IE5x PC that will prematurly close a style rule when it runs into the string "\"}\"". After that string appears in a rule, then, we can override previously set attribute values and only browsers without the parse bug will recognize the new values. So any of the name-value pairs above this comment that we need to override for browsers with correct box-model implementations will be listed below."
"We use the voice-family property because it is likely to be used very infrequently, and where it is used it will be set on the body tag. So the second voice-family value of "inherit" will override our bogus "\"}\"" value and allow the proper value to cascade down from the body tag."
"The style rule immediately following this rule offers another chance for CSS2 aware browsers to pick up the values meant for correct box-model implementations. It uses a CSS2 selector that will be ignored by IE5x PC."
cjh wrote:
> Yeah, not bad I suppose :).
>
> How long did that take to create?
About 4 hours. The hard part is the box positioning and relationships to the other page elements as well as stacking it in an order that a non CSS/xHTML (NN4) browser can still render in a logical format.
> Yeah, not bad I suppose :).
>
> How long did that take to create?
About 4 hours. The hard part is the box positioning and relationships to the other page elements as well as stacking it in an order that a non CSS/xHTML (NN4) browser can still render in a logical format.
Mind if I ask, what "voice-family" does?
Yeah, not bad I suppose :).
How long did that take to create?
How long did that take to create?
I've been here brfore preaching about using xHTML and CSS to layout pages instead of tables. One or two of you were sceptical about this method, and a few of you have seen the simple CSS/xHTML layout I have used for my own site... But I had to show you this...
http://wip.blackwellpublishing.com/wwwsubjsitescorp/
It's only a concept a the moment, but the layout is generally the final product. But check out source code (minus comments, about 130 lines), almost a 3rd less than if built using tables for layout. Look at the CSS for the #leftcolumn, #centercolumn and #rightcolumn, tru static/fluid layout.
Rob... before you ask, it works perfectly in IE6, NN6.22/7 and Moz 1.2 still a few minor positioning bugs in IE5/5.5, but this is due to it's box model handling.
I rock...
CSS rocks, this is the future of website design...
http://wip.blackwellpublishing.com/wwwsubjsitescorp/
It's only a concept a the moment, but the layout is generally the final product. But check out source code (minus comments, about 130 lines), almost a 3rd less than if built using tables for layout. Look at the CSS for the #leftcolumn, #centercolumn and #rightcolumn, tru static/fluid layout.
Rob... before you ask, it works perfectly in IE6, NN6.22/7 and Moz 1.2 still a few minor positioning bugs in IE5/5.5, but this is due to it's box model handling.
I rock...
CSS rocks, this is the future of website design...
Page: