Some states have rules decided based on whether it's a game of chance or skill.
For example, pinball was hotly contested in some states, because there are some luck elements - especially because early pinballs paid out. (And they didn't have flippers, so it was almost entirely chance at first.) Some of those luck elements (free games, match, etc.,) must be disabled in some states, to be on the skill side of the chance vs. skill threshold.
Some states require that games of skill not pay out, some of them have a certain legal tests for what a game of skill is (they essentially boil down to something along the lines of, can a skilled player win even with all luck elements being against them, IIRC,) etc., etc.
The rumor mill says that Microsoft has current versions of Windows built for ARM internally... sorta like how Apple kept x86 builds of Mac OS X internally the whole time.
Wireless mesh networks will break down, though, over thousands of hops.
And, consumers don't care. Consumers just want their music and videos. Those, they can get from the mass media, which will have agreements that let them link to each other.
Well, back in the 1980s, almost everyone's disk formats were incompatible with each other in some way, whether it was 5.25" or 3.5".
I think the 3.5" disk was the first one to be adopted by a major US computer company, though. (And, it was the US companies that were the ones that could push change through. The Japanese couldn't really hit any markets outside of Asia, and the British could seriously innovate, but then squandered it (and couldn't really hit any markets outside of Europe and in some cases Australia/NZ.) Every time. And it was only Amstrad that used a microfloppy that wasn't 3.5" anyway.)
1. Open monitor. 2. Disconnect LVDS cable from LCD panel. 3. Connect to FPGA board, with an LVDS receiver programmed into the FPGA, and either some way of dumping the raw frames to a PC, or a video encoder that outputs compressed video. 4. ??? 5. Profit!
Bob was positioned to compete against Packard Bell Navigator and other similar vendor alternate shells, and Microsoft ultimately required that vendors only distribute Bob if they wanted to distribute an "easier" Program Manager replacement.
The difference between the BBC and PBS/NPR is that paying the BBC is compulsory if you watch TV, paying PBS/NPR is voluntary.
BBC is quasi-governmental, and has some laws relating to how it can operate, PBS/NPR are not-for-profit organizations, and can operate however the hell they want (as long as the mission isn't to profit.)
The upshot of this is that PBS runs telethons every so often - basically, for a whole day, instead of content, you get fundraising. As I understand, NPR just advertises donations every now and then, although I don't listen to NPR. Also, PBS and NPR can be blatantly biased in whatever direction they want without violating any laws.
And that's what it's doing right now. HTML5 itself is codec-agnostic.
The problem is that it doesn't matter what codecs are supported, it matters what codecs people actually use to post content online. If you can't legally support H.264, and people want to post H.264 videos, you're screwed.
Now, can browsers support the system codecs? Yes, and I've heard claims that on Unix, Opera actually does. Problem solved, anything that you have a GStreamer codec for can be played in Opera using <video>.
However, part of the point of <video> was that it would get rid of having to download codecs and media players and such.
Except the paperless office will never be a reality, paper is lighter weight than even the lightest slate tablets, it has infinite battery life, is generally considered stronger for legal purposes, and is harder for the possessor to accidentally destroy or for someone else to intentionally destroy.
Because almost always, the 3D stuff comes along for the ride, when you get a couple dual-link DVI ports strapped to it.
(And, sometimes, 2D stuff can lay on the 3D acceleration hardware.)
Even ATI's current server 2D discrete graphics chipset, the ES1000, is basically just a die-shrunk version of the Radeon 7000, which was a solid low-end PCI/AGP 3D graphics card when it came out.
The performance will make even the worst integrated graphics that you can buy nowadays look significantly better, but you can get Intel graphics on a Core i7. Or anything with a PCI slot, really.
It's called the i740.
I believe it'll work with the drivers for Intel integrated graphics, as the i740 is the direct predecessor of Intel's integrated graphics line, and IIRC, the i740 is actually the same as the i810's graphics hardware.
It also meant that you could run such apps on desktop Itanium (remember, when.NET came out, Itanium was supposed to be the next big thing,) or any other architecture that MS decided to move to.
You'd be surprised at how quickly someone will write a somewhat friendly wrapper for the SDK's USB loader, and distribute it somewhere like XDA Developers.
There's a rather significant WinMo modding community, they're not gonna lie down for this one.
Slashdot Mirror
You can develop for (almost) *ANY* Windows Mobile phone, not just 100 phones, without App Store intervention.
Some states have rules decided based on whether it's a game of chance or skill.
For example, pinball was hotly contested in some states, because there are some luck elements - especially because early pinballs paid out. (And they didn't have flippers, so it was almost entirely chance at first.) Some of those luck elements (free games, match, etc.,) must be disabled in some states, to be on the skill side of the chance vs. skill threshold.
Some states require that games of skill not pay out, some of them have a certain legal tests for what a game of skill is (they essentially boil down to something along the lines of, can a skilled player win even with all luck elements being against them, IIRC,) etc., etc.
Either that, or there's another tactic that you could use.
Do step 1.
But then, instead of doing step 2, get a crap lawyer. Intentionally lose the case.
Then, Google will lobby Congress to push through a law legalizing robots.txt, which will trump the case law.
The other thing is, keep a full build internally.
The rumor mill says that Microsoft has current versions of Windows built for ARM internally... sorta like how Apple kept x86 builds of Mac OS X internally the whole time.
Wireless mesh networks will break down, though, over thousands of hops.
And, consumers don't care. Consumers just want their music and videos. Those, they can get from the mass media, which will have agreements that let them link to each other.
Of course, you can always start an MVNO. (Mobile Virtual Network Operator.)
Piggy-back on someone else's network and agreements, and provide your own customer service and billing and such.
VERY approximately. AFAICT, SXCE was more like Solaris 10, but with bleeding-edge OpenSolaris /dev code.
Well, back in the 1980s, almost everyone's disk formats were incompatible with each other in some way, whether it was 5.25" or 3.5".
I think the 3.5" disk was the first one to be adopted by a major US computer company, though. (And, it was the US companies that were the ones that could push change through. The Japanese couldn't really hit any markets outside of Asia, and the British could seriously innovate, but then squandered it (and couldn't really hit any markets outside of Europe and in some cases Australia/NZ.) Every time. And it was only Amstrad that used a microfloppy that wasn't 3.5" anyway.)
1. Open monitor.
2. Disconnect LVDS cable from LCD panel.
3. Connect to FPGA board, with an LVDS receiver programmed into the FPGA, and either some way of dumping the raw frames to a PC, or a video encoder that outputs compressed video.
4. ???
5. Profit!
Technically, the 3.5" disk we use today is not QUITE Sony's design, but based upon it: http://en.wikipedia.org/wiki/History_of_the_floppy_disk#3.C2.BD-inch_format
And, ultimately, it was Apple adopting it that made it take off.
And Microsoft sure as hell tried that.
Bob was positioned to compete against Packard Bell Navigator and other similar vendor alternate shells, and Microsoft ultimately required that vendors only distribute Bob if they wanted to distribute an "easier" Program Manager replacement.
It WAS released during the (very end of) the Windows 3.1 years.
Windows 95 came out in August, 1995.
The difference between the BBC and PBS/NPR is that paying the BBC is compulsory if you watch TV, paying PBS/NPR is voluntary.
BBC is quasi-governmental, and has some laws relating to how it can operate, PBS/NPR are not-for-profit organizations, and can operate however the hell they want (as long as the mission isn't to profit.)
The upshot of this is that PBS runs telethons every so often - basically, for a whole day, instead of content, you get fundraising. As I understand, NPR just advertises donations every now and then, although I don't listen to NPR. Also, PBS and NPR can be blatantly biased in whatever direction they want without violating any laws.
The video tag isn't canvas. It's just a different kind of embed that directly accepts a URL for a video.
That video can be H.264, or it can be Ogg container, Theora video, Vorbis audio. Actually, it can be anything, but those are the two primary formats.
(Opera on *nix can use any video format for which there is a GStreamer codec installed.)
In this case, this is the BBC, so viewers are already paying for the content in their TV fees, and the BBC isn't even allowed to show ads in the UK.
It's a Chi Mei Optoelectronics panel.
You might have heard of their joint venture with IBM, IDTech, which made a 22.2 3840x2400 IPS panel. And a 15.0 2048x1536 IPS panel for laptops.
They know how to make quality panels.
This one's only Chi Mei's S-MVA tech, but MVA certainly isn't bad.
http://www.chimei-innolux.com/opencms/cmo/products/lcd_tv/products_lcd_tv_V562D1.html?__locale=en
And that's what it's doing right now. HTML5 itself is codec-agnostic.
The problem is that it doesn't matter what codecs are supported, it matters what codecs people actually use to post content online. If you can't legally support H.264, and people want to post H.264 videos, you're screwed.
Now, can browsers support the system codecs? Yes, and I've heard claims that on Unix, Opera actually does. Problem solved, anything that you have a GStreamer codec for can be played in Opera using <video>.
However, part of the point of <video> was that it would get rid of having to download codecs and media players and such.
Except the paperless office will never be a reality, paper is lighter weight than even the lightest slate tablets, it has infinite battery life, is generally considered stronger for legal purposes, and is harder for the possessor to accidentally destroy or for someone else to intentionally destroy.
Because almost always, the 3D stuff comes along for the ride, when you get a couple dual-link DVI ports strapped to it.
(And, sometimes, 2D stuff can lay on the 3D acceleration hardware.)
Even ATI's current server 2D discrete graphics chipset, the ES1000, is basically just a die-shrunk version of the Radeon 7000, which was a solid low-end PCI/AGP 3D graphics card when it came out.
Technically, you can.
The performance will make even the worst integrated graphics that you can buy nowadays look significantly better, but you can get Intel graphics on a Core i7. Or anything with a PCI slot, really.
It's called the i740.
I believe it'll work with the drivers for Intel integrated graphics, as the i740 is the direct predecessor of Intel's integrated graphics line, and IIRC, the i740 is actually the same as the i810's graphics hardware.
It was more than just desktop x86.
It also meant that you could run such apps on desktop Itanium (remember, when .NET came out, Itanium was supposed to be the next big thing,) or any other architecture that MS decided to move to.
EVDO is Sprint's 3G network tech.
Not on WinPho 7, except in very limited circumstances.
They really are copying the iPhone. Except, they didn't get the memo that Apple finally got around to adding copy and paste to the iPhone.
You'd be surprised at how quickly someone will write a somewhat friendly wrapper for the SDK's USB loader, and distribute it somewhere like XDA Developers.
There's a rather significant WinMo modding community, they're not gonna lie down for this one.
Technically, it's not rendered to an image - it's rendered to an Opera internal markup language, IIRC.