File Details |
|
| File Size | 0.0 MB |
|---|---|
| License | Freeware |
| Operating System | Windows (All) |
| Date Added | May 8, 2006 |
| Total Downloads | 2,734 |
| Publisher | Mozilla.Org |
| Homepage | Firefox 1.5 CCK (Client Customization Kit) |
Publisher's Description
Firefox CCK allows people to create an extension that customizes the browser for a particular installation or deployment. Example customizations include adding an indentifier to the user agent string, changing the default home page, title bar text and the animated logo, preinstalling browser plugins and search engines, adding bookmarks, registry keys and certificates.
Latest Reviews
spiked reviewed v1.0 on May 8, 2006
It's about time! This is a good start on matching the IEAK which Microsoft has been offering for NINE YEARS, but the CCK is merely a start. For instance, it doesn't assist with actually packaging the custom configuration into an installer; you have to follow the manual instructions (for Win32) at mozilla.org/projects/cck/firefox/wininstall.html
Secondly, the CCK doesn't provide any way for corporate deployments to enforce the customized settings; the end-user can simply uninstall the CCK-generated XPI. Firefox needs to implement Group Policy-based restrictions. Sure, it would be a Win32-specific, Active Directory-specific feature which all MS haters will turn their noses up at, but do they care about Firefox adoption or not? Growth in Firefox has started to run out of hobbyists and other home users to spread to.
Congrats to the CCK team on this first attempt, but looking forward to future improvements...
spiked reviewed v1.0 on May 8, 2006
It's about time! This is a good start on matching the IEAK which Microsoft has been offering for NINE YEARS, but the CCK is merely a start. For instance, it doesn't assist with actually packaging the custom configuration into an installer; you have to follow the manual instructions (for Win32) at mozilla.org/projects/cck/firefox/wininstall.html
Secondly, the CCK doesn't provide any way for corporate deployments to enforce the customized settings; the end-user can simply uninstall the CCK-generated XPI. Firefox needs to implement Group Policy-based restrictions. Sure, it would be a Win32-specific, Active Directory-specific feature which all MS haters will turn their noses up at, but do they care about Firefox adoption or not? Growth in Firefox has started to run out of hobbyists and other home users to spread to.
Congrats to the CCK team on this first attempt, but looking forward to future improvements...