I still strong suggest the use of Virtual Keyboard, as input method seems to be a hurdle for small/light portable devices at the moment.
Good idea! Except for two things:
Canesta only makes a virtual keyboard chipset for OEMs; they don't sell keyboards.
There aren't any OEMs that make keyboards with the chipset.
In other words, the only way you can get one of these keyboards right now is to purchase the Canesta development kit for $7500 and then write a keyboard program that runs on their hardware.
Maybe not, but you most certainly do on your file format. You don't need to release any new code, and you can change the format any time you want.
I fail to see how the GTO format and associated code could not be continued by any number of other people if they so choose.
Oh, they certainly could. However, if the code is incompatible with new products, and the new format is unknown, this causes a problem for end users.
And finally, I cannot for the life of me understand why anyone would want to exchange 3D geometric and animation data over a network using XML -- especially in a human readable form.
Amen. They justify it this way. Apparently they are working on a binary format.
If there was ever a less appropriate use of XML I can't think of it.
FreeCache can only serve files that are on a web site. If the link to a file on that web site goes away, so will the file in the FreeCaches. Also, there is a minimum size requirement. We don't bother with files smaller than 5MB, as the saved bandwidth does not outweight the protocol overhead in those cases.
The AOL example is bad, because everybody's apps had to interact with AOL's server. File formats are different.
Okay, I'll give you a better example. How about RTF? Microsoft has release the RTF specification. It's public, and a de facto standard that anyone can use. However, Microsoft continuously tweaks their implementation so that not even Microsoft products of different versions are entirely compatible with each other, and interoperability between applications is a complete mess.
Besides, if the ability to switch to another file format makes the current one less than open, then there are no open file formats at all.
It's not the ability to switch that's making it less than open. This is simply a side effect of not standardizing. Standardization makes it difficult for any one group to ruin interoperability without dire consequences to themselves. Without standardization, this isn't true.
Besides, there are open file formats. The format and encoding rules for XML is very ridgidly defined. If you use an application of XML, like XHTML, you can be absolutely certain of the file format.
Who can say with absolute certainty that gcc won't drop support for.c files in the future, and transition to encrypted c# instead?
This is a bad example, as there's no strictly defined file format in the C language specification, and GCC uses the platform's encoding rules, IIRC. In fact, I bet you can find plenty of C files that are encoded in EBCDIC that GCC reads just fine, provided you're on a platform that supports it.
Open source projects changing file formats is also not unheard of. Many projects have broken things by changing their configuration file format. Just because the code is open source does not make the file format it uses an open standard.
Now if you said that no one could say with absolute certainty that GCC wouldn't drop support for the increment operator, I'd have to disagree. If they did this, they would no longer be a C compiler, because they wouldn't support the C standard. Someone else would then step in to take their place.
With one company calling all the shots, this doesn't happen. The company can change the format willy-nilly, and you have to play catch-up. Furthermore, you can't have your ideas incorporated into their format. With a standard format, you can bring your ideas before the standards committee.
Walking around with a harddrive and CD is "more convenient" than walking around with just a harddrive? What wierd strange world do you come from?
I live in a weird strange world where most machines don't boot from CD by default.
It is far more convienent to just put the CD in and boot the machine than it is to try to find the correct BIOS settings (or find out that the machine in question doesn't have them).
Like I said before, it's a mini-CD, not an 8" floppy. It fits in a shirt pocket. It's not any more inconvenient than carrying around the HD.
I can't speed for Softimage, but Tweak Film's GTO is not a "proprietary format". Its released under LGPL as evidenced by its FSF listing.
While it is true that the code is released under the LGPL, this does not prevent the company from discontinuing its use of the format, using a new format, and then not releasing that under the LGPL. A similar situation happened with AOL's TOC protocol. Standardization prevents this from happening, because usually, more than one company or group designs the standard and more than one vendor creates products using the standard.
So then it's not as convenient as just walking around with a portable harddrive and jacking it in to random systems, but you also need to carry around the CD as well.
Actually it's more convenient, because most machines are able to boot off a CD by default, so you don't have to mess with the BIOS.
Furthermore, it's a mini-CD, so it's not like it takes up a lot of extra room.
I never thought it could happen to me! I was in Fry's the other day trying out at an MX500. I was considering purchasing the mouse, when a very attractive sales girl came my way. Attractive is an understatement. She was simply gorgeous, with long flowing blonde hair, a tight ass, and full large breasts.
"How do you like it?", she asked.
My first comment was, "It feels like a well formed breast I'm touching here, filling my hand in all the right places." I was taken aback by my faux pas of saying such a thing in front of such a fetching member of the opposite sex, but she just smiled.
"Do you want a comparison?", she said knowingly. I couldn't help noticing her shaply bosoms beneath her tight shirt. I imagined her moaning as I gently massaged her nipples to their full one and a half inch lengths.
She motioned me to follow her. I couldn't help staring at her backside. She had on tight jeans reavealing a perfect ass. I could not get the vision out of my head of thrusting my purple-headed warrior deep within her quivering mound of love-pudding. I started to feel a tightness in my loins.
"This is a new mouse by Microsoft", she said stopping at the next display, "It's designed by S+arck."
There are at least two opensource 3d file format standards that I know of developed by actual companies in the industry
Both of which are proprietary formats.
Just because a company chooses to make certain applications that use their format open source doesn't make their format a standard. Furthermore, neither of these companies have enough spin to make their proprietary format a de facto standard.
X3D is being put through the ISO standards process, and U3D is being designed by huge industry players.
By the time I had read through the articles on the home page, most of the album had played out. Then I read the AGC article and downloaded the code.
The weird part is that when I started reading the Luminary source code, the track playing was, "Moonloop", and hit the part at 13:18 where an excerpt of the Apollo landing broadcast is mixed it.
In one final display that left onlookers speechless yesterday, the company showed how the suspension system can be coaxed into jumping -- yes, jumping -- over obstacles in its path.
This is nothing new. The Mach 5 had this in 1966.
This "new" system doesn't even have a kid and a monkey in the trunk, let alone make the "ch-ch-ch-ch" sound.
Now that it has been established by many posts that the drives are crap when it comes to ethernet perhaps someone can suggest a better product?
The Linksys NSLU2 is *much* better than the Ximeta drives. You can attach two USB drives or a HD and a flash drive to it.
Unlike the Ximeta drive, it works under Linux with no issues, can be written to by more than one person concurrently, can be accessed by multiple subnets, uses a common protocol that doesn't require driver installation (SMB and CIFS), is built on GPL software, and can back up shares from other machines on a schedule.
HP got Virus Throttler to work well in its labs with products using operating systems like HP-UX and
Linux (news - web sites). However, the technology required changes to the way those operating systems run that HP couldn't duplicate on Windows systems, because "we don't own Windows," Redmond says.
Does that imply that HP thinks they own Linux? I think we just figured out their new strategy to generate revenue in the future.
Don't confuse the sale and promotion of Nazism and icons thereof with trying to cover up what happened.
What I don't understand, though, is why they need to do things like this:
Important note for German users - Disclaimer: You are about to enter the Castle Wolfenstein website. The following pages may have content that is forbidden by law in Germany. Activision Germany GmbH is not responsible for the content of the following pages. By entering this site you approve having read this disclaimer.
It's not like Wolfenstein promotes Nazism any more than Doom promotes Satan.
This one is labeled "Moderately Critical".
MikeMacK would have replied, but his right to free speech has been taken away.
Dood, if your unit shrinks so much as to be a pain in your ass, you need to see a doctor. Immediately!
Good idea! Except for two things:
- Canesta only makes a virtual keyboard chipset for OEMs; they don't sell keyboards.
- There aren't any OEMs that make keyboards with the chipset.
In other words, the only way you can get one of these keyboards right now is to purchase the Canesta development kit for $7500 and then write a keyboard program that runs on their hardware.Not to mention AA, since the grandparent used a, "*".
Anal! Posteri[or]! That's a joke, son. Went right past you...
Sorry, I'll leave now...
What about ChatZilla? It's free, cross-platform, and not too bad.
Maybe not, but you most certainly do on your file format. You don't need to release any new code, and you can change the format any time you want.
I fail to see how the GTO format and associated code could not be continued by any number of other people if they so choose.
Oh, they certainly could. However, if the code is incompatible with new products, and the new format is unknown, this causes a problem for end users.
And finally, I cannot for the life of me understand why anyone would want to exchange 3D geometric and animation data over a network using XML -- especially in a human readable form.
Amen. They justify it this way. Apparently they are working on a binary format.
If there was ever a less appropriate use of XML I can't think of it.
XML excels at being used inappropriately.
Okay, I'll give you a better example. How about RTF? Microsoft has release the RTF specification. It's public, and a de facto standard that anyone can use. However, Microsoft continuously tweaks their implementation so that not even Microsoft products of different versions are entirely compatible with each other, and interoperability between applications is a complete mess.
Besides, if the ability to switch to another file format makes the current one less than open, then there are no open file formats at all.
It's not the ability to switch that's making it less than open. This is simply a side effect of not standardizing. Standardization makes it difficult for any one group to ruin interoperability without dire consequences to themselves. Without standardization, this isn't true.
Besides, there are open file formats. The format and encoding rules for XML is very ridgidly defined. If you use an application of XML, like XHTML, you can be absolutely certain of the file format.
Who can say with absolute certainty that gcc won't drop support for .c files in the future, and transition to encrypted c# instead?
This is a bad example, as there's no strictly defined file format in the C language specification, and GCC uses the platform's encoding rules, IIRC. In fact, I bet you can find plenty of C files that are encoded in EBCDIC that GCC reads just fine, provided you're on a platform that supports it.
Open source projects changing file formats is also not unheard of. Many projects have broken things by changing their configuration file format. Just because the code is open source does not make the file format it uses an open standard.
Now if you said that no one could say with absolute certainty that GCC wouldn't drop support for the increment operator, I'd have to disagree. If they did this, they would no longer be a C compiler, because they wouldn't support the C standard. Someone else would then step in to take their place.
With one company calling all the shots, this doesn't happen. The company can change the format willy-nilly, and you have to play catch-up. Furthermore, you can't have your ideas incorporated into their format. With a standard format, you can bring your ideas before the standards committee.
Or a CD drive mounted sideways!
I live in a weird strange world where most machines don't boot from CD by default. It is far more convienent to just put the CD in and boot the machine than it is to try to find the correct BIOS settings (or find out that the machine in question doesn't have them).
Like I said before, it's a mini-CD, not an 8" floppy. It fits in a shirt pocket. It's not any more inconvenient than carrying around the HD.
While it is true that the code is released under the LGPL, this does not prevent the company from discontinuing its use of the format, using a new format, and then not releasing that under the LGPL. A similar situation happened with AOL's TOC protocol. Standardization prevents this from happening, because usually, more than one company or group designs the standard and more than one vendor creates products using the standard.
Actually it's more convenient, because most machines are able to boot off a CD by default, so you don't have to mess with the BIOS. Furthermore, it's a mini-CD, so it's not like it takes up a lot of extra room.
CAN'T... LEAVE.. THIS.. ONE.. ALONE... ARRRrRRGGgghh!
Sorry. I had to.Both of which are proprietary formats.
Just because a company chooses to make certain applications that use their format open source doesn't make their format a standard. Furthermore, neither of these companies have enough spin to make their proprietary format a de facto standard.
X3D is being put through the ISO standards process, and U3D is being designed by huge industry players.
I just bought The Sky Moves Sideways, and I was listening to it while reading Slashdot.
By the time I had read through the articles on the home page, most of the album had played out. Then I read the AGC article and downloaded the code.
The weird part is that when I started reading the Luminary source code, the track playing was, "Moonloop", and hit the part at 13:18 where an excerpt of the Apollo landing broadcast is mixed it.
I am totally freaked out right now.
The Tatsunoko Company built the Shooting Star.
This is nothing new. The Mach 5 had this in 1966.
This "new" system doesn't even have a kid and a monkey in the trunk, let alone make the "ch-ch-ch-ch" sound.
The Linksys NSLU2 is *much* better than the Ximeta drives. You can attach two USB drives or a HD and a flash drive to it.
Unlike the Ximeta drive, it works under Linux with no issues, can be written to by more than one person concurrently, can be accessed by multiple subnets, uses a common protocol that doesn't require driver installation (SMB and CIFS), is built on GPL software, and can back up shares from other machines on a schedule.
Oh, and you can hack it.
The funny part is some dipshit and/or sick bastard modded you informative!
Like beer googles, but instead the person you were attracted to the night before turns out to smell really bad.
Does that imply that HP thinks they own Linux? I think we just figured out their new strategy to generate revenue in the future.
What I don't understand, though, is why they need to do things like this:
It's not like Wolfenstein promotes Nazism any more than Doom promotes Satan.