This way, the Mozilla people don't have to program tabs into their program. Apply this to any program you'd wish use tabs, and now you've got a better picture of how useful this becomes.
I'm certain it's something that can be manipulated via the vimrc file. I'll even wager that the change is in the mswin.vim file that is sourced by default installs on Windows. That's what this thread leads me to believe. (See March 27, 2004 21:57 comment)
In most GUIs, when you select text using a mouse or the keyboard, it puts you in some kind of "type over" mode. ViM now seems to respect this behavior rather than doing it's own thing of allowing commands to be executed. I am unsure whether or not it is a Windows-specific behavioral change or an across-the-board one, but what it boils down to is that ViM on Windows behaves more like a Windows app for this very common and quite expected way.
I think the problems aren't in the DOCTYPE usage (although IE seems to understand little more than the presence of a DOCTYPE), but rather other standards such as CSS and DOM handling.
Personally, I have no trouble implementing designs in CSS and using the DOM to manipulate a page, one only needs to realize that every whiz-bang feature doesn't work across the board (:after and:before rules, for example). As you can see, DOCTYPE has no meaning for that stuff.
I installed this last week and was quite happy to see that the p-bug in windows is now fixed! Basically, if you had text selected and started to type a letter p, a paste would ensue rather than typing the letter p.
Support all W3C standards. Deprecate all your proprietary extensions.
And paint my house while you're at it! Sheesh, you lazy Microsofties, you can't even kill off backwards compatibility with products you created at a time when there were no governing standards in place to accomplish what you felt was important to your customers. With this kind of thinking, your next kernel release won't even break backwards compatibility! What were you thinking?!?
One big thing to remember is that Microsoft isn't releasing this new IE as a standalone app with this release. People that use older versions of Windows won't be able to upgrade. This translates into popup windows still be utilized for the most part for a while longer, as they are still fairly economical. That's not to say that advertisers won't start using more annoying methods, but I don't think it will happen overnight.
That isn't a solution for background images. Specifically, if you want to use a background image that doesn't repeat or scale to fit the entire box, the box gets clipped due to the filter applied to it. Also, the text inside the box takes on the filter, which isn't useful for the most part. The IE PNG hack has very limited uses, we need full support. If nothing else, it'll shut up some of the web development community and let them worry about something more important, like accessibility.
The marketplace will determine what competes with what. This will be a significant handheld war to be sure.
I'm rooting for the DS myself. I don't trust Sony to deliver all that they promise. Just look at how the PSX was scaled back before final release--hook the consumer with features then switch 'em to a less mature product. I expect the PSP to be the same.
FYI, the mp4 format is sorta a container format, similar to quicktime. The AAC audio and Apple Lossless audio both use the m4a extension, and the protected versions use m4p.
that's an easy one. Cancer doesn't come with documentation. One can flesh out an implementation of a spec, but figuring out the great unknown is quite a bit more difficult.
Is it possible/easy to have two forms on the same page? In the examples I've seen (mostly on w3schools.com), only one form is present. Since there's no form element per se, it seems as if it would be difficult to have two forms on a page.
Your HTML shouldn't render well as you're breaking the rules of the game. Check the specs, but you aren't supposed to have block elements being the children of inline ones. If you're wanting to have the divs #test and #test2 be next to each other, you'll need to assign a "float: left" to them, or use a less supported display type such as table-cell.
Mozilla often renders things correctly according to the specs, while other browsers (especially IE) don't follow the rules consistently.
That's probably not the best choice of labels, as the successor to Ultra-Wifi will be even more "Ultra" and then you have a similar problem that USB 2.0 has: high speed, full speed, we all speed for ice speed.
Wifi 2 or something safer would be a better choice. (I'm partial to "Son of Wifi," but that of course would never fly)
Yeah, because the GPL automatically makes the program in question "good". The maintainer of the code would still reject any patches that made his/her program different than the original vision of the program. Just because it's GPL doesn't mean squat.
Why should Microsoft have to create everything? It sounds as if you're saying for a protocol to really be open, Microsoft should create a competing product on a competing os. That's just foolish.
Microsoft's sent C# and their CLI to ECMA. Why should they be forced to create a version for OSX or Linux?
They reviewed the smaller players that compete with the iPod mini. You did notice they don't include the 40GB iPod or the Archos Jukebox right? Your 20GB player is in a different class.
Slashdot Mirror
This way, the Mozilla people don't have to program tabs into their program. Apply this to any program you'd wish use tabs, and now you've got a better picture of how useful this becomes.
It's nice, but I don't like it when apps use different background colors than my system.
I'm certain it's something that can be manipulated via the vimrc file. I'll even wager that the change is in the mswin.vim file that is sourced by default installs on Windows. That's what this thread leads me to believe. (See March 27, 2004 21:57 comment)
In most GUIs, when you select text using a mouse or the keyboard, it puts you in some kind of "type over" mode. ViM now seems to respect this behavior rather than doing it's own thing of allowing commands to be executed. I am unsure whether or not it is a Windows-specific behavioral change or an across-the-board one, but what it boils down to is that ViM on Windows behaves more like a Windows app for this very common and quite expected way.
I think the problems aren't in the DOCTYPE usage (although IE seems to understand little more than the presence of a DOCTYPE), but rather other standards such as CSS and DOM handling.
:before rules, for example). As you can see, DOCTYPE has no meaning for that stuff.
Personally, I have no trouble implementing designs in CSS and using the DOM to manipulate a page, one only needs to realize that every whiz-bang feature doesn't work across the board (:after and
I installed this last week and was quite happy to see that the p-bug in windows is now fixed! Basically, if you had text selected and started to type a letter p, a paste would ensue rather than typing the letter p.
One big thing to remember is that Microsoft isn't releasing this new IE as a standalone app with this release. People that use older versions of Windows won't be able to upgrade. This translates into popup windows still be utilized for the most part for a while longer, as they are still fairly economical. That's not to say that advertisers won't start using more annoying methods, but I don't think it will happen overnight.
That isn't a solution for background images. Specifically, if you want to use a background image that doesn't repeat or scale to fit the entire box, the box gets clipped due to the filter applied to it. Also, the text inside the box takes on the filter, which isn't useful for the most part. The IE PNG hack has very limited uses, we need full support. If nothing else, it'll shut up some of the web development community and let them worry about something more important, like accessibility.
The marketplace will determine what competes with what. This will be a significant handheld war to be sure.
I'm rooting for the DS myself. I don't trust Sony to deliver all that they promise. Just look at how the PSX was scaled back before final release--hook the consumer with features then switch 'em to a less mature product. I expect the PSP to be the same.
FYI, the mp4 format is sorta a container format, similar to quicktime. The AAC audio and Apple Lossless audio both use the m4a extension, and the protected versions use m4p.
that's an easy one. Cancer doesn't come with documentation. One can flesh out an implementation of a spec, but figuring out the great unknown is quite a bit more difficult.
That's really clever. Maybe we do deserve spam after all.
What am I saying?
Is it possible/easy to have two forms on the same page? In the examples I've seen (mostly on w3schools.com), only one form is present. Since there's no form element per se, it seems as if it would be difficult to have two forms on a page.
Am I missing something?
Your HTML shouldn't render well as you're breaking the rules of the game. Check the specs, but you aren't supposed to have block elements being the children of inline ones. If you're wanting to have the divs #test and #test2 be next to each other, you'll need to assign a "float: left" to them, or use a less supported display type such as table-cell.
Mozilla often renders things correctly according to the specs, while other browsers (especially IE) don't follow the rules consistently.
That's probably not the best choice of labels, as the successor to Ultra-Wifi will be even more "Ultra" and then you have a similar problem that USB 2.0 has: high speed, full speed, we all speed for ice speed.
Wifi 2 or something safer would be a better choice. (I'm partial to "Son of Wifi," but that of course would never fly)
At least it wasn't E.T.
This discussion has officially changed from suck to blow.
anybody know where Canada stands on software patents?
and for how much longer?
Yeah, because the GPL automatically makes the program in question "good". The maintainer of the code would still reject any patches that made his/her program different than the original vision of the program. Just because it's GPL doesn't mean squat.
I was thinking along similar lines. For a corporate solution, wouldn't DNS be the place to start?
Why should Microsoft have to create everything? It sounds as if you're saying for a protocol to really be open, Microsoft should create a competing product on a competing os. That's just foolish.
Microsoft's sent C# and their CLI to ECMA. Why should they be forced to create a version for OSX or Linux?
since the parent posted a password protected version of the page, go here for the regular one
I bet you spent an extra amount of time rechecking syntax before posting, just to keep yourself free of typo-nazis, didn't you?
Maybe that's just what I would do...
They reviewed the smaller players that compete with the iPod mini. You did notice they don't include the 40GB iPod or the Archos Jukebox right? Your 20GB player is in a different class.