Confirmed users
1,041
edits
Talk:Firefox2/Features: Difference between revisions
Jump to navigation
Jump to search
m
→Updater
m (→Updater) |
|||
| Line 21: | Line 21: | ||
* [[User:shadowchaser|shadowchaser]]: I completely agree with the comment about MSI packages. MSI packages are an absolute must if Firefox wants to make ANY inroads in the business or enterprise markets. Many IT departments are VERY "Microsoft" centric, and extensively leverage Active Directory or other deployment technologies. Companies are not going to bother installing Firefox manually on every desktop - they need to be able to deploy it automatically to thousands of machines automatically using Windows Installer (MSI). Adding this feature, and support for Windows Policies (ADM templates, etc) would make a HUGE dent in the IE market share. Remember all the reviews of Firefox when it came out? Most people completely wrote it off in corporate environments, saying how most would not deploy it without MSI or policy support. IT shops need automatic deployment, and the ability to force their evil ways onto users (ie/ lock out features). I disagree with tim's comment about an IE fake mode - copying IE exactially would lead to serious trademark issues. Firefox has already strived to have a similar look and feel to Internet Explorer - the only thing I would suggest is to natively support the Windows "Favorites" OS feature. You might want to take a look at the "Open Office" team. They resisted and fought for years against MSI, then finally gave in and now Open Office 2.0 supports it. Why? It's the ONLY way to make inroads into large "Microsoft Shop" corporations. | * [[User:shadowchaser|shadowchaser]]: I completely agree with the comment about MSI packages. MSI packages are an absolute must if Firefox wants to make ANY inroads in the business or enterprise markets. Many IT departments are VERY "Microsoft" centric, and extensively leverage Active Directory or other deployment technologies. Companies are not going to bother installing Firefox manually on every desktop - they need to be able to deploy it automatically to thousands of machines automatically using Windows Installer (MSI). Adding this feature, and support for Windows Policies (ADM templates, etc) would make a HUGE dent in the IE market share. Remember all the reviews of Firefox when it came out? Most people completely wrote it off in corporate environments, saying how most would not deploy it without MSI or policy support. IT shops need automatic deployment, and the ability to force their evil ways onto users (ie/ lock out features). I disagree with tim's comment about an IE fake mode - copying IE exactially would lead to serious trademark issues. Firefox has already strived to have a similar look and feel to Internet Explorer - the only thing I would suggest is to natively support the Windows "Favorites" OS feature. You might want to take a look at the "Open Office" team. They resisted and fought for years against MSI, then finally gave in and now Open Office 2.0 supports it. Why? It's the ONLY way to make inroads into large "Microsoft Shop" corporations. | ||
== | == Extension Installation and Upgrades == | ||
* [[User:mh166|mh166]]: After updating (or after installing) an extension it should not be necassary to restart Firefox. It's really anoying if you got dozens of sites opened and have to restart for updates taking change. I'm software developper of my own, too. And I think there should be possibilities for updating without restarting (haven't worked with plugin(systems) yet, but will do). So: why is it necessary atm? | * [[User:mh166|mh166]]: After updating (or after installing) an extension it should not be necassary to restart Firefox. It's really anoying if you got dozens of sites opened and have to restart for updates taking change. I'm software developper of my own, too. And I think there should be possibilities for updating without restarting (haven't worked with plugin(systems) yet, but will do). So: why is it necessary atm? | ||