Slashdot Mirror
IBM Donates Code to Firefox
OS24Ever writes "Internetnews.com is reporting that IBM has donated new DHTML code to the Mozilla foundation specifically targeted as accessability and rich interactive applications (RIA). These new features are expected to be in the next major update of Firefox (v1.5). Is this the first OSS application to get RIA/DHTML support for accessability? I would think this could open some doors for Firefox to replace IE in many Windows environments."
Thanks for supporting Open Source, and thanks for supporting Firefox.
-Random Person.
I would really love to see the code. It is in CVS yet? I am rather excited, since I have been working on several RIA things lately. Anyone seen the code yet? Or at the very least, anyone have a more specific list of new functionality?
bash: rtfm: command not found
DHTML is certainly less annoying than 30 second flash intro's, but I want a simple,fast, non-Microsoft browser. I hope this doesn't become a bloated browser like Navigator became.
The Big Yuan - tracking mainland China
Oh come on. Every time there's a Mozilla thread, there is some idiot posting That sounds like Opera's feature X. Christ, get over it. Your browser picked a bad name, and nobody wants to use it, for fear of being all hoity-toity.
Use your opera, that's fine, but don't expect me at any of your parades.
Yup, I know, the Flash player isn't open source. But there's an open source compiler, MTASC (*), and with ActionStep, there's a rapidly growing (BSD licensed!) open source component library.
All sorts of nifty open source things are happening with Flash these days; you can track that sort of thing on OSFlash.
(*) Written in Ocaml, how cool is that? (**)
(**) Very.
The Army reading list
Usually IBM has got good code, so there is hope that this will make a better browser. Certainly, it will be a great merit for firefox. Branding IBM code is a quality sign in my eyes, and might lead to wider acceptance of Firefox, as IBM seems to have noticed the browser.
Assembling etherkillers for fun an profit
Does anyone have a version of this article that isn't a vague promise that several buzzwords now have more to do with each other than ever?
I would expect this code actually does something, but the article is so vague I'm not really sure what. What's an example of something that does not work now that will work after this code is integrated and released?
(Preferably from someone who actually knows; I could make stuff up based on the article too, like this: "Before, if you set the ALT attribute on a dynamically-generated IMG tag, the screen-readers couldn't pick it up. Now they can." But I'm not sure if that's what they mean; that's just my plausible interpretation of the buzzword soup that I'm not very confident in, as I would have thought that works fine now....)
Chronology could make the link you provide somewhat invalid. That story mentions that market share slipped last month, yet I don't recall it saying where the figures are right now. But that's probably going to become irrelevant.
;) I don't think Firefox developers are going to let a one month slip get to them.
Even if the user-base hit a plateau already and everyone that wants Firefox, has it, this is article talks about providing accesability to a whole new audience. Being the first in the field does give one an advantage when the two biggest competitors are commercial (Opera) and slower than waiting for a new IE (uh...IE).
I know there are others, but when these are the three biggest players, Firefox stands to gain a good deal of respect in the accesability crowd if they pull this off with IBM.
By all means, it won't topple IE, but providing a good set of features to those with disabilities could actually see Firefox instituted in more public terminal situations like schools, libraries and such.
Besides, OSS tends to be pretty stubborn in the fact that the developers usually stop for nothing short of complete bankruptcy
Perfecting Discordia
www.stevenvansickle.com
I'd certainly like for it to open doors but features like these won't really matter unless IE pick up on them, too. The sad reality is that most sites need to work 100% with IE and the attitude towards Firefox/Safari is "if the site's legible, then it's ok". Maybe it can get some headway in some specialized areas, libraries or job centers or some other place where accessibility is a real priority, I don't know. I do however know that the one and only thing that will help Firefox dethrone IE is browser stats. It needs to hit some serious percentage. Only then will people stop "optimizing" for IE and start building their HTML according to standards.
:)
Great job on the DHTML patch, though! This sort of thing is why I use Firefox
Yah, and with a nick like OS24Ever, this person is obviously the perfect choice for making predictions about the acceptability and potential for success of a product....
(Sorry, I couldn't resist. I'm a former OS/2 user and licensee myself. "Blue Spine" all the way, baby.)
dragonhawk@iname.microsoft.com
I do not like Microsoft. Remove them from my email address.
Firefox already adheres to standards better than IE, has a more rubust, and secure environment, and arguably provides a superior user experience to IE, and yet IE lives on... So why would some (arguably nice) DHTML addons make a difference?
I think the situation's kinda like this: Those who care, and/or are "in the know" are already using Firefox.
The rest of the users still left on IE either
- Don't care (lazyness, "not my pc", whatever)
- Are too intimidated by technology to go outside the little box they've created for themselves
- Think IE's still the better browser
I suspect the bulk of the switchers have already switched, and the rest either will not switch until either their OS of choice changes (OSX anyone?), or they are faced with a computer-oriented crime which makes them paranoid about using IE (be it identity theft, stolen cc info, whatever)So while IBM's gift is a "nice to have", I don't see it making a huge difference in the lives of the average IE user. Not at the moment, at least.
You know, code that will help make Flash and its lookalikes accessible to people who maybe can't see or hear?
That's most likely what the poster of the story intended when he/she speaked of being able to "replace IE in many Windows environments."
-Rob
Biblical fiscal responsibility
My bet is that IBM is still dreaming of a day where the OS is irrelevent, since all your apps are Java based (perhaps even XUL based) and accessable through a standards compliant browser. IBM has a lot of expertise in this area, and stands to make a really nice chunk of change if customers migrate to this way of getting thier apps.
If Firefox gets above 10% marketshare and stays there, IBM should be able to do real damage to the competition by luring thier customers to more open solutions on the Firefox platform and marketing them as liberation from vendor lock in.
I'd buy into that, myself.
Soko
"Depression is merely anger without enthusiasm." - Anonymous
Just last night I wanted to show my wife a picture of a Merkur XR4TI, so she'd understand why it was funny that Prinicpal Skinner on The Simpsons drives one...
Procrastination -- because good things come to those who wait.
To many people who are only casual users of computers still consider firefox a bad Clint Eastwood movie
Please to remember: there's a difference between a bad movie that has Clint Eastwood in it, and a 'bad' Clint Eastwood movie. As Clint Eastwood movies go, Firefox is pretty damned good, really. Seriously, if you don't believe me, go see "Stealth." *shudder*
And remember: your browser will only work if you think in Russian. Think...In...Russian!
- At some point you're going to need to know how to do [X random thing] that your sample code doesn't already do. Your only options at this point are to start scouring the internet for firefox extensions, looking for extensions which do something kind of like what you want to do, and then looking at their source code to see how they did it; or mercilessly bother the IRC channel until somebody who's already done this comes by
- At some point, inevitably, you're going to hit a point where the sample code deceives you! All code contains implicit contracts. You cannot learn those contracts simply by looking at source code. Without documentation to make those contracts explicit, you are left either breaking contracts-- and thus your entire program, when some other part of the program expects something to be X at a certain time when it is in fact Y-- or doing a crazy kind of cargo cult programming, terrified to change anything unless you break the magic incantation that makes the component or preferences or whatnot system recognize your existence. I lost about two weeks on my project because I looked at the sample code, saw it always did a certain thing a certain way, concluded I could do the same thing the same way elsewhere, and was entirely ignorant as to the fact that there was another file in a totally different part of the package which I had to modify for every instance of this specific thing. What this meant was that I made extremely simple alterations to the file I was working on, and the entire extension broke-- for no reason I was aware of-- because I had accidentally caused a mismatch between the file I was working on and a totally different file.
And this is just for extensions, a VERY common thing many people have done. As I started to poke my nose into more intricate and obscure things-- say, components-- I found the amount of available information on how to proceed went from inadequate to absolutely nonexistent. I can only imagine what you are going through trying to embed the entire engine.Nobody. Fucking. Cares.