Slashdot Mirror
Mozilla To Launch "Build Your Own Browser"
angry tapir sends in a piece from Down Under which begins "Mozilla is readying a program that will allow companies to build their own customized browsers based on the next version of Firefox, which will be out in a few weeks. ... Through the Build Your Own Browser program, which will start sometime soon after Firefox 3.5 is released at the end of June, companies can use a Web application provided by Mozilla to specify certain customizations for the browser, such as bookmarks to certain sites or corporate intranets or portals. ... The bulk of enterprises still use Internet Explorer if they mandate a browser for company use, because Microsoft provides provisioning and installation software for IE that makes it easy for enterprises to control browser settings and install across all corporate desktops, said Forrester analyst Sheri McLeish. Mozilla has not historically done this, but something like the Build Your Own Browser program is a good start to encourage enterprises to use Firefox over IE."
Out of curiosity, when chronologically was this? I know I was building customized Internet Explorer 4 browsers using an NT 4 IEAK back in '98.
I'm sort of vaguely remembering a comparable feature involving Netscape about then, also?
By the way. I still think IE4 didn't suck in comparison to the competition when it came out. As a matter of fact, I would say that about Microsoft in general up until mid/late 2000. They got really squirrelly about then.
Evil and monopolistic, sure. but in a useful way.
Why, yes, I AM a Pagan Libertarian.
I dunno, I work for a Fortune 100 company and we use IE because all the crappy "enterprise" software we run requires stupid ActiveX or JavaScript or whatever that only runs on IE6. Good luck to FireFox, but customizations ain't got nothing to do with it where I work.
There's even more to it than that. The WebBrowser COM/.NET control is the IE control. Even if you manage to supplant IE as the browser of choice, all code which embeds the COM or .NET wrapped COM control depends on it. So for example, the Windows Shell and the help system, and Windows Update, Windows Media Player, third party apps integrating the system WebBrowser such as WinAmp, etc.
The Internet Explorer browser itself is really just a light weight set of UIs wrapped around the standard WebBrowser COM/ActiveX control. It's actually pretty fun to write .NET code that interacts with the WebBrowser. You can add some interesting features like web page scrapers, etc.
Even more than before, ISPs will push "their" own flavor of a browser that comes bundled with those godforsaken coasters that unsuspecting victims dump into their machines, only to end up with an IE (or FF from now on, too) that blatantly advertises the ISP, rehijacks the "favorite browser" position every time you rip it from him and stuff all kind of browser addons into it that you strangely cannot get rid of anymore due to miraculously missing deinstall routines.
I like the idea. No really, I do. But this is what it will be (ab)used for.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
At UW-Milwaukee's dorms, I used FFDeploy to do just this: create a silent Firefox installer for student and faculty machines with some built-in bookmark buttons for our student service websites, e-mail system and so on.
Doing this saves time and installs FF with a nice student-friendly UI right off the bat -- very useful in converting otherwise IE-centric students who don't care what browser they're using to Firefox.
Good point - but then you're hitching the proverbial wagon to not just one vendor now, but two. While you could approach the problem this way, wouldn't it be a lot more efficient to just work with the web app vendor to build in compatibility?
Clearly it can be done - I'm betting that Hong Jen Yee would be up for a nice paycheck for this kind of work.
Depends on the vendor. If the business demands MS Exchange, then OWA in "Light Mode" is all you get in FF. It becomes very hard to justify a browser change if it's going to cost $$$ making a system supplied by $vendor that has a major business investment in it or even changing vendors when what comes with Windows "works" (term used very loosely there).
I prefer the "Best of Both Worlds" approach. Free to deploy our browser of choice and no fighting with vendors that will state that IEx is a requirement so bad luck.
It will also make pathways towards using more cross platform software, anything that can break the dependencies is a "Good Thing".
# cat
Damn, my RAM is full of cats. MEOW!!
IMO, IEtab for Linux is actually a great idea. Currently people use IEs4linux or just plain WINE or a virtualisation environment - having an IEtab for linux that can seamlessly hook into a virtualised / WINE version of IE could be useful for those migrating from a Microsoft OS to a Linux distro or those doing testing with IE.
Bonus marks if it virtualises IE6/IE7/IE8 and allows compatibility modes too and only shows as a tab in FF none of the virtualisation env being revealed.
Currently I use dual-boot and virtualbox (for web design compat. testing), which I'd need to keep on with but an IEtab4linux could aid brief testing.