[quote]and so I see no reasoning behind trying to force FF upon people when IE is also capable, though from a programming perspective, more effort is required, and too right to, if you plan on programming for a major website or even a minor website, you should be prepared to do all the coding required to make it a multi-browser operational website[/quote] Firstly, as a gaming website, the majority here actually uses non-IE browsers, from what I can tell. If not, it's very close. Also, Firefox is open-source. You may not see any reason to use it yourself, but others do, such as users, programmers ( who can make content for it, or learn from it ) , and web designers - and why have administrators go to extra trouble to support something that very few people actively prefer, most people are neutral about, and almost as many people are proactive about? Or atleast, that's what some would argue, were the term 'articulation' within their vocabularies. >_> Admittantly, the article Chui linked to is rather poorly written. edit: Also, I am using the Classic skin. Ftw! Although Carbonite looked pretty good. I'd just like if some fonts and buttons were smaller, and link colors changed slightly. The pinkish/orangish doesn't seem to work too well, to me.

Quote

and so I see no reasoning behind trying to force FF upon people when IE is also capable, though from a programming perspective, more effort is required, and too right to, if you plan on programming for a major website or even a minor website, you should be prepared to do all the coding required to make it a multi-browser operational website

Firstly, as a gaming website, the majority here actually uses non-IE browsers, from what I can tell. If not, it's very close.
Also, Firefox is open-source. You may not see any reason to use it yourself, but others do, such as users, programmers ( who can make content for it, or learn from it ) , and web designers - and why have administrators go to extra trouble to support something that very few people actively prefer, most people are neutral about, and almost as many people are proactive about?
Or atleast, that's what some would argue, were the term 'articulation' within their vocabularies. >_>
Admittantly, the article Chui linked to is rather poorly written.

edit: Also, I am using the Classic skin. Ftw! Although Carbonite looked pretty good.
I'd just like if some fonts and buttons were smaller, and link colors changed slightly. The pinkish/orangish doesn't seem to work too well, to me.

[QUOTE]if you plan on programming for a major website or even a minor website, you should be prepared to do all the coding required to make it a multi-browser operational website.[/QUOTE] Srsly, no offense, but a fuck you is in order here. CSS, HTML, JAVASCRIPT, XML has standards. As in, this should give you that result, and another thing will give you this result. It is super frustrating when things don't do what they should and you have to write hacks or change what you want to do solely because of IE. I used to have signatures float up into the signature a little bit, but I had to kill that because of IE. Like 10 different styles I had all had to be scraped because IE couldn't do things right. You don't find flaws because you don't do serious stuff with browsers. If you were writing a paper and using Word, and Ctrl + B gave you italic somethings, bold other times, and sometimes, simply erased your entire document, you'd get pretty damn pissed about it.

Quote

if you plan on programming for a major website or even a minor website, you should be prepared to do all the coding required to make it a multi-browser operational website.

Srsly, no offense, but a fuck you is in order here.
CSS, HTML, JAVASCRIPT, XML has standards. As in, this should give you that result, and another thing will give you this result. It is super frustrating when things don't do what they should and you have to write hacks or change what you want to do solely because of IE. I used to have signatures float up into the signature a little bit, but I had to kill that because of IE. Like 10 different styles I had all had to be scraped because IE couldn't do things right. You don't find flaws because you don't do serious stuff with browsers. If you were writing a paper and using Word, and Ctrl + B gave you italic somethings, bold other times, and sometimes, simply erased your entire document, you'd get pretty damn pissed about it.

My point was simply that if you plan on doing a major website then there has to be commitment to bring a service to a wide audience of people otherwise it wouldn't be a major website.

My point was simply that if you plan on doing a major website then there has to be commitment to bring a service to a wide audience of people otherwise it wouldn't be a major website.

I was talking about the Classic Skin.. And I do own FF, but it uses diffrent fonts which i stubbornly hate.

I was talking about the Classic Skin..

And I do own FF, but it uses diffrent fonts which i stubbornly hate.

I'll make classic more like it used to be. Shocko, still. IE makes things so much harder that at some times, I feel like blocking the browser entirely. Sometimes I get different results with the EXACT same version of IE on different computers. It's mind bogging. Besides the developmental problems, it is also heavily insecure.

I'll make classic more like it used to be.

Shocko, still. IE makes things so much harder that at some times, I feel like blocking the browser entirely. Sometimes I get different results with the EXACT same version of IE on different computers. It's mind bogging. Besides the developmental problems, it is also heavily insecure.

Could always make a splash screen giving a warning best suited for FF over IE =/ Edit: Some sites block FF from accessing it and require ya to use IE, others block IE and make you use FF. In the end I rather use FF since I get 0 popups from it and shit load if I loaded IE >_< As I see it, in the end up to IP which way he wants to code it. If he doesn't want to code for IE then don't force him, hell why not you code the IE side for site and he just code the FF side -_-; then ya can see how much work he puts into it.. sigh..

Could always make a splash screen giving a warning best suited for FF over IE =/

Edit: Some sites block FF from accessing it and require ya to use IE, others block IE and make you use FF. In the end I rather use FF since I get 0 popups from it and shit load if I loaded IE >_<

As I see it, in the end up to IP which way he wants to code it. If he doesn't want to code for IE then don't force him, hell why not you code the IE side for site and he just code the FF side -_-; then ya can see how much work he puts into it.. sigh..

I like all the special effects and such. But couldnt be as it was? It was so much easier and accurate. Yeah you would lose the special effects and what not. But isnt it best to have simplicity that works than color varity that hurts some others. Only way I can type is be constantly highlighting my text. I really dont desire to do that all the time in the future...

I like all the special effects and such. But couldnt be as it was? It was so much easier and accurate. Yeah you would lose the special effects and what not. But isnt it best to have simplicity that works than color varity that hurts some others. Only way I can type is be constantly highlighting my text. I really dont desire to do that all the time in the future...

Teach me how to code, and I will code the IE side. What codes are you using? I know a little about html, a nano-bit of PHP, I don't know javascript (I heard java and javascript are completely different) I know a fractional bit of CSS and yeah, if IP is willing to teach me what I need to know, i'd gladly code the IE side of things.

Teach me how to code, and I will code the IE side.
What codes are you using? I know a little about html, a nano-bit of PHP, I don't know javascript (I heard java and javascript are completely different) I know a fractional bit of CSS and yeah, if IP is willing to teach me what I need to know, i'd gladly code the IE side of things.

there is no ie side to stuff i *want* to do that i should be able to do... ie and ff don't get separated php or html side, it's css and javascript side... and you can only do so much with ie hacks...

there is no ie side to stuff i *want* to do that i should be able to do...
ie and ff don't get separated php or html side, it's css and javascript side... and you can only do so much with ie hacks...

css is IE right? isn't javascript too?

css is IE right? isn't javascript too?

What? No... CSS is cascading style sheets. div { background-color:orange } div.top { background-color: green } div > div { background-color: black } <div>Hola (orange)<div>Sup (black)</div></div> <div class="top">Hey (green)</div> <div>Hi (orange)</div> Javascript is client side scripting, which does things like the menu drop down boxes and ajax (shoutbox). IE mutilated JS horribly, by adding their own shit to the game without even making what JS is supposed to do work. I might have an update up in a couple minutes to fix the invisible text.

What? No... CSS is cascading style sheets.
div { background-color:orange }
div.top { background-color: green }
div > div { background-color: black }
<div>Hola (orange)<div>Sup (black)</div></div>
<div class="top">Hey (green)</div>
<div>Hi (orange)</div>

Javascript is client side scripting, which does things like the menu drop down boxes and ajax (shoutbox). IE mutilated JS horribly, by adding their own shit to the game without even making what JS is supposed to do work.

I might have an update up in a couple minutes to fix the invisible text.

I know that but I thought you said that CSS / Javascript were like browser dependant, I know how to do like scroll bars and text with CSS and things like that...

I know that but I thought you said that CSS / Javascript were like browser dependant, I know how to do like scroll bars and text with CSS and things like that...

I seriously think the original skin wasn't terrible. People convinced themselves it was so "horrible" that any change at all (even if it got worse) would've caused them to say it looked better. There has to be some psychological phenomenon at work here. ;o

I seriously think the original skin wasn't terrible. People convinced themselves it was so "horrible" that any change at all (even if it got worse) would've caused them to say it looked better. There has to be some psychological phenomenon at work here. ;o

cheeze. needs. shadows. (in the original.. whatever those things were when you hovered over them and it changed colors)

cheeze. needs. shadows. (in the original.. whatever those things were when you hovered over them and it changed colors)

i didn't mind the original, I hated it at first but it grew on me, i do however like these skins more.

i didn't mind the original, I hated it at first but it grew on me, i do however like these skins more.

Yeah, I liked the old one, but like these a bit better. Except for the purple. [QUOTE]Teach me how to code, and I will code the IE side. What codes are you using? I know a little about html, a nano-bit of PHP, I don't know javascript (I heard java and javascript are completely different) I know a fractional bit of CSS and yeah, if IP is willing to teach me what I need to know, i'd gladly code the IE side of things.[/QUOTE] Well, If you know a bit of CSS, you know it all. Just get a proper editing tool so you can cycle through different.. commands, I guess. Here's a brief intro: [QUOTE] #td {background-color: #FFAAFF} //If the ID of an element is td, this will apply .td {background-color: #AAFFFF} //If the class of the element is td, this will apply td {background-color: #FFFFAA} //If the element is a td, this will apply <div id="td"></div> //#FFAAFF <div class="td"></div> //#AAFFFF <td></td> //#FFFFAA [/QUOTE] Pretty simple. IE forces you to make workarounds around incredibly simple things something like changing an elements appearance (dropdowns) via pure CSS isn't supported almost exclusively by IE, for example. There's probably a lot of JS things not supported by IE as well, but I'm not that hot with Javascript (and, thus, AJAX. I should take a look at Rexy's tutorial again) Is there really anything blocking you from using FX like a normal human being? Until IE's up to [b]web standards[/b], there's really no point in using it. It really isn't fair to force IP to work to adhere to your refusal to use FX, and it's for your own good anyway.

Yeah, I liked the old one, but like these a bit better. Except for the purple.

Quote

Teach me how to code, and I will code the IE side.
What codes are you using? I know a little about html, a nano-bit of PHP, I don't know javascript (I heard java and javascript are completely different) I know a fractional bit of CSS and yeah, if IP is willing to teach me what I need to know, i'd gladly code the IE side of things.

Well, If you know a bit of CSS, you know it all. Just get a proper editing tool so you can cycle through different.. commands, I guess. Here's a brief intro:

Quote

#td {background-color: #FFAAFF} //If the ID of an element is td, this will apply
.td {background-color: #AAFFFF} //If the class of the element is td, this will apply
td {background-color: #FFFFAA} //If the element is a td, this will apply
<div id="td"></div> //#FFAAFF
<div class="td"></div> //#AAFFFF
<td></td> //#FFFFAA

Pretty simple. IE forces you to make workarounds around incredibly simple things something like changing an elements appearance (dropdowns) via pure CSS isn't supported almost exclusively by IE, for example. There's probably a lot of JS things not supported by IE as well, but I'm not that hot with Javascript (and, thus, AJAX. I should take a look at Rexy's tutorial again)

Is there really anything blocking you from using FX like a normal human being? Until IE's up to web standards, there's really no point in using it. It really isn't fair to force IP to work to adhere to your refusal to use FX, and it's for your own good anyway.

It's just going from one browser that i've grown attached to, to another browser, I use FF sometimes, but I don't really like the layout compared to IE's layout.

It's just going from one browser that i've grown attached to, to another browser, I use FF sometimes, but I don't really like the layout compared to IE's layout.

[color=#b5b5ff]Classic looks much nicer with the new fontset, but the post-reply box has font size that is too big. Syphon's skin is too bichromatic - the background of the site and the post body content have too similar colors. Edit~I see things are changing as I speak.. right now titlebars could be a little more distinct from background but things are better.[/color]

Classic looks much nicer with the new fontset, but the post-reply box has font size that is too big.

Syphon's skin is too bichromatic - the background of the site and the post body content have too similar colors.

Edit~I see things are changing as I speak.. right now titlebars could be a little more distinct from background but things are better.

[quote=Shocko]I have gone all this time using IE and never once found that it was filled with errors and flaws, I use FF and I too find that there is no errors or flaws, and so I see no reasoning behind trying to force FF upon people when IE is also capable, though from a programming perspective, more effort is required, and too right to, if you plan on programming for a major website or even a minor website, you should be prepared to do all the coding required to make it a multi-browser operational website.[/quote] IE IS NOT CAPABLE. You don't notice until you're sitting there at 4 am trying to get cross-browser rendering consistency with both of those W3C Valid buttons lit up, but you do, it hits you hard. Coding a simple layout is fine and easy. Just shit about borders mainly. I had to deal with so much crap to make the header fluid and cross compatible. It's really not simple at all.

Quote from Shocko

I have gone all this time using IE and never once found that it was filled with errors and flaws, I use FF and I too find that there is no errors or flaws, and so I see no reasoning behind trying to force FF upon people when IE is also capable, though from a programming perspective, more effort is required, and too right to, if you plan on programming for a major website or even a minor website, you should be prepared to do all the coding required to make it a multi-browser operational website.

IE IS NOT CAPABLE.

You don't notice until you're sitting there at 4 am trying to get cross-browser rendering consistency with both of those W3C Valid buttons lit up, but you do, it hits you hard.

Coding a simple layout is fine and easy. Just shit about borders mainly. I had to deal with so much crap to make the header fluid and cross compatible. It's really not simple at all.

dtbk, things weren't changing as you wrote that cuz i was watching a movie... unless... moose...

dtbk, things weren't changing as you wrote that cuz i was watching a movie...
unless... moose...