Seriously, although it certainly makes sense that Manufacturers compensation for flaws, they've got one hell of a crap production line if their flawed products outnumber their good ones.
Think markets here: You'll sell a lot more mid range cards then high end ones because let's face it, not everyone is stupid.
Saying that, some of those mid-range cards are defective to the point where they can't be high end, but a large majority are perfectly fine.
So, you design you production line to make the high end cards, overprice them to cater to the high end market, and price disabled, mid-range cards so you still make a profit and volia: daddy get's a new ferrari!
(Actually, the profits from high end cards probably got back into R&D to cover the next gen of high end cards... the company survives day to day on the regular stuff I'd bet)
I div is a logical structure, it doesn't have a known display. ie, it can be placed anywhere on the page, and anywhere in relation to other divs.
I could float that div and put it in the top right of the page.
A td is by defintion a table cell (tabular data), which has an implied structure. Breaking that structure to present a table as something not like a table is the wrong thing to do, especially since you're so concerned about browser compatability.
Try using a screen reader on you websites and then come back to me.
1. IE mac is a joke, if MS doesn't feel the need to support it, I certainly don't.
2. The HTML in the CSS result remains the same should you redesign the site at a future date, the HTML in the table result will change. This matters if a) you have a large site and/or b) you use a CMS to spit out HTML.
If you're using firefox, you don't need greasemonkey for what you want to do, you just need to tinker with about:config.
How can they stop you from printing the contents of the screen anyway? Between view source and your OS's print screen button, it should be easy to get around.
None of them seem to have a clue that a world exists outside of their campuses, and that world if full of greedy capitalists.
The beauty of the GPL as opposed to BSD or MIT schemes is that it uses existing copyright laws to ensure that programmers can actually be recognized properly for the code they create.
This means a lot more than having the respect of your peers. It means being able to feed your family.
Of course, GPL won't enable you to make money in and of itself, but it prevents others from directly exploiting you. You hear a lot of whining about loss of freedom in today's world, but I will truely be frightened the day a GPL case is lost in a Supreme Court somewhere. It's that important.
Open Source ideas outside of the GPL are not practical if you lack the massive finacial support of an institution. They do have their place though, I guess.
Whomever designed that stupid slideshow app that they seem to be in love with should be fired. Whomever commisioned the dev who designed it should be fired too.
What a wonderful user experience... having the page change on it's own while you're in the middle of a sentence. Real slick.
If anyone needed an example of how not to design a UI, this is it.
aside from the bad spelling, it should be "spade a spade".
but this:
The bottom line is, was, and always will be, this: if you're not doing anything wrong, you don't have anything to worry about!
Pretty much undermines the entire base of western civilzation (arguably), and most definately the founding principles of the US.
Of course you (and many like you) are too stupid to realize that.
(I don't like to resort to ad-hominum attacks - but it's high time we start calling a space a spade.)
Seriously, although it certainly makes sense that Manufacturers compensation for flaws, they've got one hell of a crap production line if their flawed products outnumber their good ones.
Think markets here: You'll sell a lot more mid range cards then high end ones because let's face it, not everyone is stupid.
Saying that, some of those mid-range cards are defective to the point where they can't be high end, but a large majority are perfectly fine.
So, you design you production line to make the high end cards, overprice them to cater to the high end market, and price disabled, mid-range cards so you still make a profit and volia: daddy get's a new ferrari!
(Actually, the profits from high end cards probably got back into R&D to cover the next gen of high end cards... the company survives day to day on the regular stuff I'd bet)
the New netscape is owned by AOL, and really has nothign to do with Mozilla... that connection has long ago been severed.
I lot of folk in this thread seem not to realize that.
because you want to charge an extra $50 for those cards.
It's cheaper to do things this way than it is to actually alter your production lines.
here, try this:
http://www.snook.ca/archives/000177.html
also note that this site is css based as well.
I div is a logical structure, it doesn't have a known display. ie, it can be placed anywhere on the page, and anywhere in relation to other divs.
I could float that div and put it in the top right of the page.
A td is by defintion a table cell (tabular data), which has an implied structure. Breaking that structure to present a table as something not like a table is the wrong thing to do, especially since you're so concerned about browser compatability.
Try using a screen reader on you websites and then come back to me.
1. IE mac is a joke, if MS doesn't feel the need to support it, I certainly don't.
2. The HTML in the CSS result remains the same should you redesign the site at a future date, the HTML in the table result will change. This matters if a) you have a large site and/or b) you use a CMS to spit out HTML.
first google result: http://www.jakpsatweb.cz/css/css-vertical-center-s olution.html
www.w3shools.com
(VERY basic though)
Then let us know.
I'm not seeing your point then.
Seperating style from content using css has so many pros I don't know why I wouldn't suscribe to it.
That being said, I do use tables: to present tabular data.
think of your customers, think of your bandwith
1. CSS based designs use less bandwidth, because stylesheets are cashed.
2. Think of yuo customer's customers. Specifically, those using browsers other than ie, those on cell phones, those who are using screen readers etc.
If you're using firefox, you don't need greasemonkey for what you want to do, you just need to tinker with about:config.
How can they stop you from printing the contents of the screen anyway? Between view source and your OS's print screen button, it should be easy to get around.
that a lot less folk can't even agree on a single flavour of linux, I wouldn't hold my breath on that one.
The lack of a tail causes humans to have some of the worst balance in the animal kingdom.
It couldn't get any worse!
a treo.
You'll find out.
You can learn a lot about a show by looking at it's time slot.
This show is on Friday nights.
That pretty much sums it up.
None of them seem to have a clue that a world exists outside of their campuses, and that world if full of greedy capitalists.
The beauty of the GPL as opposed to BSD or MIT schemes is that it uses existing copyright laws to ensure that programmers can actually be recognized properly for the code they create.
This means a lot more than having the respect of your peers. It means being able to feed your family.
Of course, GPL won't enable you to make money in and of itself, but it prevents others from directly exploiting you. You hear a lot of whining about loss of freedom in today's world, but I will truely be frightened the day a GPL case is lost in a Supreme Court somewhere. It's that important.
Open Source ideas outside of the GPL are not practical if you lack the massive finacial support of an institution. They do have their place though, I guess.
It's firefox, not KDE that is challenging microsoft.
Most users are compiling anything, becasue most users are running windows.
And works great.
That logic is a little backwards.
If you have x sick days a year, and x vacation days a year, the company has already accounted for these days in your salary.
They haven't lost shit, those days were already assigned. If you don't take them, they gain a little, but it's not the other way around.
Whomever designed that stupid slideshow app that they seem to be in love with should be fired. Whomever commisioned the dev who designed it should be fired too.
What a wonderful user experience... having the page change on it's own while you're in the middle of a sentence. Real slick.
If anyone needed an example of how not to design a UI, this is it.
so Billy doesn't think that Apple hasn't clued into this already?
there will be a cell enabled Ipod soon enough I'm sure.