6
edits
CCK:Overview: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 84: | Line 84: | ||
And perhaps we can make the install piece use a mozilla.cfg file if it is available to combine the two (not just putting the jsc file on a server) | And perhaps we can make the install piece use a mozilla.cfg file if it is available to combine the two (not just putting the jsc file on a server) | ||
--[[User:Robin|Robin Lu]] 4/30 10:21:50 CST 2005 | |||
You are right. The mozilla.cfg should be added into install package by installer builder to enable the autoconfig by default. It is the connection point. | |||
For the menu lockdown, we should find out if admin want to lock the menu by default or they want to manage/change what to lock after deployment. I believe locking the menu by installer builder can meet most of the requirement. What do you think? | |||